What are story points?
Story points are a relative-sizing unit used to estimate the effort of a backlog item. They roll three things into a single number: complexity, effort, and uncertainty. They're not hours — they're a measure of "how big is this compared to other things we've done?"
The Fibonacci scale
Most teams use a modified Fibonacci sequence: 1, 2, 3, 5, 8, 13. The gaps between values get bigger to reflect how uncertainty grows with size. A 13 isn't "13 times harder than a 1" — it's "much bigger and we're not sure how much."
Anything bigger than 13 should be split, not estimated.
Why story points beat hours
- Less false precision — saying "5" admits uncertainty in a way "12 hours" doesn't.
- Per-team calibration — a "3" on your team is whatever your team's "3" has been historically.
- Faster estimation — relative sizing is faster than calendar arithmetic.
Converting to hours
If a stakeholder asks for hours, multiply by your team's hours-per-point ratio. Your velocity divided by sprint capacity gives this number.
Use our Story Points Estimator to convert in one click.
Common story point mistakes
- Treating points as hours — defeats the whole purpose. Stay relative.
- Cross-team comparison — never compare points across teams.
- Estimating without a reference — anchor against a recent ticket the whole team agrees was a "textbook 3."