Drunk Agile Episode 105 - Using Sprint Length To Size Stories
6 snips
May 13, 2025 The hosts dive into the pitfalls of sizing user stories solely based on sprint length. They advocate for a more adaptable, capability-focused approach to ensure better outcomes. Exploring how sprint duration impacts planning, they reveal that a standard cycle might hinder agility. The discussion touches on managing cycle times in regulated industries and addresses common misconceptions about Scrum. Plus, they emphasize the importance of audience feedback in refining content.
AI Snips
Chapters
Transcript
Episode notes
Don't Size Stories by Sprint Length
- Avoid using sprint length as the guideline for story sizing since it often causes problems.
- Determine story size based on actual process capability and cycle time, not fixed sprint duration.
Sprint Length Often Arbitrary
- Sprint lengths like 14 days are often arbitrary and based on industry norms rather than actual needs.
- It's more important to understand your process capability and adjust sprint length and story size accordingly.
Use Continuous Start and Cycle Time
- Start work on stories continuously rather than all at sprint start to avoid sprint planning becoming irrelevant.
- Use cycle time metrics like median or 85th percentile to size stories based on how long work actually takes.