Definition
Fibonacci estimation is an agile estimation technique where teams assign story points using numbers from the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21. Some teams extend to 34 and use a "?" card for items that cannot be estimated. The sequence is used because the increasing gaps between numbers reflect a fundamental truth about software estimation: the larger the work, the less precisely you can estimate it.
The technique is most commonly used during planning poker sessions, where team members independently select a Fibonacci number for each backlog item and then reveal their estimates simultaneously. Divergent estimates trigger discussion. If one developer estimates a 3 and another estimates a 13, the team discusses their assumptions until they converge.
Fibonacci estimation differs from T-shirt sizing, which uses relative labels (S, M, L, XL) instead of numbers. Fibonacci gives you numerical values that can be summed for velocity tracking and sprint capacity planning. T-shirt sizing is faster but less precise. Many teams start with T-shirt sizing for early-stage roadmap planning and switch to Fibonacci for sprint-level estimation.
Why It Matters for Product Managers
Fibonacci estimation gives PMs the data they need for delivery forecasting. When you know the team's average velocity is 30 story points per sprint and the remaining backlog totals 120 points, you can estimate roughly 4 sprints to completion. This is imprecise, but it is far better than guessing.
The estimation conversations are often more valuable than the numbers themselves. When an engineer estimates a seemingly simple feature at 13 points, the discussion reveals hidden complexity: database migrations, third-party API limitations, edge cases the PM had not considered. These conversations improve the PM's understanding of technical constraints and lead to better-scoped requirements. The RICE calculator can help you weigh the estimated effort against the expected impact when prioritizing items.
How to Apply It
- ☐ Calibrate the team by estimating 3-5 completed items as reference points (anchor stories)
- ☐ Use planning poker to prevent anchoring bias during estimation sessions
- ☐ If an item is estimated at 13+, break it down into smaller pieces before the sprint
- ☐ Track velocity using Fibonacci sums to improve sprint planning accuracy over time
- ☐ Re-estimate items when significant new information emerges (scope change, technical discovery)
- ☐ Never use story points to compare productivity across teams (different teams calibrate differently)
For a structured approach to estimation sessions, see the sprint planning guide. Teams that find Fibonacci estimation too heavyweight for early-stage planning may prefer T-shirt sizing as a lighter alternative.