In this article, I describe a User Story pattern that is useful for teams that are advanced in their User Story practices. In short, the pattern is to ensure that all User Stories can be completed in 2-3 days by one developer. This pattern requires fairly advanced story slicing skills, as well as other key User Story skills and circumstances. However, when properly executed, the pattern has the follow valuable advantages for stories this small:
- More opportunities to eliminate waste by deferring or dropping unneeded stories.
- Less total effort required to understand stories.
- Higher quality implementation: fewer bugs.
- Less effort expended in creating and estimating tasks
- Increased team morale by allowing more frequent story closure
In the article, I cover the team context that is required to achieve the pattern, the advantages of the pattern, and a strategy for progressing towards the pattern. I also discuss how this pattern can impact the Scrum implementation.