2.3 The Scrum Master Accountability & True Leadership
Key Takeaways
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide by helping everyone understand theory and practice.
- The Scrum Master is accountable for the Scrum Team's effectiveness by enabling continuous improvement within the Scrum framework.
- The Scrum Master is a true leader who serves the Scrum Team, the Product Owner, and the broader organization.
- The Scrum Master causes the removal of impediments to the team's progress, focusing on systemic and organizational barriers.
- The Scrum Master holds no formal command-and-control authority over team members, leading instead through coaching and influence.
2.3 The Scrum Master Accountability & True Leadership
Scrum Guide 2020 Definition: The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master is accountable for the Scrum Team's effectiveness.
The Scrum Master (SM) accountability is frequently misunderstood in traditional corporate environments. Rather than acting as a traditional project manager, coordinator, or administrative secretary, the Scrum Master operates as a true leader who serves the Scrum Team, the Product Owner, and the broader enterprise.
Dual Core Accountabilities of the Scrum Master
The 2020 Scrum Guide cleanly encapsulates the Scrum Master’s role into two primary accountabilities:
- Establishing Scrum as Defined in the Scrum Guide: Ensuring that empirical process control (transparency, inspection, adaptation) and Scrum core values (commitment, focus, openness, respect, courage) are understood, enacted, and adhered to by the team and organization.
- Enabling Scrum Team Effectiveness: Fostering an environment where the team can continuously improve its engineering practices, team dynamics, self-management capabilities, and delivery of usable Increments.
Three Pillars of Service
The Scrum Master serves three distinct audiences: the Scrum Team, the Product Owner, and the broader Organization. Understanding these specific services is essential for passing the PSM I examination.
| Target Audience | Specific Services Provided by the Scrum Master |
|---|---|
| Service to the Scrum Team | • Coaching team members in self-management and cross-functionality.<br>• Helping the team focus on creating high-value Increments that meet the Definition of Done.<br>• Causing the removal of impediments to the team's progress.<br>• Ensuring all Scrum events take place and are positive, productive, and kept within the timebox. |
| Service to the Product Owner | • Helping find techniques for effective Product Goal definition and Product Backlog management.<br>• Helping the Scrum Team understand the need for clear and concise Product Backlog items.<br>• Helping establish empirical product planning for a complex environment.<br>• Facilitating stakeholder collaboration as requested or needed. |
| Service to the Organization | • Leading, training, and coaching the organization in its Scrum adoption.<br>• Planning and advising Scrum implementations within the enterprise.<br>• Helping employees and stakeholders understand and enact an empirical approach for complex work.<br>• Removing barriers between stakeholders and Scrum Teams. |
True Leader vs. Traditional Project Manager
A major focus of the PSM I assessment is distinguishing servant leadership from traditional command-and-control management:
Traditional Project Manager Scrum Master (True Leader)
--------------------------- --------------------------
• Directs daily tasks • Coaches self-management
• Assigns work to individuals • Enables team self-management
• Tracks individual status • Focuses on team effectiveness
• Manages project constraints • Protects empirical process & values
• Acts as central decision bottleneck • Removes organizational impediments
• Possesses formal line authority • Leads through influence & coaching
Authority Without Command-and-Control
The Scrum Master does not possess formal line-management HR authority over team members. They cannot fire employees, set salaries, assign daily tasks, or write performance reviews. Instead, their authority stems from their deep knowledge of Scrum principles, their ability to facilitate productive collaboration, and their leverage of transparency to expose process bottlenecks and organizational anti-patterns.
Causing the Removal of Impediments
One of the most frequently tested concepts on the PSM I exam is the Scrum Master's accountability regarding impediments.
What is an Impediment?
An impediment is any obstacle that prevents the Scrum Team from delivering value, achieving the Sprint Goal, or improving its effectiveness. Examples include:
- Unavailability of necessary hardware, software licenses, or cloud infrastructure.
- Inter-team dependencies and departmental silos.
- Lack of access to key business stakeholders or domain experts.
- Severe team conflicts or toxic communication habits.
"Causing" vs. "Resolving Everything Personally"
Notice the precise phrasing in the Scrum Guide: the Scrum Master is accountable for causing the removal of impediments. This does not mean the Scrum Master personally fixes every technical bug or configures every server.
- If an impediment can be resolved by the Developers (such as resolving a merge conflict or asking a teammate for assistance), the Scrum Master coaches them to handle it self-sufficiently.
- If an impediment is organizational or external (such as corporate procurement delays or security policy roadblocks), the Scrum Master actively intervenes with management to remove the barrier.
Facilitating Scrum Events
The Scrum Master ensures that all five official Scrum events occur and are kept within their designated timeboxes. However, facilitation does not mean the Scrum Master acts as a mandatory meeting chairperson:
- Sprint Planning: Ensures the event occurs and the team understands its purpose.
- Daily Scrum: Ensures Developers hold the event daily; teaches Developers to keep it within 15 minutes. The Scrum Master does not need to attend or conduct it.
- Sprint Review: Ensures the event is held as an informal working session, not a passive presentation.
- Sprint Retrospective: Ensures a safe environment for self-inspection and actionable improvement planning.
Common PSM I Exam Traps for Scrum Masters
Trap 1: The Scrum Master Assigns Tasks
Incorrect Scenario: The Scrum Master assigns Sprint Backlog items to Developers based on individual skill sets during Sprint Planning. Correct Scrum Behavior: Developers select their own work and self-manage task allocation throughout the Sprint.
Trap 2: The Scrum Master Solves Technical Problems
Incorrect Scenario: The Scrum Master steps in to rewrite broken code or fix database connection strings when Developers hit a roadblock. Correct Scrum Behavior: The Scrum Master encourages Developers to pair program, seek help, or adjust technical approaches, preserving Developer autonomy.
Trap 3: The Scrum Master Works for the Product Owner
Incorrect Scenario: The Scrum Master acts as an administrative assistant for the Product Owner, writing user stories and taking meeting notes. Correct Scrum Behavior: The Scrum Master is a peer to the Product Owner within the Scrum Team, coaching the PO in effective Scrum practices.
Summary Checklist for PSM I Candidates
- Accountable for establishing Scrum and overall Scrum Team effectiveness.
- Serves the Scrum Team, Product Owner, and Organization in specific empirical ways.
- True leader who serves; holds no command-and-control authority over team members.
- Accountable for causing the removal of impediments, not necessarily fixing everything personally.
What is the primary accountability of the Scrum Master regarding team effectiveness?
The Developers encounter a corporate firewall policy restriction that prevents deploying test builds. Who is accountable for causing the removal of this impediment?
How does a Scrum Master serve the Product Owner?