The Scrum Master is the “servant leader” of the Scrum Team who moderates and facilitates team interactions as team coach and motivator. The Scrum Master is responsible for ensuring that the team has a productive work environment by guarding the team from external influences, removing any obstacles, and enforcing Scrum principles, aspects, and processes.
The Scrum Master has many responsibilities, and they change depending on which process is being conducted. For example, during the develop epics process, the Scrum Master facilitates creation of the epics and personas.
The table given below summarizes the Scrum Master’s responsibilities in the various Scrum processes.
Processes |
Scrum Master Responsibilities |
Idetify Scrum Master and Stakenholder(s) |
|
Form Scrum Team |
|
Develop Epic(s) |
|
Create Prioritized Product Backlog |
|
Conduct Release Planning |
|
Create User Stories |
|
Approve, Estimate and Commit User Stories |
|
Create Tasks |
|
Estimate Tasks |
|
Create Sprint Backlog |
|
Create Deliverables |
|
Conduct Daily Standup |
|
Groom Prioritized Product Backlog |
|
Convene Scrum of Scrums |
|
Demonstrate and Validate Sprints |
|
Retrospect Sprint |
|
Retrospect Project |
|
Responsibilities of the Scrum Master in Scrum Processes
Chief Scrum Master
Large projects require multiple Scrum Teams to work in parallel. Information gathered from one team may need to be appropriately communicated to other teams. The Chief Scrum Master is responsible for this activity.
Coordination across various Scrum Teams working on a project is typically done through the Scrum of Scrums (SoS) Meeting ). This is analogous to the Daily Standup Meeting and is facilitated by the Chief Scrum Master. The Chief Scrum Master is typically the individual responsible for addressing impediments that impact more than one Scrum Team.
Typically, any inter-team issues are addressed by the interested parties in a session immediately following the Scrum of Scrums. The Chief Scrum Master facilitates this session.