What is Planning Poker?

tl;dr

Everyone picks a card with their estimate. Everyone reveals at once. If the cards disagree, you talk about why — then re-vote. When the cards converge, that's your estimate.

It sounds trivial. The trick is the private vote, simultaneous reveal: nobody anchors on the first person to speak, and any real disagreement actually shows up instead of getting smoothed over.

Where it came from

James Grenning named it in 2002 — he wanted something faster than the Wideband Delphi method (a structured estimation process from 1940s RAND, exactly as ceremonial as it sounds). Mike Cohn put it on the map with his 2005 book Agile Estimating and Planning, and from there it became standard Scrum kit.

The cards usually run a Fibonacci sequence (1, 2, 3, 5, 8, 13, 21…). The gaps grow on purpose. The bigger the work, the less anyone really knows — so the options spread out instead of inviting arguments about whether something's a 9 or a 10.

Why teams use it

• It surfaces hidden disagreement. When one engineer plays a 2 and another plays a 13, you've found a shared-understanding gap. Averaging the two would have hidden it.
• It rewards cross-functional thinking. Designers, QA, and engineers all vote — so the estimate reflects the full cost of shipping, not just the coding.
• It de-escalates seniority. A junior's hidden card counts the same as the lead's. The conversation that follows the reveal is where seniority actually earns its keep.
• It's fast. A focused team can size 10–15 stories in 30 minutes. The estimates also tend to be more honest than the ones you get under social pressure.

You're estimating effort, not hours

Planning Poker estimates relative effort, not time. A story point bundles three things: complexity, uncertainty, and amount of work. A 5 is roughly five times the effort of a 1 — even when nobody can say how many hours either one takes.

That's the whole point. Humans are famously bad at predicting clock time and pretty good at saying "this is bigger than that one." Planning Poker leans into what your team is already good at.

When it's the wrong tool

Planning Poker shines when you need shared understanding, not just a number. If you've got hundreds of items and just need rough sizing, reach for bucket sizing or T-shirts instead. And if your stories are already small and well-understood, you might not need to estimate at all — plenty of teams drift toward "no estimates" once their refinement is sharp.

Ready to try it?

Open a session, paste the link in your team chat, and you'll be running your first round inside two minutes. Want a walkthrough first? Read the facilitator's guide.