How can a user story be negotiable as well as estimable
INVEST criteria. good user stories are: Independent; Negotiable; Valuable; Estimable; Small; Testable.
A user story is written from the user's perspective using the format .
I want [goal] so that [benefit]."
It should be :
(1) independent*, negotiable**, valuable to users,
(2) estimable by developers,
(3) small enough to complete in one sprint, and
(4) testable with clear acceptance criteria.
Stories focus on user needs rather than technical implementation details.
*Independent: should not be dependent on other user stories for completion of value.
**Negotiable:
The negotiable nature of user stories can make precise sizing difficult, which is why most agile teams use a multi-step refinement process to resolve this.
Story Refinement/Grooming: is where negotiability transitions to clarity. During these sessions (usually before sprint planning), the team collaboratively discusses the story, asks clarifying questions, and explores implementation approaches. Key details get documented as acceptance criteria, and the team reaches a shared understanding of scope and approach.
Acceptance Criteria: serve as the bridge between negotiable and concrete. They specify the conditions that must be met for the story to be considered "done," providing enough detail for accurate estimation while preserving flexibility in implementation methods.
Estimation typically happens in story points: rather than hours initially, reflecting relative complexity and effort. Teams often use techniques like Planning Poker, where the discussion during estimation helps surface assumptions and clarify requirements. Only after this shared understanding emerges can teams break stories into tasks and estimate hours if needed.
By sprint planning, there should be enough clarity for confident estimation and commitment.
Comments
Post a Comment