The Scrum Master's Role in Planning Poker
The product owner's job in planning poker is to clarify scope. The Scrum Master's job is different: keep the session honest, moving, and free of the dynamics that quietly wreck estimates. Here's what that looks like in practice.
Protect the reveal
The single most important thing a facilitator does is make sure votes are cast simultaneously. If people can see each other's cards before committing, the session stops being an estimate and becomes a negotiation anchored on whoever went first. Use a tool like One More Point so every vote stays hidden until everyone has locked one in, then reveal together.
Ask "why" before asking for a re-vote
When the spread is wide, don't just ask people to vote again. Ask the highest and lowest voter to explain their reasoning first. Often the low estimate missed a dependency, or the high estimate is pricing in a risk nobody else flagged. That thirty-second exchange resolves more disagreements than three more rounds of blind voting.
Keep the clock visible
Estimation sessions expand to fill the time available. A Scrum Master who timeboxes each story (two minutes of discussion, one vote, one re-vote if needed, then move on) gets through a backlog in a fraction of the time a free-flowing discussion takes. If a story needs more than that, it's usually not ready to estimate yet, not a sign the team needs to argue longer.
Don't vote, and don't break ties
The Scrum Master isn't there to size the work; they didn't write the code or the acceptance criteria. Stay out of the voting pool, and resist the urge to resolve a stuck disagreement by picking a number yourself. If the team can't converge after two rounds, park the story and bring it back once it's better understood.
Watch for silent estimators
Some team members go along with the group rather than voting their honest read. A facilitator who notices someone consistently voting the median, or who never explains an outlier vote, should ask that person directly what they're seeing. Consensus that isn't actually independent isn't useful data.
The Scrum Master's value in planning poker isn't in the estimates themselves. It's in making sure the process that produces them stays fast, honest, and low-drama enough that the team keeps trusting it.
