A way to assess your user stories is to check if they meet the requirements dedined by Bill Wake's INVEST acronym in 2003. Bill Wake also repurposed the acronym SMART (Specific, Measurable, Achievable, Relevant, Time-boxed) for tasks resulting from the technical decomposition of user stories.
- Independent - We want to be able to develop in any sequence.
- Negotiable - Avoid too much detail; keep them flexible so the team can adjust how much of the story to implement.
- Valuable - Users or customers get some value from the story.
- Estimatable - The team must be able to use them for planning.
- Small - Large stories are harder to estimate and plan. By the time of iteration planning, the story should be able to be designed, coded, and tested within the iteration.
- Testable - Document acceptance criteria, or the definition of done for the story, which lead to test cases.
For more detail, User Stories Applied by Mike Cohn (pdf file)
* Real quote: "An investment in knowledge pays the best interest." - Benjamin Franklin
No comments:
Post a Comment