Servant leadership in practice: what a Scrum Master does

"Servant leader" is the most quoted and least explained phrase about the Scrum Master. It sounds like a contradiction, or like a polite word for an assistant. The Guide's sentence is more demanding than either. Scrum Masters, it says, are true leaders who serve the Scrum Team and the larger organisation. Both words are meant.

What the Guide asks for

After that sentence the Guide lists how the Scrum Master serves three groups. For the Scrum Team: coaching members in self-management and cross-functionality, helping them create high-value Increments that meet the Definition of Done, causing the removal of impediments, and ensuring all Scrum events take place and are positive, productive and within the timebox. For the Product Owner: helping find techniques for Product Goal definition and backlog management, and facilitating stakeholder collaboration. For the organisation: leading, training and coaching in Scrum adoption, advising on implementations and removing barriers between stakeholders and teams.

Look at the verbs: coach, help, cause, ensure, facilitate, lead, train. None of them is "decide for". The Scrum Master is accountable for Scrum being established and for the team's effectiveness, and exercises that accountability through influence.

The SBOK® Guide names the preferred style supporting leadership, describing leaders who use listening, empathy and insight while sharing power and authority with team members, and who achieve results by focusing on the needs of the team. It calls this style the embodiment of the Scrum Master role. It sets it against styles such as directing, autocratic and laissez-faire, noting that leaving a team entirely unsupervised often leads to anarchy. So the position is not "do nothing". It is a specific kind of active.

The Agile Manifesto's principle on motivated individuals says the same from the other side: give them the environment and support they need, and trust them to get the job done.

Five behaviours you can observe

Listening before speaking. In a Retrospective or a disagreement, the servant leader hears the whole argument first. The effect is subtle but strong: the team notices who is willing to listen, and imitates it.

Asking before telling. "What have you tried?" and "What would make this easier?" lead to the team solving the problem. A Scrum Master who answers every question teaches the team to ask them instead of thinking.

Clearing the path. The Guide's phrase is "causing the removal of impediments". The Scrum Master does not always remove them personally, and often should not. They make sure the right person knows, and that the obstacle is dealt with. See impediments and the impediment log.

Protecting focus. Interruptions, side requests and extra meetings come from outside. A Scrum Master who absorbs or redirects them gives the Developers the working attention that the Sprint Goal requires.

Stepping back. The most skilled move, and the one most often missed. When the team can run its own Daily Scrum, plan its own Sprint and resolve its own conflict, the servant leader does less. An indispensable Scrum Master is a sign of a team that has not grown.

A worked example: the design dispute

This is an illustrative scene. Two Developers have disagreed about the design of a notification service for three days. One wants a message queue, the other a simpler scheduled job. The argument is getting personal. The Sprint is at risk.

A directing manager would pick one and move on. An absent one would let it run. The Scrum Master takes a third path. She asks both to write down, in a few sentences, what problem each design solves and what it risks, and asks the team to read both. She does not take a side. She points out that the Definition of Done requires the design to be reviewed and tested, and that the Sprint Goal needs a working version by day eight.

The team talks it through. A third Developer notes that the scheduled job can ship this Sprint and the queue can follow if volumes grow. The original two agree. The Scrum Master asks what should be recorded for the Retrospective, and the team decides to note the design reason. Nothing was ordered, and nobody was ignored. The team made the decision, understood it and moved faster than they would have under instruction.

The SBOK summarises the intended effect: the Scrum Master is the supporting leader who moderates and facilitates team interactions as coach and motivator, and guards the team from external influences.

When to be more directive

Servant leadership is not passivity. There are moments when a firm line is part of service. The Guide gives the Scrum Master accountability for ensuring that events take place and are kept within the timebox, and for establishing Scrum as defined in the Guide. If a stakeholder keeps cancelling the Sprint Review, or a manager is assigning tasks to Developers, the Scrum Master should say so clearly, to the right person, and more than once if needed. Firmness about the framework and gentleness with people can sit together.

How you know it is working

The measure is the team, not the Scrum Master. A few observable signs: the Daily Scrum runs without you, impediments are raised sooner and by more people, Retrospective actions are chosen by the team and then done, and stakeholders deal with the Product Owner and the Developers directly. The Guide ties the Scrum Master to the team's effectiveness, and effectiveness is something you can see over several Sprints in shorter waits and fewer surprises.

There is also a quieter sign. People bring the Scrum Master problems early, including ones that reflect badly on them. That only happens when the Scrum Master has shown, repeatedly, that bad news is treated as information and not as an offence.

How the role goes wrong

• The secretary. The Scrum Master books rooms, updates boards and takes notes, and never coaches. The team becomes dependent on the administration.
• The boss. The Scrum Master assigns work, chases progress and reports on individuals. This replaces a self-managing team with a managed one, and the Guide's accountability for the team's effectiveness is turned into control.
• The invisible. The Scrum Master avoids all conflict, so impediments pile up and the organisation never hears the cost.
• The rescuer. They fix everything personally, which feels like service and creates dependence.

How to practise it

Pick one behaviour to work on for a Sprint, for example asking a question where you would normally give an answer, and note what the team does. In the simulator you can take the Scrum Master role and see how many of your decisions are the team's to make.