What are Story Points?
Story points measure complexity — not hours. Understanding that takes five seconds. Applying it correctly takes five sprints. The most common mistake: managers converting story points to hours, which turns a relative complexity tool into a broken time-tracking system.
Story points definition
Story points are a unit of measure for estimating the relative complexity and effort required to complete a backlog item. They are not hours or days. A story estimated at 5 points is considered more complex than one at 2 points — but the exact time it takes depends on the team's composition, focus, and unknowns encountered. Over multiple sprints, a team's average output in story points (velocity) becomes a reliable forecasting tool.
Why Fibonacci? (1, 2, 3, 5, 8, 13...)
Most teams use a Fibonacci-inspired scale rather than linear numbers. The reasoning: estimation accuracy degrades as complexity increases. The gap between 1 and 2 is much easier to judge than the gap between 13 and 14. The growing intervals in Fibonacci reflect this — they force the team to acknowledge increasing uncertainty rather than pretending they can estimate large work precisely.
If a story seems larger than 13, consider breaking it into smaller pieces before estimating.
Story points vs hours: the key difference
Hours say...
'This task will take 6 hours.' Specific, but often wrong — and wrong in ways that compound. An optimistic estimate creates schedule pressure; pressure leads to shortcuts; shortcuts create bugs; bugs take time to fix.
Story points say...
'This task is roughly twice as complex as that one.' Relative, calibrated over time. The team's velocity adjusts naturally sprint over sprint — absorbing reality rather than fighting it.
Common story point mistakes
Converting points to hours
The moment you say '1 point = 4 hours,' you've broken the tool. Management starts measuring individuals by points-per-hour, which destroys honest estimation.
Using velocity as a performance target
'We need to hit 40 points this sprint.' Velocity should measure what the team can do, not what they're expected to do. Velocity targets inflate estimates — the opposite of the point.
Estimating solo instead of as a team
The value of Planning Poker comes from the discussion when estimates diverge — not the numbers themselves. Solo estimation produces numbers without insight.
Never re-calibrating the baseline
If your team's composition or speed changes significantly, old point values lose meaning. Revisit the reference story after major team changes.
Frequently asked questions
Do all Agile teams use story points?
No. Story points are popular but not universal. Many experienced teams abandon them after years of use — they've built enough intuition to plan without explicit estimation. Some teams use #NoEstimates approaches. Story points are a useful scaffold; the goal is reliable planning, not the tool itself.
What is Planning Poker?
Planning Poker is an estimation technique where team members simultaneously reveal their estimate for a backlog item using cards. The simultaneous reveal prevents anchoring bias (one person's estimate influencing others). Large disagreements trigger discussion that surfaces hidden complexity or assumptions.
Test your Scrum knowledge
The Scrum Quiz covers estimation, velocity, sprint planning, and more.
Take Scrum Quiz →