6.3 Scrum Master Stances

The Scrum Master as a True Leader Who Serves

The 2020 Scrum Guide describes the Scrum Master as a true leader who serves the Scrum Team and the larger organization, and lists specific services: coaching team members in self-management and cross-functionality, helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done, causing the removal of impediments, ensuring all Scrum events take place, training, and causing the removal of barriers between stakeholders and the team. org competency content that organizes how a Scrum Master delivers those services — it is professional practice, not an additional set of Scrum rules.

PSM I expects you to recognize which service or stance fits a scenario, and to avoid stances that take ownership away from the team.

The Core Stances

None of these stances involves commanding the team. Even the impediment-remover stance is about clearing the path, not directing the work.

Coaching vs Teaching vs Mentoring

These three are the most commonly confused on PSM I, and the difference is about where the knowledge and the decision sit:

• Teaching is appropriate when the gap is knowledge — the team simply does not know a Scrum rule, event purpose, or accountability yet. You explain it directly. Teaching is content out from the expert.
• Coaching is appropriate when the team is capable but stuck, dependent, or not seeing its own options — you ask questions and hold space so they decide. You do not give the answer, even if you know it. Coaching is drawing answers out of the team.
• Mentoring is appropriate when someone wants the benefit of your experience — you share what you have seen work in similar situations, while explicitly leaving the choice with them.

A frequent exam trap: a strong, mature, self-managing team hits a minor problem and a weak answer chooses "teach them the rule again" or "the Scrum Master solves it." The better answer is usually to coach — ask questions and let the team own the solution — because over-teaching or fixing erodes self-management. The inverse trap also appears: a brand-new team that does not know the rules is best served by teaching, and choosing pure coaching ("only ask questions") leaves a knowledge gap unfilled.

Matching Stance to Team Maturity

• Forming / new team: heavier teaching and mentoring; the team needs the rules and some experienced guidance to get moving.
• Developing team: shift toward facilitation and coaching; let them practice deciding while you safeguard the process.
• Mature, effectively self-managing team: mostly light coaching, occasional facilitation, and change-agent work at the organizational level so the team keeps improving and is not held back by systemic obstacles.

The skill tested is deliberate stance selection, not memorizing labels. The wrong stance applied confidently is still the wrong answer. A useful heuristic for exam questions: pick the stance that grows the team's future capability while preserving its accountability — that is almost always coaching for a capable team and teaching for a team with a genuine knowledge gap.

Coaching Skills and Anti-Patterns

Coaching is the stance most often tested and most often misunderstood. Core coaching skills include active listening, asking powerful (open, non-leading) questions, reflecting back what the team says, and holding silence so the team thinks instead of waiting for the answer. Powerful questions are open-ended and forward-looking: "What options have you considered?", "What would Done look like here?", "What is getting in the way?" — never thinly disguised instructions like "Don't you think you should just do X?"

Watch for these stance anti-patterns, which routinely appear as wrong answers:

• The fixer: solving every problem for a capable team, creating dependency and eroding self-management.
• The over-teacher: re-explaining basics to an experienced team that needs coaching, not instruction.
• The absent Scrum Master: claiming 'self-management' as an excuse to disengage and stop serving.
• The boss: using authority to direct the work, which the Scrum Master never holds.

The Scrum Master also coaches individuals (a Developer struggling with a skill), the whole team (improving how they collaborate), the Product Owner (effective Product Backlog management and stakeholder engagement), and the organization (empiricism and agility at scale). Selecting the right stance for the right audience — and resisting the pull to simply give the answer — is the heart of this competency.