Servant Leadership and Facilitation
Servant Leadership in Practice
Servant leadership means the Scrum Master serves the team, the Product Owner, and the organization - removing obstacles, coaching, and enabling self-management rather than directing. Key behaviors: asking powerful questions, listening, creating safety, and letting the team own decisions. A trap presents a Scrum Master who assigns tasks or makes technical decisions "to help"; that undermines self-management and is wrong even when well-intentioned.
Facilitation Skills
Effective facilitation designs the container: clear purpose, appropriate format, timebox, and psychological safety. The facilitator manages process, not content - they do not steer the team toward a preferred answer. Techniques include silent brainstorming, dot voting, fist-of-five, and round-robin to balance participation. Traps include the Scrum Master dominating a retrospective or solving the team's problem for them.
Impediment Handling Nuance
Servant leaders remove impediments the team cannot remove itself, but they also coach the team to resolve what it can. Distinguish "removing" (organizational blockers) from "coaching" (capability building).
Worked rule of thumb
When a scenario asks what the Scrum Master should do first, prefer the option that increases the team's own capacity to solve the problem - facilitate, coach, or ask - over one that does the work for them. Escalation is appropriate when the impediment is outside the team's authority.
Exam traps
- Facilitation is not decision-making on the team's behalf.
- Servant leadership is not passivity; it includes assertive protection of the team and Scrum.
- The Scrum Master does not own the team's improvements; the team does.