Story points
Definition
Story points are a unit of relative estimation used by agile teams to measure the size, complexity, and uncertainty of a backlog item compared to other items — not a measure of the time or hours the work will take.
Story points are one of the most misunderstood concepts in agile. The single most common mistake: treating them as hours. They are not hours. A 5-point story doesn't take 5 hours — it takes roughly twice the effort of a 2- or 3-point story, relative to how your team calibrates.
Why relative estimation: Humans are notoriously bad at estimating absolute time on complex tasks. We're better at comparing. "Is this story bigger or smaller than the login feature?" is an easier question than "How many hours will this take?" Relative sizing acknowledges this and leans into comparison.
Common sizing scales:
- Fibonacci-inspired: 1, 2, 3, 5, 8, 13, 21 — the increasing gaps force the team to resolve ambiguity rather than splitting hairs between 6 and 7.
- T-shirt sizes: XS, S, M, L, XL — converted to numbers for velocity tracking.
- Powers of 2: 1, 2, 4, 8, 16 — simple but less common.
How teams estimate: Planning Poker is the most popular method — each team member privately selects a number, all reveal simultaneously, outliers explain their reasoning, and the team converges on a number. This prevents anchoring (the first person to speak biases everyone else).
What points capture:
- Effort (how much work is involved)
- Complexity (how technically difficult)
- Uncertainty (how much we don't know yet)
A story with a known solution but lots of tedious implementation might be 5 points. A story with an unknown solution might also be 5 points — for different reasons.
Story points only work within a single team's calibration. Never compare point values across teams.
Examples
- Team estimates a new API endpoint as 3 points and a full checkout redesign as 13 points
- Planning poker round: developers play 2, 3, 8, and 13 — the outliers explain their reasoning and team settles on 5
- Story re-estimated from 3 to 8 points during refinement after a hidden database migration is discovered
- New team member asks 'so 1 point = 1 hour?' — team explains the relative nature during onboarding
- Team uses velocity to forecast: 5 sprints of 40 points = 200 points of capacity for Q3
Related terms
Snap a story points. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.