Agile Glossary

Scrum Master

What is Scrum Master?

The Scrum Master is the team role responsible for ensuring the team lives agile values and principles and follows the processes and practices that the team agreed they would use.

The responsibilities of this role include:

  • Clearing obstacles
  • Establishing an environment where the team can be effective
  • Addressing team dynamics
  • Ensuring a good relationship between the team and product owner as well as others outside the team
  • Protecting the team from outside interruptions and distractions.

The scrum master role was created as part of the Scrum framework.  The name was initially intended to indicate someone who is an expert at Scrum and can therefore coach others.

The role does not generally have any actual authority. People filling this role have to lead from a position of influence, often taking a servant-leadership stance.


Also Known As

Scrum Master is typically the term used to refer to this role, even by teams not explicitly following Scrum. Other terms used infrequently include iteration manager, agile coach, or team coach.


Expected Benefits

The general benefit expected from having a scrum master on a team is providing a self-organizing team with ongoing access to someone who has used agile, and Scrum in particular in another setting and can help the team figure out the best way to apply it in their situation.

Another expected benefit is that the scrum master is someone that can address distractions, disruptions, and obstacles so that the remainder of the team is free to focus on the work of producing output that will generate the desired outcome.


Common Pitfalls

While having a scrum master can provide several benefits, there are also several problems that arise from the improper application of the role. Those problems include:

  • Assuming that you can just slide project managers who are used to command and control type leadership into a scrum master role and expect them to be effective.
  • Asking someone to fill the scrum master role without any experience working in an agile setting
  • Expecting the workload for a scrum master to be the same on every team irrespective of how long the team has worked together, their understanding of agile values and principles, and their experience in the domain. A well-functioning team will most likely need much less coaching from a scrum master than a team new to working with each other and in agile values and principles

Skill Levels

While there are no officially defined levels of skill for scrum masters, in practice there are different levels of experience:

  • Rotating Scrum Master – members of a team rotate scrum master responsibilities (primarily the administrative ones) amongst each other on a sprint-by-sprint basis
  • Part-time Scrum Master – one individual on the team takes on Scrum Master responsibilities in addition to other responsibilities on the same team.
  • Full-time dedicated Scrum Master – one individual’s sole responsibility is as a scrum master for one time. This model is best suited for a team learning agile
  • Full-time Scrum Master with more than one team – this model is quite frequently applied where an individual’s sole responsibility is to be a scrum master, but they work with more than one team
  • Agile Coach – An individual does not have a specifically assigned team but works with several teams and only on specific needs.

Further Reading

Scrum Master definition in the Scrum Guide

Add to Bookmarks Remove Bookmark
Add to Bookmarks Remove from Bookmarks
Add to Bookmarks Remove from Bookmarks

Thank you to our Annual Partners​

Join us today!

Agile Alliance offers many online and in-person events and workshops for our members. If you’re not currently a member, you can join now to take advantage of our many members-only resources and programs.

Get the latest Agile news!

  • This field is for validation purposes and should be left unchanged.

By subscribing, you acknowledge the Agile Alliance Privacy Policy, and agree to receive our emails.

Additional Agile Glossary Terms

An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios.
Test-driven development (TDD) is a style of programming where coding, testing, and design are tightly interwoven. Benefits include reduction in defect rates.
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities for improvement.
A product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver in order to achieve a specific outcome.
An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios.
Test-driven development (TDD) is a style of programming where coding, testing, and design are tightly interwoven. Benefits include reduction in defect rates.
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities for improvement.

Help us keep the definitions updated

Discover the many benefits of membership

Your membership enables Agile Alliance to offer a wealth of first-rate resources, present renowned international events, support global community groups, and more — all geared toward helping Agile practitioners reach their full potential and deliver innovative, Agile solutions.

Not yet a member? Sign up now