What is Planning Poker? A Complete Guide for Agile Teams

What is Planning Poker?

Planning Poker (also called Scrum Poker) is a consensus-based estimation technique used by agile software development teams. Each team member simultaneously reveals their estimate using cards, then discusses differences until reaching agreement. The simultaneous reveal is the key mechanism — it prevents anchoring bias where early estimates influence everyone else.

Where Did Planning Poker Come From?

The technique was first described by James Grenning in 2002 and later popularized by Mike Cohn in his book "Agile Estimating and Planning." It draws from the Wideband Delphi estimation technique and combines it with game-like mechanics to make estimation more engaging and accurate.

How Does a Planning Poker Session Work?

A typical session follows these steps:

• 1. The Product Owner presents a user story or backlog item to the team
• 2. Team members ask clarifying questions about scope and acceptance criteria
• 3. Each member privately selects a card representing their estimate
• 4. All cards are revealed simultaneously
• 5. If estimates converge, that value is accepted
• 6. If estimates diverge, the highest and lowest estimators explain their reasoning
• 7. The team re-votes until consensus is reached

What Do the Cards Mean?

The most common deck is the Fibonacci sequence: 0, 1, 2, 3, 5, 8, 13, 20, 40, 100. The gaps between numbers grow larger as uncertainty increases — there's no meaningful difference between 23 and 25 hours, so there's no "23" card. Special cards include ? (I don't understand this story), ∞ (this is too large to estimate), and ☕ (I need a break).

Why Does Planning Poker Work?

Several psychological mechanisms make Planning Poker effective:

• Simultaneous reveal eliminates anchoring bias — no one is influenced by hearing others' estimates first
• Everyone must commit to an estimate, preventing passive participation
• Discussion of outliers surfaces hidden complexity and shared misunderstandings
• The game-like format keeps teams engaged during long planning sessions
• Relative estimation is more accurate than absolute estimation for complex work

Planning Poker vs. Other Estimation Methods

Compared to alternatives: Top-down estimation (manager assigns points) lacks team input and is consistently optimistic. T-shirt sizing (XS/S/M/L/XL) is faster but less granular. Bucket estimation works for large backlogs. Planning Poker is best for sprint-level estimation where accuracy matters and team alignment is critical.

Common Mistakes to Avoid

Teams often make these mistakes:

• Estimating time instead of complexity — story points are not hours
• Skipping the discussion when estimates differ — that's where the value lives
• Not using a reference story — always anchor estimates to a known baseline
• Pressuring toward consensus too quickly — two rounds of voting is often necessary
• Spending more than 5 minutes on any single story — time-box ruthlessly

Running Planning Poker Online

For remote teams, a digital planning poker tool is essential. Look for: simultaneous card reveal (not one-by-one), real-time sync, no sign-up required for participants, and support for multiple deck types. Scrum Poker Online offers all of this — create a room in seconds, share a code, and your team can start estimating from anywhere.