Primary description of the Scrum Master (Scrum Guide 2020)

A **leader who serves** the Scrum Team and the organization by enabling Scrum and empiricism.

Scrum Master service to Product Owner

Coaches on Product Goal and backlog, facilitates collaboration with Developers, teaches stakeholder engagement; does not own the backlog or priorities.

Scrum Master service to Developers

Coaches on self-management, facilitates Scrum events, helps remove impediments, supports quality and transparency; does not assign tasks or manage individuals.

The people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint.

A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.

Someone who designs and guides group processes and meetings so that participants can achieve effective outcomes.

What is Anti-pattern?

A common response to a recurring problem that is usually ineffective and risks being counterproductive.

The Scrum Master: Stances, Service, and Anti‑Patterns — Professional Scrum Master I (PSM I) Exam Power Prep

Step 1 – Reframing the Scrum Master Today

Scrum Master in 2026

The current Scrum Guide (2020, still current in 2026) defines the Scrum Master as a leader who serves, not a project manager or team boss.

Self-Managing Team

Scrum Teams are self-managing: they decide who does what, when, and how. The Scrum Master does not assign tasks or manage people.

Core Stances

Think of the Scrum Master as a coach, facilitator, change agent, and servant leader for the Scrum Team and the organization.

Exam Shortcut

If the Scrum Master is enabling empiricism and removing impediments → likely correct. If they are controlling people or collecting status → likely an anti-pattern.

Step 2 – Scrum Master Service to the Product Owner

Serving the Product Owner

The Scrum Master helps the Product Owner maximize value by coaching, facilitating, and teaching—not by deciding requirements or deadlines.

Backlog & Goal Coaching

They coach on Product Goal, Product Backlog ordering, and empirical planning so the backlog is transparent, understood, and value-focused.

Collaboration & Refinement

They facilitate collaboration between PO and Developers, especially during Product Backlog refinement and clarification of PBIs.

Not a Proxy PO

The Scrum Master does not own the backlog, set priorities, or act as a proxy PO. Challenging and supporting the PO is good; replacing them is not.

Step 3 – Example: Helping (Not Replacing) the Product Owner

Scenario Setup

A busy Product Owner asks the Scrum Master: "Can you prioritize the backlog for the next Sprints?" The backlog is huge and unordered.

Anti-Pattern Response

The Scrum Master reorders the backlog and tells Developers what to build. The PO loses ownership; accountability is blurred.

Healthy Response

The Scrum Master refuses to take over prioritization, coaches on value-based ordering, and helps set a clear Product Goal.

Facilitation, Not Control

They organize a refinement workshop with PO and Developers, keeping accountability with the PO while improving collaboration.

Step 4 – Scrum Master Service to the Developers

Serving Developers

The Scrum Master helps Developers create a self-managing environment to deliver a usable Increment every Sprint.

Self-Management Coaching

They coach Developers to create their own Sprint plan and manage the Sprint Backlog without external task assignment.

Events & Impediments

They ensure Scrum events are effective and help remove impediments, especially systemic ones that the team cannot remove alone.

Not a Task Master

They do not assign tasks, track individual performance, or turn the Daily Scrum into a status meeting or pressure session.

Step 5 – Thought Exercise: Daily Scrum Stances

Imagine you are observing a Daily Scrum.

Three different Scrum Masters behave differently:

Scrum Master A stands in front of the board and points to each Developer: "What did you do yesterday? What will you do today? Any blockers?" They take notes for a status report.
Scrum Master B reminds Developers of the 15-minute timebox and the goal: "Use this time to inspect progress toward the Sprint Goal and adapt your plan." Then they step aside and listen.
Scrum Master C does not show up. The Developers still meet, inspect progress toward the Sprint Goal, and adjust their plan.

Questions for yourself:

Which Scrum Master shows a command-and-control stance?
Which one shows a servant leader / coach stance?
In an exam question, which behavior would Scrum.org likely consider most appropriate once the team is mature?

Write down your answers before you move on, then compare:

A = command-and-control, status reporter.
B = servant leader / coach (especially for newer teams).
C = may be perfectly fine for a mature, self-managing team.

Key takeaway: The Scrum Master’s goal is to make the team less dependent on them over time, not more.

Step 6 – Scrum Master Service to the Organization

Change Agent Role

The Scrum Master serves the wider organization by acting as a change agent, helping people understand and adopt Scrum.

Training & Coaching

