The Scrum Master's role in estimation
The Scrum Master is the guardian of the agile process, and that includes facilitating estimation sessions. But there’s a thin line between facilitating and influencing — and crossing it compromises the entire exercise.
What the Scrum Master SHOULD do
Facilitate the process
- Make sure everyone understands the Planning Poker rules
- Keep each estimation round time-boxed
- Ensure everyone has voted before cards are revealed
- Mediate discussions impartially
Create a safe environment
- Ensure divergent votes are respected
- Encourage junior members to share their perspectives
- Prevent senior members from dominating the conversation
- Proactively ask quiet participants for their thoughts
Protect the team
- Shield the team from stakeholders pushing for lower estimates
- Block external interruptions during the session
- Don’t let managers try to “negotiate” estimates
What the Scrum Master should NOT do
Vote (in most cases)
The Scrum Master is usually not a technical contributor. Offering a guess on technical complexity can bias the team. If the Scrum Master has a technical background on this team, they may vote — but with caution.
Suggest estimates
“That feels like a 5 to me” — never. Even if meant as a genuine suggestion, the team will interpret it as direction.
Accept pressure for lower numbers
“The client needs this fast, can’t it be an 8?” — the Scrum Master should shut this down. Estimates belong to the team and aren’t negotiable by outsiders.
Ignore extreme divergences
If someone votes 3 and another votes 13, don’t just average them. The Scrum Master’s job is to make sure that gap gets discussed and understood.
Neutral facilitation technique
When there’s disagreement, use neutral questions:
- “Could whoever voted 3 walk us through your reasoning?”
- “For whoever voted 13, what are you seeing that others might not?”
- “Is there something we’re not considering?”
- “Do we need more information before we can estimate this?”
Never say: “Let’s just go with 8, then.” Instead try: “It sounds like we’re converging on 8 points. Does anyone have concerns?”
When the Scrum Master has a technical background
If the Scrum Master comes from the development team and knows the codebase:
- Vote last to avoid anchoring the group
- Declare your bias upfront: “I’ve worked on this part of the code, so I might be biased. I’d vote 5, but I want to hear from others first.”
- Consider abstaining on items where your opinion would carry disproportionate weight
Metrics of good facilitation
The Scrum Master can self-assess their facilitation with these questions:
- Were all voices heard?
- Did the estimates come from the team, not from me?
- Were disagreements explored and resolved?
- Did the session finish on time?
- Did the team leave with clarity?
Conclusion
The Scrum Master is the conductor, not the musician. Your role is to create the conditions for the team to estimate well — not to estimate on their behalf. That distinction is fundamental to producing honest, reliable estimates.