Planning Poker Works, But Not for the Reason Most Teams Think
Planning poker is an estimation technique in which team members simultaneously reveal their estimates for a story, then discuss discrepancies before converging on a number. The standard explanation for why it works is that simultaneous reveal prevents anchoring — no one’s estimate influences others before they have formed their own. This is true and not the main reason the technique is valuable.
The main reason planning poker works is that it makes disagreement visible. When one person estimates a story at two points and another estimates it at thirteen, the discrepancy is not primarily a calibration problem to be resolved by arithmetic. It is a signal that two people have different understandings of what the story involves. The discussion that follows the reveal is where the team discovers what one person knew that the other did not — a dependency, an edge case, a technical constraint, an ambiguity in the acceptance criteria. The estimate that emerges from that conversation is more accurate than either original estimate, not because the team split the difference, but because the team now has a shared understanding they did not have before.
This reframes what estimation sessions are actually producing. The number is a byproduct. The shared understanding is the output. Teams that use planning poker as a point-generation exercise — moving quickly through the backlog to assign numbers without engaging with disagreement — are capturing the least valuable part of the technique and discarding the most valuable part.
The implication is that a story where everyone immediately agrees on the estimate may not have been refined sufficiently. Immediate agreement is either a sign that the story is genuinely simple and well understood, or a sign that the team does not yet know what they do not know. The product owner and the facilitator should treat fast consensus as a prompt to ask one more question, not as permission to move on.
The specific numbers on the cards matter less than the conversation the cards facilitate. Teams that understand this use the technique well. Teams that focus on the Fibonacci sequence miss the point.