0, 1, and 2 points
Use these for tiny or well-understood work. If a story is repeatedly estimated as zero, ask whether it is really a task, a dependency, or already done.
FreeScrumPokerA Fibonacci scale gives teams enough precision for small work and enough distance between large numbers to admit uncertainty. Use it as a decision aid, not a substitute for splitting unclear stories.
The labels are less important than shared calibration. Keep a few reference stories nearby so the team can compare new work to completed examples.
Use these for tiny or well-understood work. If a story is repeatedly estimated as zero, ask whether it is really a task, a dependency, or already done.
These are common sprint-ready sizes. The work has some implementation detail, but the team can explain the likely path and acceptance criteria without much uncertainty.
Use larger values when scope, unknowns, or coordination risk increase. A repeated 13 is often a signal to split the story before sprint commitment.
Treat 21 as a warning label, not a comfortable commitment. It usually means the team should identify slices, spikes, or acceptance-criteria gaps.
The question mark is useful when the voter lacks enough information to estimate responsibly. Discuss the missing detail before forcing a number.
Coffee is a humane pause card. Use it when people need a break, the story discussion is drifting, or the group has hit meeting fatigue.
The gaps help teams express uncertainty. Large work rarely deserves exact-looking numbers, so the wider spacing nudges teams toward discussion and splitting.
No. Some teams cap the deck at 13 to force earlier splitting. Use the highest value that supports useful decisions without normalizing oversized stories.
Yes. FreeScrumPoker supports custom decks when your team needs different labels or wants to remove values that create poor planning habits.