📊 Estimation fundamentals
Story Points: What They Are & How to Estimate
What story points actually measure, why agile teams prefer them to hour estimates, how to size them with planning poker, and how velocity turns them into a forecast.
What are story points?
A story point is a unit of relative effort. Rather than guessing how many hours a task takes, the team asks how big it is compared with other work they've done. A 5-point story is roughly five times the effort of a 1-point story. Points bundle three things into one number: complexity, uncertainty, and sheer volume of work.
Why points instead of hours?
Hour estimates feel precise but rarely survive contact with reality — they vary by who picks up the work and invite false confidence. Relative sizing is faster, more consistent across a team, and decouples estimation from individual speed. Over a few sprints the team's average points-per-sprint (its velocity) becomes a far more reliable planning input than any sum of hour guesses.
Velocity in plain terms
If a team completes around 30 points per sprint, you can forecast a 120-point backlog at roughly four sprints — and refine that as real data accumulates.
Don't compare velocities across teams
Points are relative to each team's own baseline. One team's 8 is another team's 5. Velocity is a forecasting tool, never a performance scoreboard.
How to estimate story points with planning poker
Planning poker is the most common way to assign points. The team discusses a story, everyone privately picks a Fibonacci card, and all reveal at once. Outliers explain their thinking and the team re-votes to consensus. The conversation calibrates everyone's sense of size — which is why the same team gets more consistent at pointing over time.
Frequently asked questions
▸What do story points measure?
Relative effort — a blend of complexity, uncertainty, and amount of work — not hours or days.
▸How many hours is a story point?
There is no fixed conversion, and trying to set one defeats the purpose. Points are relative to your team's own past work.
▸What scale should we use for story points?
Most teams use the Fibonacci sequence because its widening gaps reflect rising uncertainty for larger items.
▸What is velocity?
The average number of story points a team completes per sprint. It turns point estimates into a rough delivery forecast.
▸How do we estimate points as a team?
Planning poker is the standard method: discuss, vote privately on Fibonacci cards, reveal together, and re-vote to consensus.
Related guides
Point your backlog together
Run a free planning poker session and estimate story points as a team in real time.