Why the card sequence matters
An estimation scale shapes the conversation. Closely spaced values invite fine distinctions, while values that spread out encourage the team to acknowledge uncertainty. No sequence is universally correct. A useful deck is one that your team understands, applies consistently, and can use without spending more time debating numbers than discussing the work.
Fibonacci-style deck
0 · 1 · 2 · 3 · 5 · 8 · 13 · 21 · ?
The Fibonacci-style sequence creates larger gaps as work becomes bigger. It is a strong default for backlog refinement because the growing gaps reflect a practical truth: people are less able to distinguish precisely between large, uncertain items. If one item feels like a 13 or 21, the most useful next step is often to split or investigate it rather than search for a more exact number.
Ordinal sequence
0 · 1 · 2 · 3 · 4 · 5 · 6 · 7 · ?
The ordinal sequence offers evenly spaced choices. It works well when a team has a stable shared reference for each level and regularly needs to distinguish between adjacent sizes. Because every step looks equally precise, facilitators should watch for false confidence on large or poorly understood items.
Ordinal sequence with decimals
0 · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8
0.5 · 1.5 · 2.5 · 3.5 · 4.5 · 5.5 · 6.5 · 7.5 · ?
The decimal ordinal sequence adds half steps between whole-number estimates. It can help teams whose work items are already small and consistently prepared, or teams that use an established scoring model requiring those distinctions. It is usually a poor fit when requirements are broad or uncertain, because extra choices can make an estimate look more accurate than the available information supports.
What the special cards mean
- 0
- The item requires negligible effort, is already complete, or should not be estimated as meaningful work.
- ?
- The voter cannot estimate yet because important information is missing. Treat it as a request for clarification.
How to select a deck as a team
Start with the simplest sequence that supports your decisions. Use the same deck for several sessions, then review whether it creates useful conversations. If adjacent values repeatedly lead to debates with no planning impact, simplify the scale. If the team frequently needs a meaningful choice between two existing values, consider a more detailed ordinal deck.
Whichever deck you choose, keep a few reference items that the team understands well. Comparing new work with those examples is more reliable than trying to define each number in isolation. For the full session workflow, read the planning poker guide.