All tools

Planning Poker

Estimate user stories with Fibonacci cards. Pick your card, then reveal all at once to avoid anchoring bias.

Files processed in your browser — never uploaded to our servers

Pick your card

What is Planning Poker?

Planning poker (Scrum poker) is a consensus-based estimation technique where team members simultaneously reveal their story point estimates to avoid anchoring bias. If one person reveals their estimate first, others naturally anchor on that number — simultaneous reveal prevents this and surfaces genuine disagreement. The standard card values follow a Fibonacci-inspired sequence: 0, 1, 2, 3, 5, 8, 13, 20, 40, 100, ?, and infinity. Fibonacci works better than a linear scale because the growing gaps between large numbers reflect genuine estimation uncertainty — a 40-point story is not just twice as complex as a 20-point story, it carries far more unknowns. Story points are a relative unit of effort, not a time unit: a 5-point story is simply understood to be more effort than a 3-point story by however the team defines their scale.

How to use

  1. Add team members who will participate in the estimation session.
  2. Present a user story or task description so all participants understand what is being estimated.
  3. Each team member privately selects their story point estimate from the Fibonacci card deck.
  4. Reveal all estimates simultaneously — this prevents anchoring bias from early influencers.
  5. If estimates are close, accept the consensus or the average and record the final point value.
  6. If estimates diverge widely (e.g. one person picks 3 and another picks 13), ask the highest and lowest estimators to explain their reasoning, then re-vote.

Why it matters

Planning poker surfaces estimation disagreement that would otherwise be hidden. When one developer estimates 3 points and another estimates 13 for the same story, they are operating on different assumptions about scope, technical approach, or risk. That conversation — triggered by the estimate gap — prevents the misalignment that causes sprint failures mid-delivery. Teams that skip estimation or allow one person to dictate estimates routinely discover, mid-sprint, that a story was far larger than assumed. Consensus estimation builds shared understanding of the work before it begins.

Pro tip

If a team cannot reach consensus after 2 rounds of voting, the user story is too large or too unclear to estimate reliably. Split it into smaller stories or spike it — timebox an investigation task to resolve the uncertainty before committing to a point value. A story the team cannot agree on is a story that will fail in the sprint.

Frequently Asked Questions

Planning Poker (or Scrum Poker) is an agile estimation technique where all team members simultaneously reveal their estimate for a story, preventing anchoring bias from early influencers.
Fibonacci numbers (1, 2, 3, 5, 8, 13…) reflect the natural uncertainty in estimation — the larger a task, the less precise the estimate. The growing gaps force the team to acknowledge uncertainty.
The ? card means 'I don't have enough information to estimate.' It signals that the story needs clarification before the team can commit to a point value.
∞ (infinity) means the story is too large or too vague to estimate as-is. It should be broken down into smaller stories before the next sprint.
This version is single-player — useful for a facilitator to collect votes verbally or in a shared screen session. Each team member picks their card, the facilitator records the consensus.
The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21…) represents story points — a relative measure of effort, complexity, and uncertainty rather than hours. Larger numbers have larger gaps to reflect the inherent imprecision of estimating bigger pieces of work.
All team members select their estimate privately and reveal their cards simultaneously. This prevents the first person to speak from anchoring everyone else's judgment. When estimates differ widely, it opens a productive discussion rather than a groupthink consensus.
Planning poker works best with 3 to 8 participants — typically the development team plus the scrum master. Larger groups can participate but the discussion after revealing divergent estimates becomes harder to manage efficiently.
Wide divergence is valuable — it signals a difference in understanding or approach. Ask the highest and lowest estimators to explain their reasoning. Often this surfaces a missing requirement, a technical concern, or a simpler implementation that neither side had considered.
No — any team that needs to estimate relative effort for tasks can use planning poker. Content teams, marketing teams, and operations groups all use it to size projects and prioritize backlogs, even without a formal software development context.