Planning Poker

Popularized by Mike Cohn, Planning Poker is a facilitation technique for estimation.

Estimation is probably one of the most controversial topics in the Agile domain. The reason is likely related to assumptions about what these estimations are going to be used for. Some fear teams are going to be held accountable for the provided estimates, which will not be driving better estimations since teams are probably going to add some contingency to the estimates. Others claim estimating is pointless in a Complex domain since there are too many unknowns.

The main objective of Agile Estimation is to have better conversations about the problem to be solved. The main job of a Product Owner is to maximize return on investment, and one part of that equation is the size of the work, so estimating is also helping Product Owners do their job.

Popularized by Mike Cohn, Planning Poker is a facilitation technique for estimation. The idea is that the conversation is facilitated so that every team member’s opinion counts, while keeping the process effective. Planning cards or smartphone Apps can be used to share values, typically a Fibonacci like sequence is used: 0 ,1, 2, 3, 5, 8, 13, 20, 40, 100, ?

How to play

At the start of planning poker, each team member is given a deck of cards. For each user story or theme to be estimated;

  • A moderator (PO, SM or Analyst, doesn’t vote) reads the description.
  • Each team member privately chooses a card value based on their gut feeling and understanding of the story description.
  • When everyone has chosen a card, the cards are shown to all.
  • The ones with highest and lowest value provide their arguments for choosing this value.
  • The product owner and or stakeholder answers any questions that the team members have.
  • Each team member again privately selects a card representing his or her estimate.
  • All cards are shown simultaneously so that all participants can see each estimate.
  • Again the ones with highest and lowest value provide their arguments for choosing this value.
  • After the discussion, each team member re-estimates by selecting a card.
  • When there is just one step difference between the remaining cards, the highest value is chosen.
  • If after the third round there is still no consensus on the estimate, the highest value of is chosen.


Related Blog Post

Elevate Your SAFe® By Breaking Down Barriers

Impact of Hierarchical Boundaries on SAFe® Scaled Agile Framework Adoption In the pursuit of organisational agility, the Scaled Agile Framework (SAFe®) above all is thought to offer a roadmap for…

Miscommunication in software specifications.

There are often misunderstandings in software specification documents. The solution we typically choose is to make more detailed specifications. Unfortuantely that doesn't lead to better results

Related Training

Related Resources

How to Run a Retrospective

Running an effective retrospective is crucial for continuous improvement in Agile teams. If you’ve ever felt that your team’s retrospectives are lacking direction or failing to produce actionable insights, you’re…

Five different bridges

Five Ways to Build Consensus

Discover five effective strategies to build consensus and foster collaboration within your team or organization.

A circular flow chart with various stages representing the scrum process

The Scrum Process Explained

Uncover the intricacies of the Scrum process and learn how this agile framework can revolutionize project management.

More Resources

Let's Talk About
How We Can Help!

Are you enjoying our articles? Even better you can talk to us in person! Get in touch with us so we can schedule something!