Scrum Master Stances: A Situational Toolkit
A Scrum Master isn't just a meeting facilitator. They're a situational leader who adopts different roles—teacher, coach, impediment remover—to serve the team. This toolkit helps them decide when to teach, when to coach, and when to clear a path for the team.
Why it exists
Scrum is a framework, not a detailed process manual. Teams need guidance to navigate it effectively, but their needs change over time. A single, rigid role for the Scrum Master wouldn't work, so the stances provide a flexible model for effective, situational leadership.
The mental model
A Scrum Master is like a versatile coach for a sports team. They don't just run drills (facilitate). Sometimes they teach fundamentals (teacher), help a player with their technique (mentor), ask the team to devise their own plays (coach), or argue with the league office about a bad rule (impediment remover). The stance they choose depends entirely on the game situation and the team's needs.
How it works
The Scrum Master constantly assesses the team, individuals, and the organization to decide which stance is most helpful. The primary stances include: Teacher, explaining the 'why' behind Scrum principles; Mentor, offering one-on-one guidance; Facilitator, ensuring meetings are productive and neutral; Coach, asking powerful questions to unlock the team's potential; and Impediment Remover, clearing external blockers. The goal is to move from more directive stances (teacher) to less directive ones (coach) as the team matures.
When to use it
Use the Teacher stance for a new team unfamiliar with Scrum. Use the Coach stance when a mature team faces a recurring problem and needs to develop its own solution. Use the Impediment Remover stance when a blocker is outside the team's control, like needing a new server provisioned by another department. The key is situational awareness.
When not to use it
Don't get stuck in one stance. A perpetual Teacher creates dependency. A perpetual Facilitator becomes a glorified meeting secretary. A perpetual Impediment Remover becomes a 'team admin' who prevents the team from learning to solve its own problems. Also, avoid the 'Scrum Police' stance—enforcing rules without context or empathy. The role is not about command and control.
One canonical example
A team consistently fails to complete its work in a Sprint. A novice Scrum Master might just facilitate a longer retrospective (Facilitator). A more experienced one might first check for understanding of estimation (Teacher), then see if an external dependency is the cause (Impediment Remover). But the most effective approach might be to ask the team, "What have we observed about our last three Sprints? What patterns do you see? What's one experiment we could try to change this outcome?" (Coach). This empowers the team to own and solve its problem.
Interview question
For a mature Scrum Team consistently missing Sprint Goals due to internal communication issues, which Scrum Master stance is most effective for long-term improvement?
- a.Coach, to guide the team in self-identifying communication patterns and developing their own solutions.Correct
- b.Facilitator, to strictly manage meeting agendas and ensure all voices are heard.
- c.Impediment Remover, to directly intervene and implement new communication tools or processes.
- d.Teacher, to educate the team on effective communication strategies and Scrum principles.
Why? this is the answer
For a mature team facing a recurring problem, the Coach stance empowers them to own and solve their issues by asking powerful questions, fostering self-organization and long-term learning. While other stances might offer temporary fixes, coaching helps the team develop its own sustainable solutions, aligning with the goal of moving to less directive stances as the team matures.
Just read this? Test yourself on what you have been reading.
- #agile
- #scrum
- #scrum master
- #leadership
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles