Scrum Master

WHAT IS IT

Scrum Master

A Scrum Master is one of the three core members of a Scrum Team (alongside the Product Owner and the Developers). The main goal of the Scrum Master is to introduce and continuously develop the Scrum framework within the teams they support, while at the same time spreading agile principles across the entire organization.

At the same time, it is important to emphasize that a Scrum Master is not a team manager or a superior. On the contrary, they act as a servant leader – someone who serves the team, supports it, and helps it become more effective, self-managing, and accountable.

Responsibilities of a Scrum Master

In practice, a Scrum Master has a wide range of responsibilities. The most important ones include:

• Educating the Team in Scrum and Agile Principles
  They help team members understand Scrum values, roles, events, and artifacts, as well as their purpose and practical application.

• Facilitating Scrum Events (Ceremonies)
  They ensure that Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are conducted in a meaningful way so that these events bring real value to the team.

• Removing Impediments
  They actively help the team remove obstacles that hinder effective work, while also teaching the team how to handle similar issues independently in the future.

• Supporting Self-Management and Team Collaboration
  The Scrum Master creates an environment in which the team takes ownership of its work and decision-making.

• Driving Process and Cultural Change
  The Scrum Master’s role does not end with the team. They also help management and other parts of the organization understand Scrum and the agile way of working.

The “Dispensability” of a Scrum Master

A good Scrum Master consciously works toward not becoming indispensable. The goal is not team dependency on one person, but rather long-term team independence.

For example:

• During retrospectives, the Scrum Master does not propose action items themselves, but instead guides the team so that solutions emerge collaboratively.
• If they help remove an impediment, they clearly explain how they approached the situation so the team can handle a similar issue on its own next time.

Thanks to this approach, the Scrum Master can gradually focus on supporting other teams and driving change at the organizational level.

Official Definition of the Scrum Master Role

For completeness, it is worth mentioning that a detailed and official definition of the Scrum Master role can be found in the Scrum Guide, which is the primary source defining the Scrum framework.

Undesirable Traits of a Scrum Master

Among the traits and behaviors a Scrum Master should avoid are:

• an overly strong ego and a need for control
• dogmatic insistence on a “textbook” implementation of Scrum regardless of team context
• inconsistency between what they teach and how they behave
• micromanagement
• building their own indispensability

Such behavior is in direct conflict with the Scrum Master role and agile principles.

What a Scrum Master Is Not

Although the role title can be misleading, a Scrum Master is not a manager or the boss of the team. It is not a controlling or directive role. On the contrary, the Scrum Master helps the team grow and improve without telling it exactly how to work.

A Scrum Master is not:

• A Project Manager
  They do not manage projects through plans, budgets, and directive task assignments. Responsibility for delivering scope within time and budget in Scrum is shared by the team and the Product Owner.

• A Line Manager
  They do not evaluate individual performance, assign rewards, give orders, or handle HR matters.

• A Team Leader
  They do not decide who does what. A Scrum Team is self-managing, and work distribution is the responsibility of the team itself.

• A Secretary or Meeting Note-Taker
  Their role is not just to schedule meetings and write notes, but to increase the value of Scrum events and support meaningful collaboration.

• A Process Police Officer
  They do not mechanically enforce Scrum “by the book.” Instead, they help people understand Scrum and adapt it to the organizational context without losing its essence.

• An Expert with All the Answers
  The Scrum Master does not solve problems on behalf of the team. They ask questions, facilitate discussion, and support solutions emerging from within the team.

• An Irreplaceable Person
  If a team cannot function without its Scrum Master, it is a sign of a problem. A good Scrum Master works toward becoming less needed over time.

Summary

A Scrum Master is a guide, facilitator, and catalyst for change, not a manager or controller. Their true value lies in helping people, teams, and the entire organization understand and sustainably live an agile way of working.

Additional Practical Resources on the Scrum Master Role

• Scrum in Practice: A hands-on training led by an expert in agile approaches. It includes practical insights and experience gained from many years of implementing agile practices in Czech companies.
• How many teams can an agile coach have at once? An article discussing how many teams an agile coach can handle simultaneously. Relevant also for the Scrum Master role.
• Everything I need to know as a Scrum master was not taught to me by a Scrum guide An article on professional growth by Senior Scrum Master Matěj Nešetřil.
• My experience with team scaling An article by Senior Scrum Master Matěj Nešetřil focusing on team scaling.
• Agile Performance Explore the agile services we offer.
• Agile Transformation We can help you with your company’s agile transformation.