The Scrum Framework — Second Edition

This chapter retains the second edition’s historical and practical teaching context. The third-edition curriculum is also available in the contents below.

---

The Scrum Master - International Scrum Institute

Broadly speaking, it is the job of the Scrum Master to ensure that the Scrum Team adheres to the Scrum theory, practices and rules.

The Scrum Master is part of the Scrum Team and acts as a servant-leader for the Scrum Team. When a team is getting started, Scrum Master responsibilities may require full-time attention, leaving little capacity for implementation work. As the team develops, the workload may change and the Scrum Master may also contribute to implementation toward the Sprint Goal, provided this does not compromise their Scrum Master responsibilities.

Trust between the Scrum Master and the other team members is crucial. Allowing the team to help select its Scrum Master can support that trust, although management often makes the appointment. To support that trust, our recommendation is to avoid giving the Scrum Master line-management responsibility for team members. Combining those responsibilities can hinder open communication and collaborative decision-making.

Responsibilities of the Scrum Master

The Scrum Master has several important responsibilities:

• Help the Scrum Team manage external requests and avoid unnecessary disruptions
• Act as a change agent and help the team adapt its processes to improve productivity
• Coach the Scrum Team
• Help remove impediments to the Scrum Team’s progress
• Support effective communication between the developers and the Scrum Product Owner
• Help ensure that Scrum Events are productive and effective

In order to effectively do this, a number of skills are helpful:

• Moderation
• Coaching
• Development know-how

Guarding the Scrum Team / Removing impediments

An important job of the Scrum Master is to help the team handle "urgent requests". Line managers or the Product Owner may introduce unplanned work during a Sprint. Protecting the Sprint Goal helps the team aim for 100% focus on its agreed goal, without treating the initial task list as unchangeable. The developers and Product Owner can clarify and renegotiate scope as they learn. Requests that would disrupt the Sprint Goal can be postponed. Only the Product Owner can cancel a Sprint, and cancellation is appropriate when its goal becomes obsolete.

The developers within the Scrum Team should only concentrate on developing customer value by delivering potentially shippable functionality. The Scrum Master helps by removing impediments that block or hinder development. Examples could be organizing meetings, clarifying questions or performing supporting work.

Change agent

One of the cornerstones of the Scrum Framework is continuous improvement through inspection and adaptation. The Scrum Master helps make the Sprint Retrospective productive and supports the team in addressing the shortcomings it identifies.

Facilitation of Scrum Events

The Scrum Master helps ensure that the following events take place and are effective. This does not mean that the Scrum Master must chair every meeting or direct the developers’ Daily Scrum:

• Daily Scrum Meetings
• Sprint Planning Meetings
• Sprint Review Meetings
• Sprint Retrospective Meeting