The Scrum Master is a servant-leader for the Scrum Team, responsible for promoting and supporting Scrum as defined in the Scrum Guide. They help everyone understand Scrum theory, practices, rules, and values. The Scrum Master is not a traditional project manager or team lead but a facilitator who helps the team become more effective.
Key Aspects of a Scrum Master
- Servant-Leader – The focus is on the needs of the team and the customer, rather than on exercising authority. They lead by serving, not by commanding.
- Coach & Mentor – They coach the Development Team in self-organization and cross-functionality and help the organization in its Scrum adoption.
- Impediment Remover – They are responsible for removing blockers that are hindering the Development Team’s progress.
- Facilitator – They facilitate Scrum events as requested or needed and ensure they are positive, productive, and kept within the timebox.
- Process Authority – They are the expert on the Scrum framework and ensure the team adheres to its principles and practices.
The Scrum Master’s Service
The Scrum Master serves the team and the wider organization in several ways:
| Service To | Description of Service |
|---|---|
| The Product Owner | Helps find techniques for effective Product Backlog management; facilitates stakeholder collaboration; ensures the Product Owner knows how to arrange the backlog to maximize value. |
| The Development Team | Coaches the team in self-organization; helps create high-value products; removes impediments to the team’s progress; facilitates Scrum events. |
| The Organization | Leads and coaches the organization in its Scrum adoption; plans Scrum implementations; helps employees and stakeholders understand and enact Scrum. |
Example Scenarios
Removing an Impediment
During a Daily Stand-up, a developer mentions they are blocked because they need access to a new software license. Immediately after the meeting, the Scrum Master takes ownership of this impediment, contacts the IT department, and works to get the license approved and installed, allowing the developer to continue their work.
Coaching the Team
The Scrum Master observes that Sprint Retrospectives are becoming stale and unproductive. They introduce the team to a new retrospective format (like “Starfish” or “Sailboat”) to facilitate a more engaging and insightful conversation about process improvement.
Why The Scrum Master Matters
- Protects the Team – They act as a shield, protecting the team from external interruptions and distractions so they can focus on the Sprint Goal.
- Fosters a Culture of Continuous Improvement – They are the champion for the Scrum process and guide the team in becoming more effective and efficient over time.
- Enables Self-Organization – By coaching and removing impediments, they help the team grow and mature into a truly self-organizing unit.
- Improves Scrum Implementation – They ensure the Scrum framework is being used correctly and effectively, which maximizes the benefits of agility.
See also: Development Team, Product Owner, Servant Leadership, Impediment, Scrum.