Estimating work in Agile projects can be tricky. Different people have different experiences, and bias can easily creep in.
That’s where Planning Poker comes in—a simple, effective technique that helps teams estimate more accurately, collaboratively, and consistently.
In this post, we’ll break down how it works, why it helps, and how to run a session.
What Is Planning Poker?
Planning Poker is an estimation game used in Agile projects. Team members assign effort estimates to tasks using numbered cards (often based on the Fibonacci sequence).
It helps:
- Avoid anchoring bias
- Encourage discussion
- Reach consensus through structured disagreement
When to Use It
Use Planning Poker when estimating:
- User stories during backlog grooming
- Tasks in sprint planning
- New feature ideas
The Basic Process
Here’s how a typical Planning Poker session works:
Step 1: Choose a Story
Select one item from the backlog. Keep it small enough to estimate in under 10 minutes.
Step 2: Clarify the Work
The Product Owner explains the story. The team can ask questions, clarify requirements, and identify unknowns.
Step 3: Everyone Chooses a Card
Each team member picks a card (privately) with a number representing their estimate. Common scale: 1, 2, 3, 5, 8, 13, 20, etc.
Step 4: Reveal Cards Together
All estimates are revealed at the same time. This avoids influence from early answers.
Step 5: Discuss Differences
If estimates vary widely:
- Ask the highest and lowest to explain
- Discuss assumptions and risks
- Re-estimate after the discussion
Step 6: Reach Consensus
Repeat the process until the team agrees on a number—or gets close enough.
Why It Works
- Democratizes input – everyone has a voice
- Exposes uncertainty – through conversation
- Improves shared understanding – reduces surprises in development
Tips for Better Sessions
- Keep it focused—don’t estimate too many items at once
- Timebox discussions to avoid analysis paralysis
- Rotate facilitators to keep things fresh
- Use online tools like PlanningPoker.com or ScrumPoker
Common Pitfalls
- Rushing through discussions
- Letting one voice dominate
- Using it for tasks that are too large or vague
Summary: Better Estimates, Better Sprints
Planning Poker helps teams talk through their work, surface hidden assumptions, and come to shared agreements. It’s not just about the number—it’s about the conversation.
Try it in your next planning session. You might be surprised at how much clarity it brings.