Scrum Master Anti-Patterns and How to Fix Them

What Makes an Anti-Pattern Dangerous

Anti-patterns are not obvious failures. They're practices that feel normal — maybe even correct — but consistently undermine team effectiveness. A Scrum Master who falls into anti-patterns often believes they're doing a good job because the ceremonies happen on time and the board looks tidy. But the team isn't improving, velocity is stagnant, and retrospective actions never get completed.

The Twelve Most Common Anti-Patterns

1. The Secretary

What it looks like: The Scrum Master's primary activity is updating Jira, writing meeting notes, and sending status emails. They've become an administrative assistant rather than a coach.

Why it's harmful: The team never learns to self-manage. They depend on the SM for basic coordination that should be distributed. The SM has no time for coaching, impediment removal, or organisational change.

Fix: Stop doing administrative work for the team. Teach them to update their own board, write their own notes, and communicate their own status. The SM's job is to make themselves unnecessary for day-to-day operations.

2. The Police Officer

What it looks like: The SM enforces Scrum rules rigidly. "The Scrum Guide says..." is their most common phrase. They correct team members publicly for process violations and treat Scrum as a set of laws rather than a framework.

Why it's harmful: Teams comply out of fear rather than understanding. They follow the letter of Scrum without embracing its spirit. Innovation and experimentation are suppressed because "that's not how Scrum works."

Fix: Explain the why behind practices, not just the what. Let the team experiment with adaptations. If a practice isn't working, help them understand the underlying principle and find a better approach — not force compliance.

3. The Hero

What it looks like: The SM solves every problem personally. Blocker? They fix it. Conflict? They mediate immediately. Technical issue? They jump in. The team never develops its own problem-solving capability.

Why it's harmful: The team becomes dependent. When the SM is unavailable, everything stalls. Team members don't develop resilience, conflict resolution skills, or the ability to remove their own impediments.

Fix: Coach, don't solve. When a team member raises a blocker, ask: "What have you tried? Who else could help? What would you do if I weren't here?" Only intervene directly for impediments that genuinely require organisational authority.

4. The Absent Scrum Master

What it looks like: The SM facilitates ceremonies and disappears between them. They're not present during the sprint, don't observe team dynamics, and only engage when something goes visibly wrong.

Why it's harmful: Problems fester unnoticed. Team dynamics deteriorate without coaching. Impediments accumulate because nobody is actively looking for them. The SM misses the subtle signals that predict bigger issues.

Fix: Be present. Observe standups (even if not facilitating). Have informal conversations with team members. Walk the board daily. The best coaching opportunities happen between ceremonies, not during them.

5. The Metrics Obsessive

What it looks like: The SM tracks every possible metric and presents elaborate dashboards. Velocity, cycle time, throughput, defect density, code coverage — all measured, all reported, all used to evaluate team performance.

Why it's harmful: Metrics become targets. Teams game velocity by inflating estimates. They avoid difficult work that might hurt their numbers. The focus shifts from delivering value to optimising metrics.

Fix: Track fewer metrics. Use them for team self-improvement, never for performance evaluation. Let the team choose what to measure. Trends matter more than absolutes. If a metric isn't driving a specific improvement action, stop tracking it.

6. The Proxy Product Owner

What it looks like: The SM makes prioritisation decisions, writes user stories, or accepts work on behalf of the PO. They've filled the PO vacuum rather than coaching the PO to be effective.

Why it's harmful: The PO never develops. The SM makes product decisions without the business context to make them well. Accountability becomes blurred — who actually owns the product?

Fix: Coach the PO, don't replace them. If the PO is unavailable, escalate — don't compensate. Make the organisational dysfunction visible rather than hiding it.

7. The Meeting Scheduler

What it looks like: The SM's primary contribution is ensuring ceremonies happen at the right time. They book rooms, send invites, and start meetings on time — but add no facilitation value once the meeting begins.

Why it's harmful: Ceremonies become routine rather than valuable. Without skilled facilitation, standups become status reports, retrospectives become complaint sessions, and planning becomes estimation theatre.

Fix: Invest in facilitation skills. Vary retrospective formats. Ask powerful questions in standups. Challenge the team in planning. The SM's value is in the quality of conversations, not the logistics of scheduling them.

8. The Conflict Avoider

What it looks like: The SM avoids difficult conversations. They don't address team members who dominate discussions, don't challenge the PO on unclear stories, and don't escalate organisational impediments that require uncomfortable conversations with leadership.

Why it's harmful: Problems persist because nobody names them. Psychological safety erodes because issues are felt but never addressed. The team loses respect for the SM's ability to protect them.

Fix: Develop courage (a Scrum value). Practice having difficult conversations in low-stakes situations first. Use frameworks like SBI (Situation-Behaviour-Impact) to structure feedback. Remember: avoiding conflict is not the same as maintaining peace.

9. The Multi-Team Scrum Master (Spread Too Thin)

What it looks like: The SM serves 3-4 teams simultaneously. They attend ceremonies for all teams but have no time for coaching, observation, or impediment removal for any of them.

Why it's harmful: Each team gets a fraction of the attention they need. The SM becomes a ceremony facilitator rather than a coach. Teams stagnate because there's no one investing in their improvement.

Fix: One SM per 1-2 teams maximum. If the organisation insists on more, make the trade-off visible: "I can facilitate ceremonies for 4 teams, or I can coach 2 teams to high performance. Which do you want?"

10. The Velocity Pusher

What it looks like: The SM celebrates velocity increases and expresses concern when velocity drops. They encourage the team to "stretch" and take on more work each sprint.

Why it's harmful: Velocity becomes a performance target. Teams inflate estimates, cut corners on quality, and burn out trying to show continuous improvement in a number that should be stable.

Fix: Never celebrate or criticise velocity. Use it only as a planning input. Celebrate outcomes: Sprint Goals achieved, customer problems solved, quality improvements made. Velocity is a thermometer, not a thermostat.

11. The Report Generator

What it looks like: The SM spends significant time creating reports for management — sprint reports, velocity charts, burndown analyses, team performance summaries. They've become a reporting layer between the team and leadership.

Why it's harmful: The SM's time is consumed by upward reporting rather than team coaching. The reports often serve management's desire for control rather than the team's need for improvement. Transparency should come from the board itself, not from SM-generated reports.

Fix: Make the board the single source of truth. Teach stakeholders to read the board directly. Automate any reporting that's genuinely needed. Redirect time from reporting to coaching.

12. The Unchanging Facilitator

What it looks like: Every retrospective uses the same format. Every standup follows the same three questions. Every planning session has the same structure. The SM never experiments with new approaches.

Why it's harmful: Teams get bored. The same format surfaces the same insights. Engagement drops. Retrospectives become "that meeting we have to attend" rather than a genuine improvement opportunity.

Fix: Rotate retrospective formats every 2-3 sprints. Try different standup approaches (walk the board, focus on blockers only, async updates). Experiment with planning techniques. Keep ceremonies fresh and purposeful.

Self-Assessment

Ask yourself honestly:

• When was the last time a team member solved a problem without my help?
• Do I spend more time on administration or coaching?
• Has the team measurably improved in the last quarter?
• Could the team run a sprint effectively without me?
• Am I addressing the hard problems or avoiding them?

If the answers are uncomfortable, pick one anti-pattern to address this sprint. Sustainable improvement comes from fixing one thing at a time.

---

Use the [Retrospective Toolkit template](/templates) to vary your retro formats and keep the team engaged.