Planning Poker
Agile estimation technique where team members use cards to provide time/effort estimates for tasks anonymously before discussion. Combines individual expertise with team consensus to improve estimation accuracy and reduce anchoring bias.
About this tool
Overview
Planning Poker (also called Scrum Poker) is a consensus-based agile estimation technique where team members use numbered cards to estimate the effort or complexity of user stories or tasks. The method combines expert judgment with team discussion to produce more accurate estimates than individual assessments.
How It Works
The Process:
- Product Owner presents a user story
- Team discusses and asks clarifying questions
- Each member privately selects an estimate card
- All cards revealed simultaneously
- Discuss differences, especially extremes
- Re-estimate until consensus reached
- Record final estimate and move to next story
Card Values:
- Typically uses Fibonacci sequence: 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89
- Also includes: ∞ (too large), ? (unknown), ☕ (break needed)
- Non-linear scale reflects increasing uncertainty
- Can use t-shirt sizes (XS, S, M, L, XL) alternatively
Key Principles
Anonymous Estimation:
- Prevents anchoring bias
- Reduces influence of senior team members
- Encourages independent thinking
- Ensures all voices heard equally
Discussion-Based:
- Divergent estimates trigger conversation
- Surfaces hidden assumptions
- Shares knowledge across team
- Builds shared understanding
- Achieves buy-in through participation
Relative Sizing:
- Estimates are relative, not absolute
- Compare to reference stories
- Focus on complexity, not hours
- Account for unknowns and risk
Benefits
Improved Accuracy:
- Wisdom of crowds effect
- Multiple perspectives reduce blind spots
- Discussion reveals missing information
- Team buy-in improves commitment
Team Building:
- Shared understanding of work
- Knowledge transfer during discussion
- Equal voice for all team members
- Builds estimation capability
Efficiency:
- Faster than detailed individual estimates
- Engages whole team simultaneously
- Identifies items needing breakdown
- Creates shared baseline
Best Practices
- Time-box discussions (2-5 minutes per story)
- Focus on largest estimate discrepancies
- Have team re-estimate, not average cards
- Use reference stories for calibration
- Break down stories estimated > 13
- Track velocity to improve accuracy over time
- Don't convert points directly to hours
Common Variations
- Async Planning Poker: Digital tools for distributed teams
- Quick Poker: Simplified for time-sensitive situations
- Modified Fibonacci: Different number sequences
- Affinity Estimation: Group similar stories first
Tools
- Physical card decks
- PlanningPoker.com
- Scrum Poker apps
- Zoom/Teams integrations
- Jira Planning Poker plugin
Use Cases
- Sprint planning in Scrum
- Backlog refinement
- Project estimation
- Capacity planning
- Risk assessment
Loading more......
Information
Categories
Tags
Similar Products
6 result(s)Short 15-minute daily meeting in agile methodologies where team members synchronize work, discuss progress toward sprint goals, and identify blockers. Promotes collaboration, transparency, and quick problem resolution.
A relative estimation method in Agile that measures complexity, effort, and risk rather than time, using techniques like Planning Poker and tracking team velocity for predictable sprint planning.
Top-down time estimation technique that leverages historical data from similar past projects to predict duration of new projects. Provides quick estimates based on expert judgment and comparable project experiences.
Project time estimation technique that breaks projects down into smaller, manageable tasks for detailed estimation, then aggregates them for an overall project timeline. Provides high accuracy through granular analysis and team involvement.
Statistical time estimation technique that uses mathematical models and historical data to calculate project duration based on measurable parameters. Applies unit costs or durations to the quantity of work for accurate predictions.
Project time estimation methodology that accounts for uncertainty by using three time estimates: optimistic, most likely, and pessimistic. Originally developed by the US Navy for complex project planning and critical path analysis.