Guide
Story points explained
A relative unit for sizing backlog items. Story points capture complexity, uncertainty, and volume in a single number — popularised by Mike Cohn in Agile Estimating and Planning (2005) and now the default unit for Scrum and Extreme Programming teams.
What story points actually measure
A story point bundles three things into one number:
- Complexity — how intricate is the logic, how many systems are involved, how many edge cases need handling.
- Uncertainty — how much of the work is well-understood vs. exploratory. A new integration with an undocumented third-party API is high-uncertainty even if the code itself is simple.
- Volume — sheer amount of work. A hundred near-identical CRUD endpoints is high-volume even at low complexity.
A 5-point story is not five times harder than a 1-point story. It is just clearly bigger than a 3 and clearly smaller than an 8, on a scale this specific team has calibrated.
Why not hours or days?
Hour estimates have two failure modes:
- They anchor on the fastest person in the room. The senior developer who could do this in four hours says "four hours", and the juniors silently fold to avoid looking slow.
- They ignore uncertainty. A story estimated at "eight hours" that turns out to need a refactor stops being eight hours, but the estimate is locked.
Story points side-step both. The team expresses relative size without committing to a duration that will be wrong. Over a few sprints, velocity — story points completed per sprint — emerges as a stable team-level number that absorbs individual variance. Planning then uses velocity, not individual estimates, to forecast.
The Fibonacci connection
Most teams use the Fibonacci-like sequence (1, 2, 3, 5, 8, 13, 21) because human estimation precision drops as work gets larger. The widening gaps are a feature: they prevent the team from arguing about whether a story is a 7 or an 8 — that resolution does not exist. See the Fibonacci scale guide for the deeper why.
Common misconceptions
"Story points are just hours in disguise"
No. Two teams delivering the same work will land on different point totals because they have calibrated differently. The number only has meaning inside one team.
"Story points are a commitment"
They are not. They are an estimate of size at the moment of estimation. If the story turns out to be bigger once you start, you re-estimate or split — the original number is not a contract.
"Higher velocity is better"
Velocity is a forecasting input, not a performance metric. Teams that get measured on velocity inflate point estimates and the signal degrades.
How to calibrate a new team
- Pick a small, well-understood story the team has already delivered.
- Agree on its size — typically a 3 or 5. This is the reference story.
- Estimate every new story relative to the reference ("bigger than the reference 5; smaller than the reference 8").
- After three to five sprints, the team has a shared sense of magnitude. The reference story can fade.
FAQ
- Are story points the same as hours?
- No. Story points capture relative effort — complexity, uncertainty, and volume in one number. Hours capture absolute duration. A 5-point story does not equal five hours; it just means clearly bigger than a 3 and clearly smaller than an 8 for this team.
- Why use story points instead of hours?
- Because hour estimates anchor on the fastest person in the room and ignore uncertainty. Story points let the team express 'this is bigger and riskier' without committing to a specific duration that will be wrong. Velocity (story points completed per sprint) then averages out the individual variance.
- Why is the Fibonacci sequence used?
- Because human estimation precision drops as the work gets larger. The widening Fibonacci gaps (1, 2, 3, 5, 8, 13, 21) prevent false precision: a 13-point story is not thirteen times harder than a 1-point story — it is just clearly bigger and probably needs splitting.
- Can a story be zero points?
- Some teams use zero for trivial work bundled with a larger story. Most teams do not bother — if it is worth tracking, it is worth a 1.
- How do new teams calibrate story points?
- Pick a reference story the team has already delivered, agree on its size (typically a 3 or 5), and estimate every new story relative to it. After three to five sprints the team has a shared sense of magnitude and the reference story can fade.
Estimate with your team
Paste your backlog and share the room link. No account, no sign-up. Sessions auto-delete after 24 hours.
Start a planning poker session