SkarpChapter 5 of 21
Scrum Accountabilities II: Scrum Master as True Leader and Servant-Leader
Look beyond the title to understand how the Scrum Master establishes Scrum, coaches the organization, and navigates common misunderstandings about authority and control.
Reframing the Scrum Master Role
Why This Module Matters
You now deepen your understanding of the Scrum Master as a true leader and servant-leader, not a mini-project manager or coordinator.
Canonical Definition
Memorize this: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide." This is the foundation for exam questions.
Connecting to Earlier Modules
You already met the Scrum Team and Product Owner. Now you complete the picture with the Scrum Master’s accountability and stance.
Exam Angle
Many PSM I questions hide traps: confusing Scrum Master with project manager, people manager, or Scrum police. This module helps you avoid them.
Scrum Master Accountability: Establishing Scrum
Accountable, Not Doing Everything
Accountable means answerable for the outcome. The Scrum Master ensures Scrum is understood and enacted, but does not have to perform every activity personally.
Establishing Scrum on Three Levels
The Scrum Master works with the Scrum Team, the Product Owner, and the wider organization to help them actually use Scrum, not just talk about it.
Guarding Scrum’s Integrity
“As defined in the Scrum Guide” means resisting Scrum-but practices like skipping Retrospectives or turning Daily Scrum into status updates to a manager.
Exam Hint
On PSM I, when a scenario shows partial or distorted Scrum, the best answer usually moves the situation closer to the Scrum Guide definition.
Scrum Master as True Leader and Servant-Leader
Servant-Leadership Basics
A servant-leader focuses on people’s growth and well-being, leading by influence, coaching, and example rather than positional power or control.
How Scrum Masters Serve
They serve the Scrum Team, the Product Owner, and the organization by facilitating, coaching, and removing impediments to empiricism and flow.
True Leadership Is Active
True leaders are not passive. They are courageous, say no to anti-Scrum requests, and protect the team’s focus on the Sprint and Product Goals.
Exam Lens
If a Scrum Master in a question only schedules meetings or tracks reports, look for an answer where they step up as a coach and change agent.
What the Scrum Master Actually Does: Services Overview
Service to the Scrum Team
The Scrum Master coaches self-management, facilitates events, ensures artifacts and commitments are understood, and helps remove impediments.
Service to the Product Owner
They coach the Product Owner in Product Backlog management, clear Product and Sprint Goals, and effective stakeholder collaboration.
Service to the Organization
They lead and coach the wider organization in Scrum, working to remove systemic impediments and align structures with agile ways of working.
Exam Pattern
Correct answers usually show the Scrum Master increasing understanding of Scrum and empiricism, not taking control away from the team.
Concrete Scenarios: Appropriate Scrum Master Activities
Scenario 1: Daily Scrum as Status
Developers report to the Scrum Master. The Scrum Master should refocus them on inspecting progress toward the Sprint Goal and adapting their plan.
Scenario 2: Product Backlog Chaos
The Product Owner randomly reorders items. The Scrum Master coaches on ordering techniques and facilitates clarity around the Product Goal.
Scenario 3: Scrum as Ceremonies
Leaders see Scrum as just meetings. The Scrum Master educates them on Scrum as empiricism using real Increments to illustrate value.
Key Pattern
In all scenarios, the Scrum Master enables others to decide and learn, rather than taking control or making decisions for them.
What the Scrum Master Does NOT Do
No Task Assignment
Developers self-manage. The Scrum Master does not assign tasks; they may coach on planning but avoid micro-management.
No Line Management
The Scrum Master does not handle performance reviews, salaries, or approvals that create power imbalances within the Scrum Team.
No Proxy Product Owner
They do not own product priorities or accept work. Those are Product Owner accountabilities; the Scrum Master focuses on the process.
Exam Red Flags
Options where the Scrum Master assigns tasks, controls vacation, or acts as a cop are usually incorrect for PSM I.
Scrum Values and the Scrum Master’s Behavior
Values Overview
Scrum values are Commitment, Focus, Openness, Respect, and Courage. The Scrum Master models these in daily behavior.
Protecting Focus
They protect the team’s focus on the Sprint Goal, negotiating scope changes transparently instead of allowing constant interruptions.
Openness and Respect
They foster open discussion of problems and respect all participants, even when challenging existing habits or structures.
Courage in Practice
They have the courage to surface uncomfortable truths, like unmet Definition of Done or the need to cancel a Sprint.
Thought Exercise: Navigating Authority and Control
Work through these short thought experiments. Imagine you are the Scrum Master and decide how you would act. This builds your instinct for exam scenarios.
- Manager demands a detailed Gantt chart
- A senior manager says: “I need a fixed Gantt chart for the next 6 months from you, as Scrum Master.”
- Reflect: How can you respond while staying within your accountability? Consider:
- Explaining how empiricism and Sprints reduce risk.
- Offering a high-level forecast based on Product Backlog and past throughput, while clarifying uncertainty.
- Inviting the manager to Sprint Reviews to see real progress.
- Team asks you to decide technical approaches
- Developers say: “You decide which architecture we use; you’re the Scrum Master.”
- Reflect: How can you support their self-management instead of taking over?
- Facilitate a technical decision workshop.
- Encourage experiments and spikes.
- Remind them that technical decisions belong to Developers.
- Stakeholder bypasses the Product Owner
- A stakeholder comes to you: “Please slip this urgent feature into the Sprint, but don’t tell the Product Owner; they always say no.”
- Reflect: How do you protect Scrum and the Product Owner’s accountability?
- Redirect the conversation to the Product Owner.
- Explain how changes to the Sprint Backlog are handled.
Write down your chosen actions for each case. Check whether they:
- Respect accountabilities.
- Increase transparency and empiricism.
- Use your influence rather than authority.
Quiz 1: Core Accountability and Stance
Test your understanding of the Scrum Master’s core accountability and leadership stance.
Which statement best reflects the Scrum Master’s core accountability and stance according to the current Scrum Guide?
- The Scrum Master is accountable for assigning tasks to Developers and ensuring the Sprint is delivered on time.
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and leads by serving the Scrum Team and organization.
- The Scrum Master is accountable for maximizing the value of the product and deciding which Product Backlog items are implemented.
- The Scrum Master is accountable for managing individual performance reviews to keep the team productive.
Show Answer
Answer: B) The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and leads by serving the Scrum Team and organization.
The canonical definition is: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide." The Scrum Guide also describes the Scrum Master as a true leader who serves. Assigning tasks, maximizing product value, and managing performance reviews are not Scrum Master accountabilities.
Quiz 2: What Should the Scrum Master Do?
Apply your knowledge to a realistic scenario.
During the Daily Scrum, Developers are giving status updates directly to the Scrum Master, who records progress in a tracking tool. What is the most appropriate Scrum Master action?
- Continue the practice because it increases control and accurate reporting to management.
- Ask each Developer to send their status by email instead, to shorten the Daily Scrum.
- Coach Developers on the purpose of the Daily Scrum and encourage them to inspect progress toward the Sprint Goal and adapt their plan together.
- Cancel the Daily Scrum because it is clearly not working and replace it with a weekly status meeting.
Show Answer
Answer: C) Coach Developers on the purpose of the Daily Scrum and encourage them to inspect progress toward the Sprint Goal and adapt their plan together.
The Daily Scrum is for Developers to inspect progress toward the Sprint Goal and adapt their plan. The Scrum Master should coach them on this purpose and help them change the format so they talk to each other, not report to the Scrum Master. Increasing control, moving to email, or cancelling the event all move away from Scrum.
Key Term and Concept Review
Flip these cards (mentally or with your own notes) to reinforce core definitions and distinctions for PSM I.
- Scrum Master (canonical definition)
- "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide."
- Servant-leadership in Scrum
- A leadership stance where the Scrum Master serves the Scrum Team, Product Owner, and organization by coaching, facilitating, and removing impediments rather than using positional power.
- One thing the Scrum Master SHOULD do
- Coach the Scrum Team and organization in understanding and applying Scrum, including empiricism (transparency, inspection, adaptation) and Scrum values.
- One thing the Scrum Master should NOT do
- Assign tasks to Developers or manage their individual performance reviews; Developers self-manage and line management is a different role.
- Scrum value most needed to challenge anti-Scrum practices
- Courage: the Scrum Master needs courage to challenge harmful practices, surface problems, and protect the team’s focus on the Sprint and Product Goals.
- Service to the Product Owner
- Coaching on Product Backlog management, facilitating stakeholder collaboration, and helping communicate clear Product and Sprint Goals.
- Service to the Organization
- Leading and coaching the wider organization in Scrum adoption, helping remove systemic impediments, and collaborating with other Scrum Masters.
Pulling It Together and Next Study Moves
Core Takeaway
Remember: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide." They are a true leader who serves.
What You Can Now Do
You can explain servant-leadership, list appropriate and inappropriate Scrum Master activities, and relate Scrum values to tough situations.
Exam Heuristic
Prefer answers where the Scrum Master coaches, facilitates, and empowers; avoid ones where they control, assign, or take over others’ roles.
Your Next Study Moves
Run the Scrum accountabilities diagnostic, then a mock exam. Let spaced review and the gap guide deepen any remaining weak patterns.
Key Terms
- Increment
- An Increment is a concrete stepping stone toward the Product Goal.
- Developers
- Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
- Empiricism
- Scrum is founded on empiricism and lean thinking.
- Scrum Team
- The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
- Sprint Goal
- The Sprint Goal is the single objective for the Sprint.
- True leader
- In Scrum, a person who actively guides and influences positive change, protects empiricism and values, and serves the team and organization without relying on formal authority.
- Product Goal
- The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- Scrum Master
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
- Product Owner
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
- Sprint Backlog
- The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
- Product Backlog
- The Product Backlog is an emergent, ordered list of what is needed to improve the product.
- Definition of Done
- The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
- Servant-leadership
- A leadership approach in which the leader’s primary goal is to serve others, focusing on their growth, autonomy, and well-being, and leading mainly through influence, coaching, and example.