Growing Uncertainty
Fibonacci gaps (1→2→3→5→8→13) grow larger as numbers increase, matching how confidence decreases for bigger estimates.
Fibonacci Estimation for Agile Teams
Estimate story points with Fibonacci sequence cards (1, 2, 3, 5, 8, 13, 21, 34, 55, 89). Free Planning Poker tool built for agile estimation, plus a downloadable Fibonacci estimation template and printable cards. No signup required.
Jump to the Fibonacci estimation template · Printable planning poker cards
Start Fibonacci Estimation
1
2
3
5
8
Fibonacci sequence for accurate relative sizing
Fibonacci Estimation Template
Use this reference template to calibrate story points before your next planning session. Each Fibonacci value has a plain-language meaning, an example story and a rough effort hint. Replace the examples with stories your own team has already delivered: a shared set of reference stories is what makes relative estimation consistent. Effort hints are illustrative only; story points measure relative size, not hours.
| Points | Meaning | Example story | Typical effort hint |
|---|---|---|---|
| 1 | Tiny, fully understood change with no unknowns | Fix a typo or update a label on an existing page | A few hours at most |
| 2 | Small change, clear approach, minimal testing | Add an optional field to an existing form | Around half a day to a day |
| 3 | Small-to-medium change touching a couple of components | Add server-side validation with error messages and tests | About one to two days |
| 5 | Medium work with some coordination or minor unknowns | New API endpoint plus the UI that consumes it | A few days |
| 8 | Large work with several moving parts or a dependency | Add CSV export for a report with filters and permissions | Around a week; check whether it can be split |
| 13 | Very large or uncertain; probably more than one story | Integrate a third-party payment provider end to end | Most of a sprint; split before committing |
| 21 | Too big for one sprint with confidence | Build a new notification system (email, in-app, settings) | Longer than a sprint; break into smaller stories |
| 34 | Feature-sized; treat as an epic | Launch single sign-on for enterprise customers | Multiple sprints; refine into stories |
| 55 | Large epic with significant unknowns | Migrate the application to a new database | Many sprints; needs discovery work first |
| 89 | Initiative-sized; too vague to estimate as a story | Rebuild the mobile app | Quarter-scale; split into epics |
| ? | Not enough information to estimate | Any story with open questions about scope or acceptance criteria | Clarify with the product owner, then re-vote |
| ☕ | Team needs a break | Long refinement session losing focus | Pause, then continue |
How to Use the Template
- Download the CSV and open it in Excel, Google Sheets or Numbers.
- Pick reference stories: for 1, 3, 5 and 8, choose a finished story the whole team remembers and add it in the last column.
- Agree the split rule: most teams split anything at 13 or above before it enters a sprint.
- Estimate by comparison: during planning poker, ask “is this bigger or smaller than our 5?” instead of thinking in hours.
- Revisit each quarter: update reference stories as the codebase and team change.
Planning Poker Scales: Fibonacci vs Modified Fibonacci
The classic Fibonacci planning poker scale is 1, 2, 3, 5, 8, 13, 21, 34, 55, 89. The modified Fibonacci scale, used by many physical decks and tools, is 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100. It keeps the precise low end but rounds the large values, which signals that big estimates are rough. Both decks usually add “?” (need more information), “∞” (too big to estimate) and a coffee card for breaks. Pick one scale per team and keep it, so velocity stays comparable from sprint to sprint.
Why Fibonacci Works
The Science Behind Fibonacci Estimation
Fibonacci sequence reflects how uncertainty grows with complexity
Prevents False Precision
Fibonacci forces rounded estimates. No debating between 19 vs 20 story points - it's either 13 or 21.
Universal Scale
Industry-standard sequence (1, 2, 3, 5, 8, 13, 21, 34, 55, 89) creates consistency across agile teams worldwide.
Faster Consensus
Limited Fibonacci options (vs 1-100 scale) help teams converge on estimates faster during Planning Poker.
Natural Grouping
Fibonacci naturally clusters stories: Small (1-3), Medium (5-8), Large (13-21), XL (34+).
Velocity Tracking
Fibonacci story points enable accurate velocity calculations for sprint planning and forecasting.
What is Fibonacci Estimation?
Fibonacci estimation is an agile technique where teams estimate story points using the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21, 34, 55, 89. Named after Italian mathematician Leonardo Fibonacci, this sequence appears throughout nature and reflects how humans naturally perceive relative differences.
In agile development, Fibonacci estimation is most commonly used with Planning Poker. Each team member holds Fibonacci cards and votes on story point values privately. The limited options prevent false precision ("Is this story 17 or 18 points?") and help teams converge on estimates faster.
Why Fibonacci Sequence for Story Points?
The Fibonacci sequence has unique mathematical properties that make it perfect for agile estimation:
- Increasing Gaps: As numbers grow (13→21→34), gaps widen to reflect growing uncertainty in larger estimates
- Non-Linear Growth: Fibonacci progresses exponentially, matching how complexity compounds in software
- Limited Options: Only 9-10 choices force quick decisions vs infinite scales like 1-100
- Natural Grouping: Small (1-3), Medium (5-8), Large (13-21) emerge naturally from the sequence
- Avoids Anchoring: No consecutive numbers reduces bias from seeing previous estimates
How to Use Fibonacci Cards in Planning Poker
- Prepare Fibonacci Cards: Each team member gets cards with values 1, 2, 3, 5, 8, 13, 21, 34, 55, 89
- Review User Story: Product Owner presents the story and answers questions
- Private Selection: Everyone picks their Fibonacci card without revealing it
- Simultaneous Reveal: All cards shown at once to prevent anchoring bias
- Discuss Outliers: Team members with highest and lowest Fibonacci values explain their reasoning
- Re-vote: Repeat until team converges on a single Fibonacci story point value
Fibonacci vs Other Estimation Scales
While some teams use linear scales (1, 2, 3, 4, 5...) or T-shirt sizes (XS, S, M, L, XL), Fibonacci estimation remains the most popular for several reasons:
- Better than Linear: Fibonacci reflects uncertainty; linear scales suggest false precision
- More Precise than T-Shirts: Fibonacci provides numerical values for velocity tracking
- Industry Standard: Most agile tools (Jira, Azure DevOps) default to Fibonacci
- Universal Language: Fibonacci is recognized across teams and organizations
Start Fibonacci Estimation with Alignlee
Alignlee provides free Fibonacci estimation with Planning Poker. Create a room in seconds, share the link with your team, and start estimating with Fibonacci sequence cards. Our tool includes all standard Fibonacci values (1, 2, 3, 5, 8, 13, 21, 34, 55, 89) plus additional options like half-point increments and infinity for outlier stories.
No signup required. No credit card. Just instant Fibonacci estimation for your agile team's sprint planning, backlog refinement, and story point sizing sessions.
Related Resources
- Story Points vs Hours - Why story points are not hours
- Planning Poker Tool - Free estimation tool for agile teams
- Printable Planning Poker Cards - Fibonacci and modified Fibonacci card sheets
- Sprint Velocity Calculator - Turn story points into a delivery forecast
- Relative Sizing with Planning Poker - The complete agile estimation guide
- Mastering Relative Sizing - Deep dive into Planning Poker
Ready to Estimate with Fibonacci?
Free Planning Poker with Fibonacci sequence cards. Start your agile estimation session now.