Planning Poker in Scrum: How Teams Estimate User Stories

Planning Poker is a collaborative technique commonly used by Scrum Teams to estimate the relative size of Product Backlog Items.

It combines individual estimates with team discussion so that different assumptions and areas of uncertainty can be identified.

Is Planning Poker Required in Scrum?

No.

Scrum does not prescribe Planning Poker or Story Points. Teams can choose an estimation approach that works for their situation.

How Does Planning Poker Work?

A typical Planning Poker session follows these steps:

  1. The Product Backlog Item is explained.
  2. The team discusses the requirement and asks questions.
  3. Each Developer privately selects an estimation card.
  4. Everyone reveals their cards at the same time.
  5. If estimates differ significantly, the team discusses why.
  6. The team estimates again if necessary.

Example

Suppose the team is estimating a User Story for adding wishlist functionality.

Developer A: 3 points
Developer B: 5 points
Developer C: 8 points

Instead of simply choosing the middle number, the team discusses the difference.

Developer C may have identified an integration dependency that the others had not considered.

After discussing the issue, the team estimates again.

Why Reveal Cards at the Same Time?

Simultaneous reveal helps reduce the influence of one person's estimate on everyone else.

If one person announces "8 points" first, others may unconsciously adjust their estimates toward 8.

The real value is the conversation.

Planning Poker is not about finding the perfect number. It helps the team uncover different assumptions and develop a shared understanding of the work.

Common Planning Poker Cards

1
2
3
5
8
13

Teams often use a Fibonacci-like sequence because the gaps become larger as uncertainty increases.

What If the Estimate Is Very Large?

A very large estimate can indicate that the item is too large, poorly understood, or contains significant uncertainty.

The team may need to clarify the item or split the work into smaller pieces.

What Is the Scrum Master's Role?

The Scrum Master can facilitate the session and encourage healthy discussion.

However, the Scrum Master should not decide the estimate for the Developers.

The people doing the work are responsible for sizing it.

Common Mistakes

Manager Chooses the Number Estimates are imposed instead of being created by the people doing the work.
Arguing About the Number The discussion becomes about being right instead of understanding the work.
Converting Points to Hours Story Points are treated as fixed units of time.
Over-Estimating Everything Teams spend too much time trying to achieve false precision.

When Should Planning Poker Be Used?

Planning Poker can be useful when the team needs to discuss and size Product Backlog Items, particularly when different views or uncertainties need to be explored.

It does not need to be used for every item or every team.

Key Takeaway

Planning Poker is a collaboration technique, not a mathematical exercise.

Its biggest benefit is helping Developers discuss the work, uncover assumptions and reach a shared understanding.