Scrum Master Role and Servant Leadership
This domain, Scrum Master Role and Servant Leadership, tests how the Scrum Master serves the team, Product Owner, and organization without becoming a command-and-control manager. Expect scenario questions about coaching, facilitation, impediments, and authority.
Core rules and concepts
- The Scrum Master is accountable for the Scrum Team’s effectiveness and for establishing Scrum as defined in the Scrum Guide. The role is a true leader who serves.
- Serving the Scrum Team includes coaching self-management and cross-functionality, helping focus on high-value Increments that meet the Definition of Done, causing impediments to be removed, and ensuring events are positive, productive, and timeboxed.
- Serving the Product Owner includes helping with Product Goal definition, Product Backlog management, empirical product planning, and stakeholder collaboration.
- Serving the organization includes coaching Scrum adoption, advising implementation, helping stakeholders understand empiricism, and removing barriers between stakeholders and teams.
- Servant leadership uses persuasion, long-term orientation, stewardship, and growth of people. It is not passivity; the Scrum Master uses influence, teaching, and facilitation.
Worked example
A Scrum Team waits for the Scrum Master to assign daily tasks and escalate every dependency. The Scrum Master stops acting as coordinator: the Developers practice choosing their own work, the impediments are made visible on a board, and the Scrum Master coaches the team to resolve what it can while working with the organization on systemic barriers. Reasoning: servant leadership grows self-management; doing the team’s coordination for it would weaken the accountability the role is meant to build.
Traps that cost marks
- Describing the Scrum Master as a project manager, HR function, or task assigner.
- Equating servant leadership with passivity or avoiding conflict.
- Claiming the Scrum Master must personally remove every impediment.
- Saying the team reports to the Scrum Master rather than to the Product Owner for product value.