Interactive Lean and Agile Management Simulation

Agile Estimation – Planning Poker

Estimate user stories collaboratively, reveal votes simultaneously, explore disagreement, revote after discussion and learn when uncertainty means the story should be refined rather than forced into a precise estimate.

At a Glance
Primary Focus Relative estimation and shared understanding
Typical Duration 12–18 minutes
Learning Format Interactive planning-poker simulation
Best For Agile teams, product practitioners and delivery leaders
Overview

Planning poker turns estimation disagreement into a learning conversation.

The simulation uses a modified Fibonacci-style point scale, private selection, simultaneous reveal, discussion of high and low estimates, and a second vote. It emphasizes relative size rather than hours and shows why story clarity and uncertainty affect confidence.

Guided Demonstration

Planning Poker — Step by Step

Eight locked stages move from estimation context through scale calibration, private voting, outlier discussion, revoting, uncertainty, an ambiguity challenge and management review.

Current Estimate Not revealed
Vote Spread Not revealed
Progress Stage 1 of 8
Guided learning stages
Foundation Stage 1 of 8

Current Instruction
Interactive Planning-poker Table

Private Estimates, Simultaneous Reveal and Team Convergence

Reveal the estimation context to begin.

100%
Planning-poker status: Establish the estimation context.
Supporting Analysis

Use estimation behavior as information.

Experiment Mode

Test an Estimation Scenario

Experiment Mode is isolated from the guided demonstration. Select a story, adjust clarity and dependency uncertainty, then compare the simulated vote pattern and confidence.

Knowledge Check

Test agile-estimation judgement.

Choose an answer, then check it.
Quick Reference

Planning-poker cues

Relative Size

Estimate one backlog item relative to other understood work; do not treat points as standardized hours.

Private Selection

Choose cards independently before seeing other estimates to reduce anchoring.

Simultaneous Reveal

Reveal together so disagreement reflects independent judgement rather than following the first visible number.

Discuss Extremes

Ask high and low estimators to explain assumptions, hidden work, dependencies and uncertainty.

Revote

Estimate again after discussion until the team has enough shared understanding to accept a size.

Refine When Needed

If the story remains very large or uncertain, clarify, spike or split it instead of forcing false precision.

Key Takeaway
The goal is shared understanding and a useful relative estimate—not numerical conformity.

Estimate privately, reveal together, discuss why estimates differ, revote with new knowledge and refine stories when uncertainty is too high for a trustworthy commitment.