Scrum Master

Scrum is simple to describe and hard to do well. Teams slip back into old habits, meetings lose their purpose, impediments pile up and managers outside the team push work in ways that break the Sprint. The Scrum Master exists to prevent that. Rather than directing the team's work, the Scrum Master coaches the team in self-management, helps the Product Owner manage the backlog, facilitates events when needed and works with the wider organization to remove obstacles that the team cannot remove itself. The role is measured by how effective the team becomes, not by how busy the Scrum Master is. Good Scrum Masters often appear to do little in meetings, because their work happens through coaching and conversations outside them.

The role is defined in the Scrum Guide by Ken Schwaber and Jeff Sutherland. The 2020 version describes Scrum Masters as true leaders who serve the Scrum Team and the larger organization, replacing earlier language about servant leadership. Scrum Master is one of the most common agile job titles, with certifications offered by organizations such as Scrum Alliance and Scrum.org. For delivery leaders, team members and managers building agile teams, understanding what a Scrum Master should and should not do is essential to getting value from the role.

Definition of Scrum Master

A Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, by helping everyone understand Scrum theory and practice within the Scrum Team and the organization, and for the Scrum Team's effectiveness, by enabling it to improve its practices within the Scrum framework.

It is one of the three accountabilities in Scrum, alongside the Product Owner and Developers, and in SAFe the equivalent role at train level is the release train engineer within an agile release train.

How a Scrum Master Serves

The team. Coaching members in self-management and cross-functionality, helping them focus on high-value increments and making sure Scrum events take place and stay productive and timeboxed.

The Product Owner. Helping find techniques for defining the Product Goal and managing the backlog, and helping stakeholders collaborate with the team.

The organization. Leading and coaching agile adoption, helping employees and stakeholders understand empirical product development and removing barriers between stakeholders and teams.

Across all three, the Scrum Master raises impediments to the right people and helps solve them, rather than solving everything personally.

What a Scrum Master Is Not

A Scrum Master is not a project manager. They do not assign tasks, set deadlines or own the team's delivery plan.

They are not the team's secretary. Taking notes and updating tools may help occasionally, but the team owns its own work and boards.

They are not the team's manager. Scrum Masters influence through coaching and facilitation rather than authority over people's careers. They are not the team's spokesperson. Stakeholders should talk directly with the team and Product Owner, not route everything through the Scrum Master.

Importance of the Scrum Master in Delivery and Engineering Operations

A good Scrum Master improves team effectiveness. Teams with skilled coaching tend to adopt practices that stick and improve steadily.

They protect focus. By managing interruptions and removing impediments, they let the team spend more time on valuable work.

They also change the organization. Many impediments are outside the team, such as approval processes or conflicting priorities, and Scrum Masters raise and help address them.

The Scrum Master and Financial Management

Removing impediments, such as slow approvals or missing environments, frees capacity that the organization is already paying for.

One Scrum Master often supports one to three teams. Organizations should weigh the cost of the role against the effectiveness gains it produces.

Treating the role as a part-time duty for a developer saves money but often leaves impediments unaddressed and events poorly run.

Scrum Masters who help teams track outcomes and flow make it easier to show the business value of agile investments.

Common Challenges

Organizations often turn Scrum Masters into meeting organizers or status reporters, which wastes the role's potential. Spreading one Scrum Master across too many teams leaves no time for coaching or organizational work.

Scrum Masters without access to leaders cannot remove organizational impediments, so problems persist.

The role can become redundant as a team matures if it focuses only on running events. Mature teams still benefit from a Scrum Master who works on wider organizational change. Combining the Scrum Master role with the Product Owner role in one person creates conflicts of interest and usually weakens both.