Agile guide · Agile practices
Agile Estimation: Story Points and the Fibonacci Scale
Agile teams rarely estimate in hours. Instead, they compare pieces of work with each other using relative units called story points, often on a Fibonacci-like scale. This guide explains why, and how to do it well.
Key takeaways
- Story points measure relative size, combining effort, complexity and uncertainty.
- The Fibonacci scale's growing gaps reflect growing uncertainty.
- The discussion during estimation is more valuable than the number.
Why relative estimation?
People are poor at predicting exactly how long work will take, but good at comparing: "this is about twice as big as that." Relative estimation uses that strength. Story points combine effort, complexity and uncertainty into one number that is only meaningful within the team.
The Fibonacci scale
The Fibonacci sequence is 1, 2, 3, 5, 8, 13, 21, where each number is the sum of the two before it. Many teams use a modified version: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100.
The gaps grow as the numbers grow, which reflects reality: the bigger the item, the less precise the estimate can be. It also stops pointless debates between, say, 11 and 12.
How to run planning poker
- The Product Owner explains a backlog item and answers questions.
- Each estimator privately picks a card from the scale.
- Everyone reveals their card at the same time.
- The highest and lowest estimators explain their reasoning.
- The team discusses and votes again until estimates converge.
The conversation matters more than the number. Wide differences usually reveal misunderstandings or hidden risks.
Other estimation techniques
- T-shirt sizing (XS, S, M, L, XL) for quick, rough sizing of large backlogs or roadmap items.
- Affinity estimation: the team silently places items on a wall from small to large, then groups them.
- Bucket system: items are placed into Fibonacci-labelled buckets, good for estimating many items quickly.
- No estimates: some teams split all work into similarly sized small items and simply count them.
Using estimates
Story points combine with velocity, the number of points a team completes per sprint, to forecast how much it can take on and when a release might be ready.
Common mistakes
- Converting points back into hours.
- Comparing story points or velocity between teams.
- Letting one senior person estimate for everyone.
- Re-estimating finished work to make velocity look better.
- Treating estimates as commitments or deadlines.
Free templates for this topic
Frequently asked questions
Why use story points instead of estimating in hours?
Hours invite false precision and depend on who does the work. Relative points are faster to agree and become reliable for forecasting once the team's velocity is known.
Who estimates story points in Agile?
The people who will do the work. The Product Owner clarifies the item but does not estimate it.
What are story points in Agile?
A relative unit of estimation that combines effort, complexity and uncertainty. A 2-point item is roughly twice the size of a 1-point item, but points have no fixed link to hours.
Why do Agile teams use the Fibonacci sequence for story points?
The gaps between numbers grow as items get bigger, reflecting that large items are less predictable. It also prevents pointless debates between close numbers like 11 and 12.
What is planning poker for story points?
An estimation game in which each person privately chooses a card, everyone reveals at once and the highest and lowest estimators explain their thinking before re-voting.
How many hours is a story point?
There is no standard conversion, and fixing one defeats the purpose. Points are only meaningful relative to other items estimated by the same team.
What is T-shirt sizing compared with story points?
A rough estimation technique using sizes such as XS, S, M, L and XL. It is useful for large backlogs or roadmap items before detailed estimation.
How do you choose a reference story for story points?
Pick a small, well-understood item the team has completed and agree its size, often 2 or 3 points. Compare new items with it.
Can story points be compared between teams?
No. Each team calibrates points differently, so comparing them is meaningless and encourages point inflation.
What if an item is estimated at 13 story points or more?
It is usually too large to finish in one sprint. Split it into smaller items before planning.
What is #NoEstimates, and does it replace story points?
An approach in which teams split work into similarly sized small items and simply count them for forecasting instead of estimating each one.