They train and coach managers and teams in Scrum theory and values, clarifying what Scrum is and is not.

Systemic Impediments

They work with leadership to remove systemic impediments, like rigid approvals or silos that block empiricism.

Not Scrum Police

They do not enforce Scrum as a rigid checklist or punish teams. They educate, influence, and collaborate instead.

Step 7 – Preferred vs Misunderstood Scrum Master Stances

Helpful Stances

Helpful Scrum Master stances: servant leader, coach, facilitator, and change agent.

Servant Leader & Coach

Servant leaders focus on others’ needs; coaches use questions and feedback to help individuals and the team learn.

Facilitator & Change Agent

Facilitators design effective events; change agents challenge the status quo and promote agile values.

Harmful Stances

Harmful stances: traditional project manager, secretary/scribe, and boss/team manager controlling people and performance.

Step 8 – Common Scrum Master Anti-Patterns

What Is an Anti-Pattern?

Anti-patterns are behaviors that seem helpful but actually harm Scrum, like controlling people or taking over others’ accountabilities.

Command-and-Control

Assigning tasks, deciding who does what, and telling Developers how to work are classic command-and-control anti-patterns.

Status Cop & Micro-Manager

Using Daily Scrum for status reports or constantly checking "Are you done yet?" are status reporting and micro-management patterns.

Proxy PO & Event Owner

Prioritizing the backlog instead of the PO or insisting on running every event yourself both show the Scrum Master taking over others’ roles.

Step 9 – Quick Check: Spot the Anti-Pattern

Choose the option that best aligns with Scrum.org’s view of a healthy Scrum Master stance.

A new Scrum Team struggles to run effective Sprint Retrospectives. What is the BEST action for the Scrum Master?

Take full control of the Retrospective, decide the improvements, and assign actions to each Developer.
Facilitate the Retrospective using a simple structure, encourage everyone to speak, and help the team choose and own a few concrete improvements.
Ask the Product Owner to run the Retrospective and decide which Developers need to improve their performance.

Show Answer

Answer: B) Facilitate the Retrospective using a simple structure, encourage everyone to speak, and help the team choose and own a few concrete improvements.

Option 2 shows the Scrum Master as a **facilitator and coach**, helping the team learn to inspect and adapt while keeping ownership with them. Option 1 is command-and-control and micro-management. Option 3 misplaces accountability (the PO does not run Retrospectives or manage individual performance).

Step 10 – Flashcard Review: Stances and Service

Flip through these cards to reinforce key ideas about Scrum Master service, stances, and anti-patterns.

Primary description of the Scrum Master (Scrum Guide 2020): A **leader who serves** the Scrum Team and the organization by enabling Scrum and empiricism.
Scrum Master service to Product Owner: Coaches on Product Goal and backlog, facilitates collaboration with Developers, teaches stakeholder engagement; does not own the backlog or priorities.
Scrum Master service to Developers: Coaches on self-management, facilitates Scrum events, helps remove impediments, supports quality and transparency; does not assign tasks or manage individuals.
Scrum Master service to the organization: Leads, trains, and coaches in Scrum adoption, removes organizational impediments, supports cultural change; not a Scrum police officer.
Helpful Scrum Master stances: Servant leader, coach, facilitator, change agent.
Harmful Scrum Master stances: Traditional project manager, secretary/scribe, boss/team manager, proxy Product Owner.
Command-and-control anti-pattern: Scrum Master assigns tasks, decides who does what, and controls how work is done, reducing self-management.
Status reporting anti-pattern: Using Scrum events, especially Daily Scrum, to collect status for external managers instead of enabling team planning.

Key Terms

Developers: The people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint.
Daily Scrum: A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
Facilitator: Someone who designs and guides group processes and meetings so that participants can achieve effective outcomes.
Anti-pattern: A common response to a recurring problem that is usually ineffective and risks being counterproductive.
Change Agent: A person who helps an organization transform by challenging the status quo and promoting new ways of working.
Scrum Master: A leader who serves the Scrum Team and the organization by helping everyone understand and apply Scrum and empiricism.
Product Owner: The person accountable for maximizing the value of the product resulting from the work of the Scrum Team, primarily through Product Backlog management.
Servant Leader: A leadership style where the leader focuses on serving the needs of others and enabling their growth and performance.
Product Backlog: An emergent, ordered list of what is needed to improve the product, the single source of work for the Scrum Team.
Command-and-control: A management style where decisions, tasks, and methods are dictated from above, leaving little autonomy to the team.