Scrum Master Anti-Patterns

Overview

• What you’ll learn: The most common Scrum Master anti-patterns, how to recognize them, why they develop, and how to correct course.
• Prerequisites: Lesson 11 — The Scrum Master.
• Estimated reading time: 13 minutes

Introduction

A well-intentioned Scrum Master can still undermine Scrum. Anti-patterns develop silently — the SM takes on too much responsibility, becomes a gatekeeper, or fades into the background. Recognizing these patterns is the first step to correcting them.

The Anti-Pattern Gallery

The Helicopter SM

This SM hovers above the team, swooping in at the first sign of conflict or difficulty. They solve problems the team should solve themselves, make decisions the team should make, and schedule meetings the team didn’t ask for. The result: a team that never learns to self-manage because someone always catches them before they fall.

Fix: Step back. Let the team struggle. Be available for coaching, but let them find their own solutions.

The Secretary SM

This SM’s contribution is limited to booking meeting rooms, sending calendar invites, and taking meeting notes. They ensure events happen on time but add no value in terms of coaching, facilitation, or impediment removal.

Fix: Invest in facilitation skills. The SM’s value is in making events productive, not just punctual.

The Invisible SM

Nobody knows this SM exists. They are nominally assigned but rarely present, rarely engaged, and contribute nothing to the team’s effectiveness. Often this happens when someone is SM for multiple teams and stretched too thin.

Fix: Limit the number of teams per SM. One or two teams max. Be present and engaged.

The Police Officer SM

This SM enforces Scrum rules rigidly without understanding the principles behind them. “The Scrum Guide says 15 minutes!” they shout, cutting off a valuable conversation. They prioritize compliance over effectiveness.

Fix: Understand the “why” behind each Scrum rule. The rules serve the values; enforce the values, coach the rules.

The Project Manager SM

This SM assigns tasks, tracks burndown charts, and reports status to management. They control the team rather than serve it. This is the most common anti-pattern in organizations transitioning from traditional project management.

Fix: Stop assigning tasks. Stop reporting status on behalf of the team. Coach transparency and let the team own their process.

The Hero SM

This SM removes all impediments personally, even those the team or organization should handle. They become a bottleneck — everything goes through them, and when they are unavailable, the team is stuck.

Fix: Teach the team to remove their own impediments. Escalate organizational impediments but empower the team for technical ones.

How Anti-Patterns Develop

• Organizational pressure: Management expects the SM to “manage” the team, so the SM falls into PM behaviors.
• Team immaturity: New teams need more guidance, and the SM over-corrects by becoming too directive.
• Lack of training: Many SMs have a two-day certification but limited coaching or facilitation experience.
• Multiple teams: An SM serving 4–5 teams cannot be effective for any of them.

Key Takeaways

• Anti-patterns develop silently — regular self-reflection and team feedback are essential.
• The most common anti-patterns: Helicopter, Secretary, Invisible, Police Officer, PM, Hero.
• Root causes are usually organizational pressure, team immaturity, or lack of SM training.
• The cure is usually the same: step back, trust the team, focus on coaching over controlling.

What’s Next

In Lesson 15, you will explore stakeholder management in Scrum — how the PO manages expectations, communicates priorities, and keeps everyone aligned without making promises the team cannot keep.