Planning Poker Fibonacci Scale Explained

The Fibonacci scale is the most common scoring system in planning poker because it reflects how uncertainty grows with complexity. As stories get larger, our confidence drops, so the gaps between numbers widen. This page explains why the scale works, how to use it, and how to avoid common misunderstandings when your team adopts it.

Why Fibonacci fits estimation

Small tasks are easy to compare, so tight numbers like 1, 2, and 3 make sense. As work becomes larger, estimation is less precise, and the Fibonacci sequence naturally creates bigger gaps. That spacing prevents false precision and keeps the team honest about uncertainty.

The sequence also encourages discussion. If someone votes 13 and another votes 5, the difference signals real risk or missing context. The scale becomes a conversation trigger rather than a math problem, which is exactly what planning poker is designed to do.

How the scale reduces false precision

Teams often get stuck debating whether a story is a 6 or a 7. The Fibonacci scale removes those micro‑differences and asks a simpler question: is this closer to 5 or 8? That shift reduces time spent on tiny disagreements and keeps estimation focused on relative size.

When you see a large spread, it is a signal to clarify scope or split the work. The scale is not about picking the perfect number; it is about converging on a shared understanding of effort and risk.

How to apply Fibonacci in practice

Start with a baseline story that the team knows well. Agree on its size and use that reference for new items. Encourage each person to compare the new story against the baseline rather than guessing in isolation. Over time the team builds a stable internal scale.

If the team consistently argues between two values, use the bigger number. It is safer to acknowledge uncertainty than to underestimate. That bias toward caution makes sprint planning more reliable and reduces carry‑over work.

• Use 1, 2, 3 for small, well‑known tasks.
• Use 5 or 8 for medium items with some uncertainty.
• Use 13 or 21 for large items that should likely be split.
• Use a “?” card when you truly lack information.
• Recalibrate with a baseline story every few sprints.

When to adjust the scale

Some teams prefer a shortened sequence like 1, 2, 3, 5, 8, 13. That can be useful for smaller backlogs or new teams. The key is not the exact numbers but the widening gaps. Adjust the scale only if it improves clarity, not because the team is uncomfortable with larger numbers.

If your work consistently lands above 13, it is a signal to split stories, not to extend the scale. Large numbers often hide complexity and create sprint planning surprises later.

Common pitfalls

Avoid converting points to hours. The Fibonacci scale is relative sizing, not a time estimate. If you map points to hours, you lose the benefits of uncertainty and end up with a false sense of precision.

Another pitfall is letting one person define the scale. Planning poker works when the team owns the numbers. Keep the scale consistent, discuss differences, and make sure everyone participates in the calibration.

Home · Planning Poker · Scrum Poker · Agile Estimation · Premium · FAQ