An estimation session disguised as a card game. Spoiler: it's far more effective than a spreadsheet.
The concept in two words
Planning Poker (also known as Scrum Poker) is a collaborative estimation technique used by agile teams. The idea: every team member votes simultaneously on the complexity of a user story using numbered cards.
The simultaneous reveal prevents anchoring — no one is influenced by anyone else's estimate. When the cards diverge, the team discusses, and a new round of voting follows. The process repeats until consensus.
Why it works
- Independent thinking: each participant forms their own opinion before exposure to others.
- Productive discussion: extreme estimates surface hidden assumptions, missing information, or differing interpretations.
- Fast convergence: typically 1 to 3 rounds per story are enough to reach consensus.
- Engagement: the game format keeps the team focused and turns a tedious task into something playful.
How to run a session
- The Product Owner presents a user story from the backlog.
- The team asks clarifying questions.
- Each participant silently picks a card matching their estimated effort.
- All cards are revealed at the same time.
- If estimates diverge, the people with the extreme values explain their reasoning.
- The team votes again. Repeat until consensus.
What about story points?
Story points represent relative effort, not time. A 5-point story is roughly five times as much work as a 1-point story — that's it. Tying points to hours kills the technique's main benefit: comparing stories rather than forecasting durations.
Common pitfalls
- Average to break ties: never average estimates. The point is consensus, not arithmetic.
- Skipping the discussion: silent rounds in a row don't generate value. Always discuss outliers.
- Estimating in absentia: only people who will work on the story should vote.
- Letting it drag: 1 minute per story is a healthy target. If you're stuck, the story probably needs to be broken down.
In summary
Planning Poker is a simple tool, but its power lies in what surrounds it: alignment, knowledge sharing, and forming a team-wide mental model of upcoming work. Used well, it makes your sprint planning faster and more accurate.