Story Points Explained
Points, not hours
A story point is a relative measure of effort, not a unit of time. When a team says a story is "5 points," they're saying it's roughly five times as much work as a 1-point story - not that it will take five hours, or five of anything measurable on a clock. That's deliberate: two developers rarely agree on how many hours something takes (skill, familiarity with the code, and interruptions all differ), but they can usually agree on relative size.
Why relative sizing works better
Humans are bad at estimating absolute effort but decent at comparing two things side by side - it's much easier to say "this feels about twice as involved as that other story we did last week" than to say "this will take exactly 6.5 hours." Story points lean into that strength instead of fighting it.
Where the numbers come from
Most teams use a Fibonacci-like scale (1, 2, 3, 5, 8, 13, 21...) instead of a plain 1-10 range. The growing gaps between numbers reflect growing uncertainty - a team can be fairly precise that something is a 2 versus a 3, but "13 vs. 14" is a meaningless distinction nobody can actually back up. See our Planning Poker explainer for how teams actually agree on a number together.
Keeping estimates consistent
Story points only stay useful if the whole team calibrates against the same reference stories. A common approach: agree as a team on one or two past stories that clearly represent "a 3" and "an 8," and compare new stories against those anchors instead of estimating from scratch every time.
What points are not for
Story points aren't a promise, and they don't transfer between teams - a 5 for one team can be a 2 for another, since it depends entirely on that specific team's shared frame of reference. Using points to compare individual output, or to compare velocity across different teams, is a common way estimation exercises turn into something less useful than the discussion they're supposed to trigger.
Putting it into practice
The easiest way to keep a team calibrated is to estimate together, live, rather than async in a spreadsheet - run a Planning Poker session and the discussion that keeps estimates consistent happens naturally as part of voting.
Try Fibopoker free
Estimate story points together in real time - no account needed to join a session.
Start a free session