7.6 Planning Poker

Introduction

Planning Poker is one of the most popular Agile estimation techniques used by Scrum Teams to estimate the effort required for User Stories or Product Backlog items.

It combines:

• Expert discussion
• Collaborative estimation
• Consensus-based decision making

Planning Poker helps teams improve estimation accuracy while encouraging collaboration and shared understanding.

What is Planning Poker?

Planning Poker is a consensus-based estimation technique where team members use numbered cards to estimate the relative effort, complexity, and size of User Stories.

Each participant independently selects an estimate card, and all estimates are revealed simultaneously.

The team then discusses differences and reaches a final consensus estimate.

Purpose of Planning Poker

Planning Poker helps Scrum Teams:

• Estimate User Stories collaboratively
• Improve estimation accuracy
• Reduce bias during estimation
• Encourage team discussion
• Build shared understanding of requirements

Why Planning Poker is Important

Without collaborative estimation:

• Estimates may become inaccurate
• Different assumptions remain hidden
• Team members may misunderstand requirements
• Dominant individuals may influence estimates unfairly

Planning Poker solves these problems by promoting equal participation and discussion.

How Planning Poker Works

Step 1: Product Owner Explains User Story

The Product Owner presents a User Story and explains:

• Business requirements
• Expected functionality
• Acceptance Criteria

Step 2: Team Discusses the Story

Developers ask questions and discuss:

• Technical complexity
• Dependencies
• Risks
• Implementation approach

Step 3: Team Members Select Cards

Each participant privately selects an estimation card representing Story Points.

Step 4: Cards are Revealed Simultaneously

Everyone shows their selected cards at the same time to avoid influencing others.

Step 5: Discuss Differences

If estimates differ significantly, team members explain their reasoning.

Step 6: Re-Estimate if Necessary

The team may repeat estimation until consensus is reached.

Common Planning Poker Card Values

Planning Poker commonly uses the Fibonacci sequence because complexity grows non-linearly.

Card Value	Meaning
1	Very small task
2	Simple task
3	Moderate effort
5	Medium complexity
8	Complex feature
13	Very large feature
21+	Too large, should be divided

Why Fibonacci Sequence is Used

As complexity increases, uncertainty also increases.

The Fibonacci sequence reflects this increasing uncertainty by providing wider gaps between larger numbers.

Example of Planning Poker

User Story

"As a customer, I want secure online payment processing."

Estimation Round

Team Member	Estimate
Developer A	5
Developer B	8
Developer C	5
Tester	8

Discussion reveals:

• Additional security testing required
• External payment gateway dependency exists

Final consensus estimate:

• 8 Story Points

Benefits of Planning Poker

Benefit	Description
Improved Estimation Accuracy	Multiple viewpoints improve estimates
Better Collaboration	Encourages team discussion
Reduced Bias	Simultaneous voting avoids influence
Shared Understanding	Clarifies requirements and complexity
Knowledge Sharing	Team members learn from discussions
Improved Sprint Planning	Supports realistic sprint commitments

Participants in Planning Poker

Participant	Role
Product Owner	Explains User Stories
Developers	Estimate implementation effort
Testers	Estimate testing effort and risks
Scrum Master	Facilitates the session

Role of Product Owner in Planning Poker

The Product Owner:

• Clarifies requirements
• Answers business questions
• Explains Acceptance Criteria
• Supports requirement understanding

The Product Owner usually does not estimate Story Points.

Role of Developers in Planning Poker

Developers:

• Estimate technical complexity
• Discuss implementation challenges
• Identify dependencies and risks
• Reach estimation consensus

Role of Scrum Master in Planning Poker

The Scrum Master:

• Facilitates estimation sessions
• Encourages participation
• Prevents dominance by individuals
• Ensures Agile estimation practices

Planning Poker vs Traditional Estimation

Aspect	Planning Poker	Traditional Estimation
Approach	Collaborative	Manager-driven
Focus	Relative estimation	Exact time estimation
Participation	Entire Scrum Team	Usually individual estimates
Bias Reduction	Simultaneous voting	Higher influence risk
Discussion	Encourages collaboration	Limited discussion

Common Challenges in Planning Poker

Challenge	Description
Unclear User Stories	Difficult to estimate accurately
Large Estimation Differences	Team disagreement on complexity
Dominant Team Members	Influencing estimation discussions
Large User Stories	Stories too complex for estimation
Rushing Estimation	Insufficient discussion

Best Practices for Effective Planning Poker

• Keep User Stories clear and refined
• Encourage open discussion
• Estimate collaboratively
• Use consistent reference stories
• Break large stories into smaller stories
• Focus on relative effort, not exact time

Common Mistakes in Planning Poker

• Converting Story Points into hours
• Allowing managers to influence estimates
• Skipping discussions
• Estimating unclear stories
• Using Planning Poker for performance evaluation

Planning Poker Tools

Teams may use:

• Physical Planning Poker cards
• Online Planning Poker tools
• Jira estimation plugins
• Agile collaboration software

Real-Life Example

Example:

A Scrum Team estimates a new “Order Tracking” feature for an e-commerce platform.

During Planning Poker:

• Some members estimate 5 points
• Others estimate 13 points

Discussion reveals:

• Integration with third-party logistics API
• Additional testing requirements
• Security considerations

After discussion, the team agrees on:

• 8 Story Points

Importance of Planning Poker in Agile

Planning Poker is important because it:

• Improves estimation quality
• Encourages collaboration
• Builds shared understanding
• Supports Agile planning
• Reduces hidden assumptions

Conclusion

Planning Poker is a highly effective Agile estimation technique that combines collaboration, discussion, and consensus-based estimation.

By encouraging equal participation and shared understanding, Planning Poker helps Scrum Teams improve estimation accuracy, sprint predictability, and overall Agile delivery success.