Story Points Explained
Story points are a unit of measure agile teams use to express the overall effort required to fully implement a backlog item. They're deliberately relative, not absolute — a way to compare the size of tasks rather than to clock them in hours.
What goes into a story point?
A story point bundles three things into a single number:
- Volume of work — how much there is to do.
- Complexity — how hard or intricate the work is.
- Uncertainty / risk — how many unknowns could bite you.
Two tasks can take the same number of hours but differ wildly in complexity and risk. Story points capture that difference in a way raw time estimates can't.
Why not just estimate in hours?
Humans are notoriously bad at estimating absolute durations but reasonably good at relative comparisons ("this is about twice as big as that"). Story points lean into that strength. They also travel better across a team: your "3 hours" and my "3 hours" differ, but a shared "3-point" reference means the same thing to both of us.
Why the Fibonacci sequence?
Most teams estimate points on the Fibonacci-style scale — 1, 2, 3, 5, 8, 13, 21 — or a lean subset like 1, 3, 5, 8, 13. The growing gaps reflect a simple truth: the bigger a task, the less precise any estimate can be. Forcing a choice between 8 and 13 (rather than fussing over 9 vs 10) keeps the conversation honest. Our cards & scales guide compares the options.
| Points | Typical meaning |
|---|---|
| 1 | Trivial, well understood, do it in your sleep |
| 2–3 | Small, clear, low risk |
| 5 | Medium; some moving parts |
| 8 | Large; complexity or unknowns |
| 13+ | Too big — split it into smaller stories |
Estimate story points together with planning poker.
Start a free sessionStory points and velocity
Over a few sprints, a team learns how many points it typically completes per sprint — its velocity. That average is what turns points into a forecast: if a team averages 25 points a sprint and the release backlog is 100 points, it's roughly four sprints away. Crucially, velocity is a planning aid for the team, not a productivity metric to compare teams or to weaponize.
Common mistakes to avoid
- Converting points to hours. It defeats the purpose and re-introduces false precision.
- Comparing velocity between teams. Points are calibrated per team; the numbers aren't interchangeable.
- Inflating estimates over time. Keep a stable reference item so a "5" means the same thing sprint after sprint.
- Estimating solo. Points work best when the team estimates together — for example with planning poker.