What Is Scrum Poker? How It Works & How to Run It Online
Scrum poker is an agile estimation technique where team members simultaneously reveal numbered cards to vote on the effort required for a user story. The simultaneous reveal prevents anyone from anchoring on someone else's number before they've formed their own opinion — which is the entire reason the technique works. If you've seen it called planning poker, that's the same thing. The two terms are used interchangeably. Scrum poker is the more common name in teams that follow the Scrum framework specifically; planning poker is the original term coined by James Grenning in 2002. Same cards, same rules, same simultaneous reveal. This guide covers how scrum poker works, why it produces better estimates than top-down guessing, and how to run sessions online with a distributed team.
Scrum poker vs planning poker: is there a difference?
Not in practice. Both terms describe the same estimation ceremony: a facilitator presents a story, the team discusses it briefly, everyone picks a card privately, and all cards are revealed at once. The conversation that follows a divergent reveal is where the value comes from. The name "planning poker" comes from Mike Cohn's popularization of the technique in his book Agile Estimating and Planning. "Scrum poker" emerged as teams running the Scrum framework started using the technique in sprint planning and named it after the methodology they were practicing. Most online tools use both terms — they're targeting the same audience.
How scrum poker works
A scrum poker session follows five steps. Each step exists for a specific reason.
1. Present the story.
The product owner reads a user story or backlog item aloud. Team members can ask clarifying questions — what's in scope, what's out of scope, what does "done" look like. Keep this to two or three minutes. The goal is shared understanding, not a full design session.
2. Estimate privately.
Each team member selects a card representing their effort estimate without showing anyone else. In a remote session, each person picks a value that stays hidden until the facilitator triggers the reveal. No announcing numbers, no thinking out loud.
3. Reveal simultaneously.
All cards flip at the same moment. This is the most important rule. Simultaneous reveal eliminates anchoring bias — the tendency to adjust your estimate toward the first number you hear rather than forming an independent judgment. If one person reveals before the others, the exercise loses most of its value.
4. Discuss divergence.
If estimates cluster tightly, take the consensus and move on. If there's a meaningful spread — say a 3 and a 13 on the same story — the highest and lowest estimators explain their reasoning. This isn't a negotiation. It's a knowledge transfer. One of them knows something the other doesn't.
5. Re-vote and finalize.
After the discussion, vote again. One or two rounds is usually enough to reach consensus. Record the agreed estimate and move to the next story.
Why scrum poker produces better estimates
The research on group estimation consistently shows that independent, simultaneous estimates beat sequential ones. When people announce estimates one at a time, every estimate after the first is influenced by what was said before. The result is artificial clustering — not real agreement, just anchoring. Scrum poker forces independence at the moment that matters: when each person commits to a number. The reveal makes that commitment visible. Whoever sees a spread after the flip knows the disagreement is real, not social. That's what triggers the useful conversation. The Fibonacci-like sequence (1, 2, 3, 5, 8, 13, 21) reinforces this by making false precision impossible. You can't estimate 11 points when the scale doesn't have 11. The gaps between large numbers force estimators to make a judgment call — is this story more like an 8 or more like a 13 — rather than anchoring on a specific number.
Running scrum poker online
Remote and distributed teams have been running scrum poker online for years, and in some ways the online format enforces the rules better than physical cards. A well-built online tool hides every vote until the facilitator triggers the reveal — there's no accidental early flip, no card visible in someone's hand before everyone is ready. What to look for in an online scrum poker tool:
No signup required.
Sprint planning already has enough overhead. A tool that requires every participant to create an account before the session can start adds friction to every single sprint. The facilitator should be able to create a room, share a link, and have the team voting within 30 seconds.
Facilitator-controlled reveal.
The reveal should be triggered by one person — the facilitator — not happen automatically when the last vote comes in. Auto-reveal removes the facilitator's ability to confirm everyone is ready before the cards flip.
Works on phones.
Remote teams don't all sit at desks. If the tool requires a laptop or doesn't work well on a phone screen, you've excluded part of your team before the session starts.
Live vote status without showing values.
You should be able to see who has voted and who hasn't — without seeing what they voted. A progress indicator that shows "5 of 7 voted" lets the facilitator nudge stragglers without breaking the hidden-vote rule.
Common mistakes that undermine scrum poker
Teams that abandon scrum poker usually do so because of process errors, not because the technique is flawed.
Skipping the discussion when estimates diverge.
Averaging a 3 and a 13 gives you an 8 that nobody believes in. The whole point of the divergent reveal is to surface the conversation. If you skip it, you've run the ceremony without capturing the value.
Letting the product owner vote.
The product owner defines the requirements and should answer clarifying questions, but their vote creates a conflict of interest. Team members who see a 2 from the product owner before they've formed their own estimate will adjust toward it.
Using it for stories that are already fully understood.
Scrum poker adds value when there's meaningful uncertainty. If a story is a three-line config change that every engineer on the team understands completely, voting on it wastes five minutes. Reserve the ceremony for stories where disagreement is possible.
How to get started
For co-located teams, a physical deck of cards works fine. For remote or hybrid teams, you need an online tool. PointPoker is free, requires no signup, and works on any device. The facilitator creates a room, shares the link, and the team can start voting in seconds. The simultaneous reveal is facilitator-controlled, live vote progress is visible without showing values, and sessions support Fibonacci, T-Shirt, and custom card scales. No account needed to join.
Run your first scrum poker session free
No signup, no credit card. Your team is voting in under 30 seconds.
Start a Free Session