What is Planning Poker?

Planning poker (also known as scrum poker) is a consensus-based agile estimation technique used by development teams to estimate the effort required for user stories, features, or tasks. During planning poker sessions, team members use numbered cards to vote on story points privately, then reveal their estimates simultaneously to discuss differences and reach agreement.

How Planning Poker Works

The planning poker process follows these simple steps:

1. Present the Story: The product owner or scrum master presents a user story or task to be estimated
2. Discuss Requirements: Team members ask questions and discuss acceptance criteria
3. Private Voting: Each team member selects an estimate using planning poker cards (typically Fibonacci numbers)
4. Reveal Simultaneously: All votes are revealed at the same time to prevent anchoring bias
5. Discuss Differences: If estimates vary significantly, team members explain their reasoning
6. Re-vote: The team votes again until consensus is reached

Why Use Fibonacci Numbers for Estimation?

Most planning poker implementations use the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, etc.) because:

• Reflects Uncertainty: Larger numbers have bigger gaps, acknowledging that complex tasks are harder to estimate precisely
• Avoids False Precision: Forces teams to think in relative sizes rather than exact hours
• Natural Scaling: The mathematical relationship mirrors how uncertainty increases with complexity
• Proven Effectiveness: Widely adopted across agile teams worldwide

Key Benefits of Planning Poker

Planning poker offers numerous advantages over traditional estimation methods:

Benefits of Planning Poker

1. Eliminates Anchoring Bias

By having team members vote simultaneously, planning poker prevents the first person's estimate from influencing others. This leads to more accurate and unbiased story point estimates.

2. Encourages Team Discussion

When estimates differ significantly, it reveals different understandings of the work involved. These discussions often uncover important requirements or technical considerations.

3. Improves Estimation Accuracy

Research shows that team-based estimation techniques like planning poker are more accurate than individual expert estimates or mathematical models.

4. Builds Team Consensus

The collaborative process helps teams align on scope and complexity, leading to better sprint planning and commitment.

Planning Poker Card Values

Common planning poker scales include:

Standard Fibonacci (Most Popular)

1, 2, 3, 5, 8, 13, 21, ?, ☕

Modified Fibonacci

0, 1, 2, 3, 5, 8, 13, 20, 40, 100, ?, ☕

T-Shirt Sizes

XS, S, M, L, XL, XXL, ?, ☕

Powers of 2

1, 2, 4, 8, 16, 32, 64, ?, ☕

Special cards include:

• ? (Question Mark): "I need more information"
• ☕ (Coffee Cup): "I need a break"

Best Practices for Planning Poker Sessions

Before the Session

• Ensure user stories are well-defined with clear acceptance criteria
• Have the product owner available to answer questions
• Choose an appropriate estimation scale for your team
• Set up your planning poker tool (like EstimateIt)

During the Session

• Keep sessions focused and time-boxed
• Encourage participation from all team members
• Focus on relative sizing rather than absolute time
• Don't spend too much time on outlier estimates

After the Session

• Record the agreed story point values
• Update your product backlog
• Use estimates for sprint planning and velocity tracking

Online Planning Poker Tools

While physical cards work for co-located teams, remote and hybrid teams need digital solutions. Online planning poker tools like EstimateIt provide:

• Real-time collaboration for distributed teams
• Multiple estimation scales (Fibonacci, T-shirt sizes, etc.)
• Automatic vote revelation and reset functionality
• Mobile-friendly interfaces for voting from any device
• No registration required for quick setup

Common Planning Poker Mistakes to Avoid

1. Estimating in Hours Instead of Story Points

Focus on relative complexity and effort, not absolute time estimates.

2. Rushing Through Estimates

Take time to discuss and understand each story before voting.

3. Ignoring Outlier Votes

High and low estimates often reveal important insights about the work.

4. Not Involving the Whole Team

Include developers, testers, and anyone who will work on the story.

Conclusion

Planning poker is a powerful technique for agile teams to estimate story points collaboratively and accurately. By using tools like Fibonacci sequences and ensuring team-wide participation, you can improve your sprint planning and build stronger consensus around project scope.

Ready to try planning poker with your team? Start a free estimation session with EstimateIt – no registration required!