Facilitation, Coaching and Servant Leadership in the Scrum Master Role
This domain tests behaviour, not definitions. Questions present a team situation - a silent retrospective, a dominating stakeholder, a recurring impediment - and ask what the Scrum Master does. The right answer is almost always one that builds the team's own capability rather than solving the problem for them.
Servant leadership in practice
The Scrum Master serves three constituencies. Serving the team means coaching self-management, facilitating events so they achieve their purpose, and removing impediments. Serving the Product Owner means helping with backlog management techniques and facilitating stakeholder collaboration. Serving the organisation means leading Scrum adoption, planning and advising, and helping people understand empirical product development. The stance is "ask, don't tell": build capability rather than making decisions on the team's behalf.
Facilitation technique
Good facilitation makes the group's thinking visible and equalises airtime. Techniques worth naming in an answer: silent writing of ideas before discussion, dot voting to converge, fist-of-five to test consent, 1-2-4-all to scale a conversation from pairs to the whole group, and plus/delta for retrospectives. The Scrum Master designs the process and holds the timebox while the team owns the content and the decisions. When conflict appears, distinguish task conflict, which is useful, from relationship conflict, which needs separate handling.
Coaching
Coaching is a structured conversation aimed at the coachee's own thinking. Powerful open questions ("what did you try?", "what would good look like?"), active listening and summarising replace advice-giving; a simple sequence is goal, reality, options, will. Teams also move through forming, storming, norming and performing, and the stance changes with the stage - more direction early, more delegation later.
Worked example
In a Retrospective two senior developers dominate while three juniors say nothing. The Scrum Master should not simply ask others to speak up. Instead: five minutes of silent writing, all cards posted and clustered, then dot voting to pick three topics, discussed in mixed pairs before the whole group. Reasoning: silent writing removes the status effect of speaking first, and the pair step gives quieter members a low-risk entry. Actions go to volunteers, not to the Scrum Master.
Traps
- Solving an impediment yourself when the team could own it; log it, agree an owner, follow up.
- Facilitating toward a predetermined decision - that destroys the safety the role depends on.
- Sliding into instructing or mentoring whenever the team struggles instead of asking questions.
- Letting retrospective actions live only in the room, with no owner, date or review at the next Retrospective.