Fibonacci Sequence in Agile Estimation: Why It Works (2026 Guide)

The Fibonacci sequence (0, 1, 1, 2, 3, 5, 8, 13, 21, 34…) is the de facto standard in agile estimation. But why is this ancient mathematical sequence perfect for estimating modern software?

What is the Fibonacci Sequence?

The Fibonacci sequence is a mathematical series where each number is the sum of the two preceding ones:

0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144...

Formula: F(n) = F(n-1) + F(n-2)

In agile estimation, a modified version is used:

0, 1, 2, 3, 5, 8, 13, 20, 40, 100

Note: 21 is replaced by 20, 34 by 40, and 100 is added for very large tasks.

Why Fibonacci is Perfect for Estimation

1. Reflects Growing Uncertainty

The difference between small numbers is small (2 vs 3 = difference of 1), but between large numbers is huge (13 vs 21 = difference of 8).

This reflects reality:

• Small tasks: We can accurately estimate the difference between 2 and 3 days
• Large tasks: It’s impossible to precisely distinguish between 13 and 14 weeks

2. Avoids False Precision

Imagine you have these options:

❌ Linear scale: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

• What’s the real difference between a 6 and a 7?
• Can you really be that precise?

✅ Fibonacci: 1, 2, 3, 5, 8, 13

• The gap forces you to think: “Is it a 5 or really an 8?”
• You don’t waste time debating 6 vs 7

3. Forces Conversation

When someone votes 3 and another person votes 8, it’s a clear signal they see the problem differently.

Real example:

Story: "As a user, I want to reset my password via email"

Developer A: votes 3
- "It's just sending an email with a token, 30 minutes"

Developer B: votes 8
- "Wait, do we have email service configured?"
- "What if the email doesn't arrive?"
- "Do we need token expiration?"
- "What if someone tries to reset 100 times?"

This discrepancy revealed hidden work. Without Fibonacci, they might have voted 4 and 5, hiding the disagreement.

How to Use Fibonacci in Planning Poker

Step 1: Establish Reference Stories

Before estimating, define concrete examples for each value:

Points	Example Story	Complexity
1	Change button text	Trivial
2	Add a field to existing form	Very simple
3	Create basic REST endpoint	Simple
5	Implement complex form validation	Moderate
8	Integrate external payment service	Complex
13	Migrate database with existing data	Very complex
20	Redesign authentication architecture	Extremely complex

Step 2: Estimate Relatively

Don’t estimate in hours. Estimate by comparing with your references:

New story: "Implement search with filters"

Correct thinking:
"This is more complex than adding a field (2),
but less than integrating payment (8).
Seems similar to complex validation (5).
I vote 5."

Wrong thinking:
"This will take 3 days × 8 hours = 24 hours.
There's no 24 in Fibonacci, I vote 20."

Step 3: Use the Gap to Detect Risks

When there’s significant disagreement (e.g., 3 vs 13), ask:

• To the low voter: “What assumptions are you making?”
• To the high voter: “What risks do you see that others don’t?”

Step 4: Don’t Force Artificial Precision

If most vote 5 but someone votes 8, don’t average to 6.5. Fibonacci doesn’t have 6.5 for a reason.

Options:

1. Discuss and vote again
2. Take the higher value (precautionary principle)
3. If discrepancy persists, split the story

Fibonacci vs Other Scales

Fibonacci vs Linear (1-10)

Aspect	Fibonacci	Linear
Precision in large numbers	Low (correct)	High (false)
Estimation speed	Fast	Slow (much debate)
Reflects uncertainty	Yes	No
Facilitates consensus	Yes	No

Fibonacci vs Powers of 2 (1, 2, 4, 8, 16)

Powers of 2:

• ✅ Mathematically simple
• ✅ Doubles each time
• ❌ Gap too large between medium values (4 to 8)

Fibonacci:

• ✅ More natural progressive gap
• ✅ More options in medium range (3, 5, 8, 13)
• ❌ Not power of 2 (less mathematically obvious)

Verdict: Fibonacci is superior for most teams because the gap grows more gradually.

Fibonacci vs T-Shirt Sizing (XS, S, M, L, XL)

T-Shirt:

• ✅ More intuitive for beginners
• ✅ Less intimidating (doesn’t require understanding math)
• ❌ Doesn’t allow numerical velocity calculations
• ❌ Difficult for reports and projections

Fibonacci:

• ✅ Allows precise velocity calculations
• ✅ Facilitates projections and roadmaps
• ❌ Initial learning curve

Verdict: Use T-Shirt for initial backlog estimates. Switch to Fibonacci when the team matures.

Special Values in Agile Fibonacci

0 - Zero

When to use:

• Trivial changes (typo in documentation)
• Work already completed
• Configuration that literally takes 5 minutes

Caution: Don’t abuse 0. If something requires code review, it’s probably at least 1.

1 - One

When to use:

• Very simple changes anyone can do
• Less than 1 hour of work
• No technical uncertainty

Example: Change a hexadecimal color in CSS.

100 - Epic

When to use:

• Story too large to estimate accurately
• Signal that it should be split

Action: Don’t accept a 100 in a sprint. Split the story.

? - Question Mark

When to use:

• You don’t have enough information
• There’s too much technical uncertainty

Action: Product Owner should clarify or team should do a spike (timeboxed investigation).

∞ - Infinity

When to use:

• The task is impossible to complete with current resources
• There are insurmountable technical blockers

Action: Reject the story or completely redefine it.

Best Practices

1. Start simple: Use only 1, 2, 3, 5, 8 until the team feels comfortable.

2. Keep visual references: Have examples of previous stories visible during Planning Poker.

3. Review accuracy: Each retrospective, compare estimates with actual effort. Not to punish, but to learn.

4. Don’t convert to hours: The points-to-hours ratio varies by task. Resist pressure to create a conversion table.

5. Accept the range: A 5 can take 4-16 hours. That’s normal. Fibonacci doesn’t eliminate uncertainty, it acknowledges it.

Conclusion

Fibonacci isn’t magic, it’s mathematics that reflects human reality: we’re good at estimating relative comparisons, bad at estimating absolute values.

By forcing gaps between numbers, Fibonacci forces us to think categorically (“is it small, medium, or large?”) instead of falsely precise (“is it 6.2 or 6.7 days?”).

Start Using Fibonacci Today

Create a Planning Poker session with Fibonacci pre-configured. No registration, no installation.

Related Resources

• Complete Planning Poker Guide
• T-Shirt Sizing: When to Use Sizes Instead of Numbers
• Calculating and Improving Team Velocity