Skip to content
PMPCAPM

Planning Poker

Planning Poker is a consensus-based agile estimation technique where team members privately select cards representing their estimate, reveal them simultaneously, and discuss differences to reach agreement.

Share:

Know it well enough for the exam? Questions on Planning Poker are scenario-based, not definitional.

Practice it free

Explanation

In Planning Poker, each team member has a set of cards with values from the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, etc.) or a similar scale. The Product Owner or team member describes a backlog item, the team discusses it briefly, and then each person selects a card that represents their estimate of the item's effort. All cards are revealed simultaneously to prevent anchoring bias.

If estimates are similar, the team quickly agrees on a value. If there is significant disagreement, the highest and lowest estimators explain their reasoning, the team discusses further, and they re-estimate. This process continues until consensus is reached. The discussion is often more valuable than the final number because it surfaces different perspectives and assumptions.

Planning Poker combines expert opinion, analogy, and group discussion. By revealing simultaneously, it avoids the anchoring effect where early estimates influence later ones. It is one of the most popular estimation techniques in agile and works well with teams of three to ten people.

Key Points

  • •Uses Fibonacci-sequence cards for relative estimation
  • •Simultaneous reveal prevents anchoring bias
  • •Disagreements drive valuable discussion about complexity and assumptions
  • •Works best with teams of three to ten people

Exam Tip

Planning Poker prevents anchoring by having everyone reveal their estimate simultaneously. The discussion that follows disagreement is where the real value lies.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Planning Poker

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.