What is planning poker?
Planning poker is a consensus-based estimation technique used by agile software teams to gauge the relative effort of backlog items. During a session, each team member privately selects a numbered card that represents their estimate. All cards are revealed at the same time, preventing any single voice from anchoring the group.
The technique was first described by James Grenning in 2002 and later popularized by Mike Cohn in his book Agile Estimating and Planning. It builds on the Wideband Delphi method, combining expert opinion with structured discussion to produce more accurate forecasts.
Most teams run planning poker during sprint planning or backlog refinement. The product owner presents a user story, the team discusses it briefly, and then everyone votes. If estimates diverge, a short discussion follows before the team re-votes. The result is a shared understanding of the work ahead and a story-point value the whole team stands behind.
How a planning poker session works
Five repeatable steps that turn backlog items into shared estimates.
Present the story
The product owner reads the user story or backlog item aloud and answers any initial questions from the team.
Discuss as a team
The team asks clarifying questions, discusses acceptance criteria, and identifies risks or unknowns before voting.
Vote privately
Each team member privately selects a card representing their effort estimate. Votes stay hidden until everyone has chosen.
Reveal all votes
All cards are flipped simultaneously so no one is influenced by others. The group sees the full spread of estimates at once.
Discuss and converge
If estimates differ, the highest and lowest voters explain their reasoning. The team re-votes until consensus is reached.
Why agile teams use planning poker
The technique solves common estimation pitfalls and improves sprint predictability.
Reduces anchoring bias
Simultaneous voting prevents senior voices from anchoring the group. Every estimate is independent.
Surfaces unknowns early
Large estimation gaps reveal misunderstood requirements or hidden complexity before work begins.
Builds team consensus
Discussion rounds align the team on scope, assumptions, and effort so everyone shares the same understanding.
Fast and focused
Time-boxed rounds keep sessions productive. Most stories are estimated in under two minutes.
Inclusive for all roles
Developers, testers, designers, and product owners all vote equally, bringing diverse perspectives to each estimate.
Scales to any team size
Whether your team has three people or twenty, the technique works the same way and keeps everyone engaged.
Common estimation scales
Choose the scale that fits your team's workflow and comfort level.
Fibonacci
0, 1, 2, 3, 5, 8, 13, 21
The classic sequence where gaps between numbers grow as complexity increases, discouraging false precision on large items.
Modified Fibonacci
0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100
Adds half-point and higher values for finer granularity on small items and broader ranges for epics.
T-Shirt Sizes
XS, S, M, L, XL
A non-numeric scale that works well for early-stage estimation or teams new to relative sizing.
Running planning poker with remote teams
Planning poker was originally played with physical cards in a conference room, but modern distributed teams need a digital alternative. Online tools replicate the full experience: private voting, simultaneous reveal, built-in timers, and automatic statistics.
With Scrum Poker, your team can create a room in seconds, invite participants with a shared link, and start estimating immediately. There is no sign-up required for participants, and sessions sync in real time across all devices.
Remote planning poker sessions also produce a natural record of estimates and discussion points, making it easier to track velocity trends over time and refine your estimation accuracy sprint after sprint.
Frequently asked questions
Planning poker was first described by James Grenning in 2002 and later popularized by Mike Cohn in his book Agile Estimating and Planning. The technique builds on the Wideband Delphi estimation method.
A typical session takes 30 to 60 minutes depending on the number of items to estimate. Most teams can estimate 8 to 15 user stories in a single session with experienced participants.
When estimates differ significantly, the highest and lowest voters explain their reasoning. The team discusses the story further, then re-votes. This process continues until the team reaches consensus, usually within 2 to 3 rounds.
Yes. While planning poker originated in software development, any team estimating relative effort can use it. Marketing teams, design teams, and operations teams have all adapted the technique for project planning.
No. While physical card decks exist, online tools like Scrum Poker let your team vote digitally in real time. This is especially useful for remote and distributed teams.
Continue reading
More guides on agile estimation and team practices.
Planning poker vs T-shirt sizing
Compare planning poker and T-shirt sizing estimation methods. Learn the pros, cons, and when to use each technique.
Read guideEstimating user stories
A practical guide to estimating user stories using story points. Learn the process, common scales, and mistakes to avoid.
Read guideStory points vs hours
Should your team estimate in story points or hours? Compare both approaches and learn when each method works best.
Read guide