2.6 Leadership Stances of the Scrum Master

2.6 Leadership Stances of the Scrum Master

Empirical Leadership Context: A Scrum Master is a true leader who serves. To succeed in complex, changing environments, the Scrum Master must fluidly adopt different leadership stances depending on the maturity of the Scrum Team, the nature of challenges, and organizational context.

Navigating the Scrum Master role requires far more than memorizing rules. On the PSM I examination and in professional practice, candidates must understand how a Scrum Master acts in real-world scenarios—knowing when to coach, when to teach, when to facilitate, and when to step back.

---

Effective Leadership Stances

A mature Scrum Master utilizes six primary effective stances to help the Scrum Team and organization flourish:

---

Ineffective Stances (Anti-Patterns to Avoid)

The PSM I exam frequently presents scenarios describing anti-pattern stances. Recognizing these negative patterns is crucial for choosing the correct exam responses.

                         INEFFECTIVE STANCES
                       (Anti-Patterns to Avoid)
                                  |
    +-----------------+-----------+-----------+-----------------+
    |                 |                       |                 |
[ The Hero ]  [ The Scrum Police ]    [ The Administrator ]  [ The Chair ]
Rescues team  Enforces rigid rules     Focuses on booking     Directs meetings
& creates     without empirical        rooms & updating       like a command
dependence.   understanding.           tooling tasks.         boss.

Anti-Pattern 1: The Hero

The Scrum Master constantly jumps in to solve every problem, write meeting notes, fix technical bugs, and shield the team from all external contact.

• Impact: Creates team helplessness, prevents self-management, and makes the Scrum Master a single point of failure.

Anti-Pattern 2: The Scrum Police (Dogmatist)

The Scrum Master enforces rules blindly ("The Scrum Guide says we must do X!"), acting as a rigid compliance officer without teaching why empirical principles matter.

• Impact: Generates team resentment, stifles psychological safety, and turns Scrum into a bureaucratic process.

Anti-Pattern 3: The Administrator / Scribe

The Scrum Master spends their day updating Jira boards, booking meeting rooms, ordering lunches, and taking notes during events.

• Impact: Reduces a strategic leadership role to secretarial administration, ignoring team effectiveness and organizational change.

Anti-Pattern 4: The Chairperson / Command-and-Control Boss

The Scrum Master runs the Daily Scrum like a project status meeting, demanding individual reports and assigning daily tasks.

• Impact: Destroys Developer self-management and reduces accountability.

---

Stance Selection in Real-World Contexts

A master Scrum Master constantly reads the room and assesses team maturity to choose the appropriate stance:

Team Maturity Level                  Primary Stance Required
-------------------                  -----------------------
Newly Formed Team          ===>      Teacher & Facilitator (Establish basics)
Developing / Growing Team  ===>      Coach & Mentor (Build self-management)
High-Performing Team       ===>      Change Agent & Impediment Remover (Focus on org level)

Scenario A: Team Argues Over Estimation

• Poor Choice (Hero/Chair): The Scrum Master dictates: "This story is 5 story points, move on."
• Good Choice (Facilitator/Coach): The Scrum Master asks: "What assumptions are we making that cause such different estimates? How can we break this item down to reduce uncertainty?"

Scenario B: Management Demands Weekly Status Reports

• Poor Choice (Administrator): The Scrum Master creates a manual weekly status spreadsheet and fills it out every Friday.
• Good Choice (Change Agent/Teacher): The Scrum Master meets with management to explain how the transparent Product Backlog and Sprint Review fulfill status visibility empirically, removing the need for manual reports.

---

The Scrum Master as Organizational Change Agent

The PSM I assessment heavily emphasizes that the Scrum Master's job is not contained solely within the Scrum Team.

As an organizational Change Agent, the Scrum Master works with executives, HR, managers, and other Scrum Masters to:

• Shift performance measurement from individual utilization metrics to team-based value delivery.
• Redesign physical and virtual workspaces to support collaboration.
• Align organizational budgeting and governance with iterative, empirical planning.
• Promote psychological safety and a culture of continuous learning across the enterprise.

---

Summary Checklist for PSM I Candidates

• Effective stances: Coach, Facilitator, Teacher, Mentor, Change Agent, Impediment Remover.
• Ineffective anti-patterns: Hero, Scrum Police, Administrator, Chairperson, Micro-manager.
• Stance selection depends on context, team maturity, and organizational needs.
• The Scrum Master serves as a Change Agent across the broader organization, not just inside the team.