Story points & time
The questions about story points that don't go away. Direct answers, with the failure modes named.
Story points are a relative-effort measure. The single biggest failure mode of Planning Poker is the team that starts converting them into hours, days, or person-weeks — at which point the team has thrown away the property the technique exists to give them. The pages below cover the conversion-trap questions, the "should I" questions, and the work types that get systematically under- or over-sized.
The conversion trap
- Story points vs hours
- Story points per sprint
- Velocity
- Story points vs time
- Story points vs t-shirt sizing
- Relative vs absolute estimation
- Epic vs story vs task
- Why no 1-point stories?
"Should we estimate X?"
- Should bugs have story points?
- Should spikes have story points?
- Do story points include testing?
- Do story points include weekends?
- Story points vs acceptance criteria
When to revisit an estimate
When scale gets in the way
Adjacent: other estimation techniques for the alternatives to points; common mistakes for the in-session failures these questions usually surface.