How to Use Planning Poker: Complete Guide
Learn how to use planning poker effectively for agile estimation. This comprehensive guide covers everything from setup to advanced techniques, helping your team estimate user stories with confidence and accuracy.
What You'll Learn
Step-by-Step Process
- • Setting up planning poker sessions
- • Presenting user stories effectively
- • Facilitating team discussions
- • Managing the voting process
Best Practices & Tips
- • Common mistakes to avoid
- • Advanced facilitation techniques
- • Handling difficult situations
- • Improving estimation accuracy
Step-by-Step Guide: How to Use Planning Poker
Set Up Your Planning Poker Session
2-3 minutesStart by creating a free planning poker session. No registration required - simply visit our tool, click 'Create Session', and share the unique room link with your team members. Choose your preferred card deck (Fibonacci, T-shirt sizes, or custom values).
Pro Tips:
- Share the session link via Slack, Teams, or email
- Ensure all team members can access the link
- Test audio/video setup if using external conferencing tools
Present the User Story or Task
3-5 minutesThe Product Owner or Scrum Master presents the user story, including acceptance criteria, definition of done, and any relevant context. This is crucial for accurate estimation - everyone needs the same understanding.
Pro Tips:
- Read the user story aloud clearly
- Explain acceptance criteria in detail
- Share any mockups, designs, or technical requirements
- Allow time for questions and clarifications
Clarify Questions and Discuss
5-10 minutesTeam members ask questions about scope, technical approach, dependencies, and potential risks. This discussion phase is essential - don't rush it. Address all concerns before voting begins.
Pro Tips:
- Encourage all team members to ask questions
- Discuss technical complexity and dependencies
- Identify potential risks or unknowns
- Ensure everyone understands the scope
Vote Privately Using Planning Poker Cards
1-2 minutesEach team member selects their estimation card privately. Don't reveal votes yet! This prevents anchoring bias where early votes influence others. Consider effort, complexity, risk, and unknowns when choosing your card.
Pro Tips:
- Think about effort, not time
- Consider complexity and risk factors
- Don't discuss your vote with others yet
- Use the card values consistently across stories
Reveal All Votes Simultaneously
30 secondsOnce everyone has voted, reveal all cards at the same time. This moment often reveals interesting differences in understanding or approach. Don't worry if votes vary widely - that's normal and valuable.
Pro Tips:
- Wait for everyone to vote before revealing
- Note the range of estimates
- Look for patterns in the voting
- Don't judge different estimates negatively
Discuss Differences and Reasoning
5-15 minutesFocus discussion on the highest and lowest estimates. Ask those voters to explain their reasoning. Often, different estimates reveal different understandings of the work or different approaches to implementation.
Pro Tips:
- Ask high and low voters to explain their reasoning
- Listen for different interpretations of requirements
- Discuss technical approaches and complexity
- Identify any missed requirements or risks
Re-vote if Necessary
1-2 minutesAfter discussion, vote again if estimates were widely different. Often, the second vote shows more consensus as understanding improves. If votes are still widely different, consider breaking the story into smaller pieces.
Pro Tips:
- Re-vote if initial estimates varied significantly
- Look for convergence in the second vote
- Consider splitting large or complex stories
- Don't force consensus if fundamental disagreements remain
Record the Final Estimate
1 minuteChoose the final estimate based on team consensus. This might be the most common vote, an average, or a value the team agrees represents the story's complexity. Record this in your backlog management tool.
Pro Tips:
- Aim for consensus, not just averaging
- Record the estimate in your backlog tool
- Note any important assumptions or risks
- Move on to the next story
Common Planning Poker Mistakes to Avoid
Mistake: Discussing estimates before revealing cards
Solution: Always vote privately first to avoid anchoring bias
Mistake: Rushing through story discussion
Solution: Take time to ensure everyone understands the requirements
Mistake: Estimating in hours instead of story points
Solution: Focus on relative complexity, not time duration
Mistake: Forcing consensus too quickly
Solution: Allow healthy debate and multiple voting rounds if needed
Mistake: Including non-development work in estimates
Solution: Estimate only the development effort, not testing or deployment
Planning Poker Best Practices
Keep Sessions Focused
Limit sessions to 1-2 hours maximum. Take breaks every 45 minutes to maintain focus and energy.
Use Consistent Reference Stories
Establish baseline stories that everyone agrees on to help calibrate future estimates.
Include the Right People
Include developers, testers, and anyone who will work on the story. Exclude stakeholders from voting.
Don't Over-Engineer Estimates
Remember that estimates are just that - estimates. Don't spend too much time on precision.
Review and Learn
Regularly review actual effort vs. estimates to improve your team's estimation accuracy over time.
Learn More About Planning Poker
Planning Poker Rules
Understand the complete rules and variations of planning poker for different team sizes and situations.
Read the rules guideFibonacci Planning Poker
Learn why the Fibonacci sequence is the most popular card deck for planning poker estimation.
Learn about FibonacciPlanning Poker Benefits
Discover the key benefits of using planning poker for agile estimation and team collaboration.
Explore the benefitsFree Planning Poker Tool
Try our free online planning poker tool with your team. No signup required, instant access.
Frequently Asked Questions
How long should a planning poker session take?
A typical planning poker session should take 15-20 minutes per user story. For a full sprint planning session with 10-15 stories, plan for 2-4 hours with breaks. Keep individual story discussions focused and time-boxed.
What if team members have very different estimates?
Large differences in estimates are normal and valuable! They often reveal different understandings of the requirements or different technical approaches. Focus discussion on the highest and lowest estimates, then re-vote after clarification.
Should we estimate in hours or story points?
Use story points, not hours. Story points represent relative complexity and effort, while hours can vary greatly between team members and are harder to estimate accurately. Story points also account for uncertainty and risk better than time estimates.
Ready to Try Planning Poker?
Start using planning poker with your team today. Our free tool requires no signup and works perfectly for remote and in-person teams.