Planning Poker Rules: Complete Guide to Scrum Estimation
Master the complete planning poker process with our comprehensive guide covering rules, best practices, and common pitfalls to avoid for effective agile estimation.
Planning poker is a consensus-based estimation technique used in agile development to estimate the effort required for user stories. By following these proven rules and best practices, your team can achieve more accurate estimates while building shared understanding of the work ahead.
The 5 Essential Planning Poker Rules
Prepare the Session
Set up your planning poker session with the right participants and materials
- Gather the development team, product owner, and scrum master
- Choose appropriate card deck (Fibonacci, T-shirt sizes, or custom)
- Prepare user stories with clear acceptance criteria
- Set up the planning poker tool or physical cards
Present the Story
Ensure everyone understands what needs to be estimated
- Product owner reads the user story aloud
- Clarify acceptance criteria and definition of done
- Answer any questions about scope or requirements
- Discuss technical considerations and dependencies
Individual Estimation
Each team member makes their estimate privately
- Team members select their cards without revealing them
- Consider complexity, effort, and uncertainty
- Base estimates on team's historical velocity
- Don't discuss estimates until everyone has voted
Reveal and Discuss
Show all estimates simultaneously and discuss differences
- All participants reveal their cards at the same time
- Identify the highest and lowest estimates
- Ask estimators to explain their reasoning
- Focus on understanding different perspectives
Re-estimate if Needed
Continue until the team reaches consensus
- If estimates vary significantly, discuss and re-vote
- Aim for consensus, not perfect agreement
- Record the final estimate for the story
- Move on to the next story
Planning Poker Best Practices
Right Team Composition
Include developers, testers, and anyone who will work on the story
Time Management
Limit discussion time to avoid analysis paralysis (2-3 minutes per story)
Focus on Relative Sizing
Compare stories to previously estimated work rather than absolute time
Encourage Discussion
Use estimation differences as opportunities to uncover hidden complexity
Common Planning Poker Mistakes to Avoid
Mistake: Averaging estimates without discussion
Solution: Always discuss outlier estimates to understand different perspectives
Mistake: Estimating in hours instead of story points
Solution: Use relative sizing with story points to avoid time-based anchoring
Mistake: Allowing dominant voices to influence others
Solution: Ensure everyone votes simultaneously before any discussion
Mistake: Over-analyzing every story
Solution: Set time limits and accept that some uncertainty is normal
Mistake: Including non-development tasks in estimates
Solution: Only estimate development effort, not meetings or documentation
Choosing the Right Card Deck
The choice of estimation scale significantly impacts your planning poker sessions. Here are the most effective options:
Fibonacci Sequence
1, 2, 3, 5, 8, 13, 21
Best for most teams. The increasing gaps reflect growing uncertainty in larger estimates.
T-Shirt Sizes
XS, S, M, L, XL, XXL
Great for high-level estimation and teams new to relative sizing concepts.
Powers of 2
1, 2, 4, 8, 16, 32
Useful for technical teams familiar with binary concepts and exponential complexity.
Advanced Planning Poker Techniques
The "Planning Poker Moderator" Role
Designate a moderator (usually the Scrum Master) to guide the session, keep discussions focused, and ensure everyone participates. The moderator should not estimate to maintain neutrality.
Using Reference Stories
Establish baseline stories of known sizes (e.g., "This 3-point story is similar to the login feature we built last sprint"). Reference stories help maintain consistency across estimation sessions.
The "Parking Lot" Technique
When discussions go off-topic or reveal new requirements, write them in a "parking lot" to address later. This keeps estimation sessions focused while capturing important insights.
Handling Large Stories
If a story receives estimates of 13+ points, consider breaking it down into smaller, more manageable pieces. Large stories are harder to estimate accurately and complete within a sprint.
Frequently Asked Questions
What are the basic planning poker rules for beginners?
Planning poker rules are simple: 1) Present a user story, 2) Each team member privately selects an estimate card, 3) Reveal all cards simultaneously, 4) Discuss any significant differences, 5) Re-vote if needed until consensus is reached. The key rule is that no estimates are shared until everyone has voted to prevent bias.
How long should planning poker sessions last?
Planning poker sessions should typically last 1-2 hours maximum. Spend 2-3 minutes per story on average - 1 minute for presentation, 1-2 minutes for discussion if needed. If a story takes longer than 5 minutes to estimate, consider breaking it down into smaller pieces.
What happens when planning poker estimates are very different?
When estimates vary significantly (e.g., 2 vs 13), ask the highest and lowest estimators to explain their reasoning. Often, different estimates reveal different assumptions about scope, complexity, or approach. Use this discussion to align understanding, then re-vote. Don't just average the numbers.
Can planning poker be used for tasks other than user stories?
Yes, planning poker rules can be applied to estimate any work items including bugs, technical tasks, spikes, or epics. The key is that the work should be development-related and benefit from team input. Avoid using it for administrative tasks or meetings.
What should you do if team members consistently give different estimates?
Consistent estimation differences often indicate different understanding of requirements, technical approach, or team capabilities. Address this by improving story clarity, ensuring shared technical knowledge, and calibrating estimates against completed work. Consider pair programming or knowledge sharing sessions.
Are there any planning poker rules for remote teams?
Remote planning poker follows the same basic rules but requires additional considerations: use digital tools for card selection, ensure everyone can see and hear clearly, be more explicit about when to vote and reveal, and allow extra time for discussion due to communication delays.
Related Guides
Ready to Start Planning Poker?
Put these concepts into practice with our free online planning poker tool.
Create Free SessionExplore More.
Discover related content to enhance your planning poker knowledge and improve your team's estimation process.