Planning Poker (also known as Scrum Poker) is a collaborative, consensus-driven estimation technique used in agile frameworks such as Scrum, SAFe, LeSS and Nexus. Teams use it to estimate the relative effort and complexity of work items (typically user stories). Each team member secretly selects a card with a number—most commonly from a modified Fibonacci sequence (0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100). All cards are then revealed simultaneously, ensuring that no one’s opinion anchors the group. Large differences are discussed, questions clarified, and the process repeats until the team reaches a robust consensus.
The goal is not to predict exact hours, but to establish a shared understanding of complexity and to compare stories against each other in a meaningful, relative way.
Origins and Theoretical Foundations
Planning Poker was invented by James Grenning in 2002 as a lighter, faster alternative to Wideband Delphi and was popularized by Mike Cohn in Agile Estimating and Planning. Its theoretical roots are clear:
• Wideband Delphi: A multi-round expert estimation technique from the 1960s where experts anonymously provide estimates, compare results and iterate toward consensus.
• Game Thinking: The card-game format with simultaneous reveals prevents anchoring effects and keeps participants equally engaged.
• Collective Intelligence: Independent individual estimates followed by structured discussion yield more reliable group decisions than traditional sequential discussions.
This combination makes Planning Poker a structured yet lightweight tool for iterative consensus building.
Step-by-Step Procedure and Advanced Good Practices
1. Preparation
• Ensure each user story meets the Definition of Ready and is clearly written.
• Establish baseline stories (e.g., 3, 5 and 8 points) as reference items to make future comparisons easier.
2. First Estimation Round
• The Product Owner (or equivalent role) explains the story and answers questions.
• Each team member secretly selects a card reflecting their estimate.
3. Simultaneous Reveal
• All cards are revealed at once to avoid anchoring and groupthink.
• Wide gaps immediately highlight hidden risks or unknowns.
4. High/Low Drill-down
• Members with the highest and lowest estimates explain their reasoning first.
• Discussion focuses on assumptions, risks and dependencies rather than defending positions.
5. Second (or Third) Round
• A second round follows if needed, reflecting insights gained.
• Stop rule: after a maximum of three rounds the team either agrees, creates a research spike, or moves the story back to refinement.
6. Retro-Calibration
• In Sprint Retrospectives the team compares estimates with actual effort and adjusts baselines or practices accordingly.
Expert-level practices for Scrum Masters and agile coaches
• Timeboxing: Limit discussion of each item to about 2–5 minutes to maintain energy and focus.
• Risk-aware dialogue: Explicitly surface technical, architectural and external dependencies.
• Knowledge balancing: Use discrepancies to identify and close knowledge gaps immediately.
• Transparent documentation: Capture estimates and rationales for later analysis and portfolio planning.
• Integration with value metrics: Combine effort estimation with business value techniques such as WSJF to improve prioritization.
Use in Different Agile Frameworks
Scrum
Planning Poker is a widely adopted best practice but not mandated by the Scrum Guide. It is typically performed during Backlog Refinement so that Sprint Planning remains focused on commitment rather than lengthy estimation. The Scrum Master facilitates, while the Product Owner provides context and clarifies requirements.
SAFe (Scaled Agile Framework)
SAFe teams commonly use Planning Poker (often called Estimating Poker) to size stories. These team-level estimates feed into Program Increment (PI) Planning, where multiple teams align their velocities and inform portfolio-level WSJF prioritization.
LeSS (Large-Scale Scrum)
LeSS applies Scrum principles to large product groups with one Product Owner and one Product Backlog. Teams may use Planning Poker to estimate their stories independently. LeSS coaches stress that estimation should stimulate learning and discussion, not serve as a control mechanism; alternative techniques (e.g. Estimation Matrix) are equally acceptable.
Nexus
Nexus minimally extends Scrum to enable multiple teams to deliver a single integrated increment. The Nexus Integration Team coordinates cross-team dependencies, but each Scrum Team continues to estimate its work—often with Planning Poker—inside its own Sprint Planning sessions.
Typical Pitfalls and Challenges
• False precision: Story Points are relative measures; converting them directly into hours misrepresents their intent.
• Groupthink: Despite simultaneous reveals, dominant personalities can influence later discussion if not carefully facilitated.
• Unrefined stories: Items that lack a clear Definition of Ready lead to endless debates and inconsistent results.
• Velocity misuse: Treating team velocity as a performance metric creates pressure to “game” estimates.
• No feedback loop: Without regular retro-calibration, teams fail to improve their estimation accuracy.
Real-World Examples
Spotify squads use Planning Poker to expose architectural risks early and to align cross-disciplinary work.
Atlassian reports that Planning Poker improves transparency and encourages input from quieter team members, especially in distributed teams.
ThoughtWorks applies Planning Poker not only in development teams but also in cross-functional discovery workshops to explore business and technical complexity together.
These cases illustrate how Planning Poker evolves from a mere estimation tool into a communication and learning practice.
CALADE Perspective
At CALADE we treat Planning Poker as more than a planning gimmick—it is a core instrument for team learning and alignment:
• In training and workshops, Planning Poker makes agile values tangible and teaches teams how to surface assumptions early.
• In transformation projects, it serves as a low-threshold entry point for collaborative estimation and shared accountability.
• In strategy and portfolio work, we combine Planning Poker with Leading & Lagging Indicators and our Living Transformation® approach, ensuring that effort estimates connect to measurable business outcomes.
This integration turns Planning Poker into a living practice rather than a mechanical meeting ritual.
Related Terms
• Scrum
• Backlog Refinement
• Story Points
• Velocity
• SAFe
• LeSS
• Nexus
• Living Transformation
← back to list