In Agile delivery, estimating work can easily become slow, political or dominated by the loudest voice in the room. Planning Poker is a simple but powerful technique designed to make estimation collaborative, balanced and data-informed.
Originally popularised within Scrum teams and described in Mike Cohn’s book Agile Estimating and Planning, Planning Poker is now widely used across Agile and product teams to estimate effort using story points rather than time.
What Is Planning Poker?
Planning Poker is a consensus-based estimation technique used to estimate the relative effort of user stories or pieces of work.
It combines three key principles:
- Independent thinking
- Simultaneous voting
- Structured discussion
The goal is not perfect accuracy — it is shared understanding.
Why Use Planning Poker?
Planning Poker works because it:
- Prevents anchoring (where the first estimate influences everyone else)
- Encourages quieter team members to contribute
- Surfaces hidden assumptions
- Promotes shared ownership of estimates
- Improves understanding of requirements
The discussion that happens between votes is often more valuable than the number itself.
How Planning Poker Works (Step by Step)
1️⃣ Prepare the Backlog
Ensure user stories are:
- Clearly written
- Small enough to estimate
- Understood at a high level
Ambiguous or oversized stories should be refined before estimation.
2️⃣ Choose a Scale
Most teams use a Fibonacci sequence:
1, 2, 3, 5, 8, 13, 21
The increasing gaps reflect growing uncertainty as complexity increases.
Some teams also include:
- 0 (no effort)
- ? (unclear)
- ☕ (needs a break!)
3️⃣ Present the Story
The Product Owner (or facilitator) reads the story and answers clarification questions.
The team discusses:
- Scope
- Assumptions
- Dependencies
- Risks
But avoids jumping straight to estimates.
4️⃣ Vote Simultaneously
Each team member selects a card representing their estimate.
All cards are revealed at the same time.
This prevents bias and groupthink.
5️⃣ Discuss Differences
If estimates vary significantly:
- Ask the highest and lowest estimators to explain their reasoning.
- Explore assumptions or misunderstandings.
- Clarify acceptance criteria if needed.
The team then re-votes.
Repeat until consensus or near-consensus is reached.
6️⃣ Record the Final Estimate
Once aligned, the agreed story point value is recorded and the team moves on.
What Makes Planning Poker Successful?
✔ Keep the Team Small and Relevant
Include only those who will actually deliver the work (typically 3–9 people).
✔ Focus on Relative Sizing
Compare stories to one another rather than trying to convert points into hours.
✔ Encourage Psychological Safety
Everyone’s input matters. Avoid judgement around estimates.
✔ Timebox Discussions
If debate runs long, the story likely needs refinement.
✔ Use a Baseline Story
Agree on a “reference” story (e.g., “This is a 3”) to anchor future comparisons.
Common Mistakes to Avoid
- Turning it into a negotiation
- Allowing senior voices to dominate
- Estimating tasks instead of user stories
- Converting story points directly into hours
- Skipping discussion to “save time”
Planning Poker is about alignment, not speed.
When Should You Use It?
Planning Poker works best when:
- Teams are estimating for Sprint Planning
- Work is moderately complex
- Cross-functional collaboration is needed
- Shared understanding is critical
It is less useful for trivial or extremely large pieces of work.
Final Thoughts
Planning Poker is more than a card game — it is a structured conversation about effort, risk and complexity. When run well, it strengthens collaboration, improves predictability and builds collective ownership of delivery commitments.
If your team struggles with inconsistent estimates or disengaged planning sessions, Planning Poker can be a simple yet transformative practice to introduce.
