What are Story Points?
Story Points are a relative unit for the size of a backlog item. They combine effort, complexity and uncertainty into one shared number the team can compare across stories.
How Story Points work
Teams pick a familiar reference story and size new work against it. A 2 should feel roughly twice a 1. A 13 should feel substantially larger and riskier than an 8. The value is the conversation quality, not mathematical perfection.
Story Points vs hours
Hours encourage false precision and individual hero estimates. Story Points keep the focus on relative difficulty for the whole team. Capacity planning still matters, but velocity is tracked in points completed per sprint rather than promised hours.
How to estimate Story Points
A practical estimation loop looks like this:
- Clarify the outcome and constraints of the story.
- Compare it with recently completed reference work.
- Vote independently with Planning Poker or Scrum Poker.
- Discuss outliers and agree on a shared size.
Fibonacci Story Points
Most Scrum teams use a modified Fibonacci sequence because larger gaps discourage over-precision on big uncertain items. Common values include 0, 1, 2, 3, 5, 8, 13 and 21.
What 1, 2, 3, 5, 8 and 13 mean
Exact definitions vary by team, but a useful starting frame is:
- 1: tiny, well-understood change
- 2: small piece of work with little uncertainty
- 3: moderate work, clear path, some coordination
- 5: meaningful feature slice with several moving parts
- 8: large item that may hide risk or unknowns
- 13: very large; consider splitting before commitment
Story Point examples
A copy change on one screen may be a 1. Adding validation to an existing form may be a 3. Building a new filtered list with API changes may be an 8. If the team cannot explain the risks in a few minutes, split the item before forcing a number.
Story Points, complexity and velocity
Points reflect more than coding time. Complexity, unknowns, testing effort and coordination all count. Velocity is the average points completed over recent sprints. Use it for forecasting ranges, not as a performance target for individuals.
Common Story Point mistakes
Avoid these patterns:
- Converting points back into fixed hours
- Using points to judge individual speed
- Estimating work that is still undefined
- Never splitting oversized 13s or 21s