Characterizing the Role of the Scrum Master
Servant leader first
The SAFe Scrum Master is a servant leader and team coach. Authority is over process, not people: the Scrum Master facilitates, teaches, removes impediments, and builds the conditions for self-management. The team decides how to do the work; the Scrum Master helps it decide well.
Concepts to name precisely
- Coaching stance. A good answer distinguishes coaching (asking, reflecting) from mentoring, teaching, and facilitating - the Scrum Master moves between them deliberately.
- Impediment removal and escalation. Team-level impediments are removed directly; organizational ones are escalated to the RTE.
- Emotional intelligence and psychological safety, which underpin conflict navigation and high-performing teams.
- Transparency and built-in quality as the Scrum Master's stewardship duties.
- Continuous improvement through retrospectives and the Scrum Master Community of Practice, where practices are shared across the ART.
Traps
- Casting the Scrum Master as a project manager: assigning tasks, collecting status, owning the schedule. The role has no such authority.
- Assuming the Scrum Master sets priorities or owns the backlog - that is the Product Owner's.
- Confusing coaching with directing: an answer that has the Scrum Master telling the team the solution is usually wrong.
- Forgetting the link upward: the Scrum Master works closely with the RTE and peer Scrum Masters, not in isolation.
- Missing that the Scrum Master protects the team's focus and time, not just its feelings.
Rule of thumb
The default Scrum Master question is "how can the team solve this itself?" - enable first, escalate when the impediment is beyond the team's authority, and never absorb work the team should own.