Scrum Master
In short
The Scrum Master is the Scrum accountability that helps a team and its organization use Scrum well by coaching, facilitating events, and removing impediments.
What is a Scrum Master?
The Scrum Master is one of the three accountabilities in Scrum, alongside the Product Owner and the Developers. The Scrum Master is responsible for helping the Scrum team use Scrum effectively so it can deliver value and keep improving. Instead of managing people or assigning tasks, the Scrum Master coaches the team, the Product Owner, and the wider organization; the 2020 Scrum Guide describes the role as true leaders who serve the team and the organization, replacing the older phrase servant leader.
Typical work includes removing impediments, the obstacles the team can't clear by itself, such as waiting on another department; making sure Scrum events take place, stay productive, and stay within their timebox; and facilitating when the team asks. The Scrum Master also helps the Product Owner with backlog techniques, coaches the team in self-management and cross-functional skills, and works with the organization to change structures that slow teams down, such as long approval chains. Some Scrum Masters serve two or three teams, and in smaller companies a Developer may take on the role part-time.
A Scrum Master is like a sports coach: they don't play in the game, but they help the players improve, notice patterns the team can't see from the field, and clear obstacles out of the way. Their success shows in how effective and self-managing the team becomes, not in how busy they look.
A Scrum Master is often confused with a project manager. A project manager traditionally plans the schedule, assigns tasks, tracks the budget, and is accountable for delivery, while in Scrum planning and task decisions belong to the team and scope decisions belong to the Product Owner. The Scrum Master is also not the team's secretary or the only person allowed to run meetings, and unlike the Product Owner, the role focuses on how the team works rather than on what it builds.
Key takeaways
- The Scrum Master helps the team and organization use Scrum effectively.
- Core duties are coaching, facilitating, and removing impediments.
- The role leads by serving, not by assigning tasks or managing people.
- A Scrum Master is not a project manager.
- Success is measured by the team's effectiveness and self-management.
Readers ask
What is the difference between a Scrum Master and a project manager?
A project manager usually plans the work, assigns tasks, and is accountable for schedule and budget. A Scrum Master doesn't direct the work; they coach the team, facilitate Scrum events, and remove impediments so the team can manage itself.
Is a Scrum Master a full-time role?
It can be. Many Scrum Masters work full-time with one to three teams, while in smaller organizations a team member may take on the role alongside development work.
What is an impediment in Scrum?
An impediment is anything that blocks or slows the team and that it can't easily resolve by itself, such as a missing access right, a broken test environment, or a dependency on another team.
See also
- Product OwnerTeams & Process, p. 18The Product Owner is the Scrum accountability responsible for maximizing a product's value by deciding what to build next and ordering the product backlog.
- ScrumTeams & Process, p. 21Scrum is an Agile framework in which a small team delivers a product in fixed-length cycles called sprints, using defined roles, events, and artifacts.
- Daily StandupTeams & Process, p. 6A daily standup is a short daily meeting, usually 15 minutes or less, where a team checks progress toward its goal, plans the day, and raises blockers.
- RetrospectiveTeams & Process, p. 20A retrospective is a team meeting held at the end of each sprint to reflect on how the team worked and agree on concrete ways to improve next time.
- SprintTeams & Process, p. 26A sprint is a fixed-length period of one month or less, often two weeks, in which a Scrum team works toward one goal and produces a usable product increment.
- AgileTeams & Process, p. 2Agile is an approach to software development that delivers working software in small, frequent increments and adjusts plans based on regular feedback.
Spotted a mistake or something missing on this page?Suggest an edit