Key Anti-Patterns in Scrum
From the sources, the following anti-patterns are common in Scrum teams. Some have names
like “Scrum-but” or “Zombie Scrum,” others are behaviours in events or roles that undermine
Scrum.
1. “Scrum-but” / Backsliding to Traditional Habits
o Teams say they are doing Scrum, but actually default to old ways (e.g.
command-and-control, waterfall style handovers, heavy documentation,
etc.). TechTarget+2DZone+2
o For example, redefining requirements mid-sprint without involving the team,
making daily stand-ups into status reports rather than
collaboration. TechTarget+1
2. Micro-management / Loss of Self-Organization
o Scrum Master, Product Owner, or Stakeholders telling developers exactly how
to do tasks; “overassigning” or “commanding” instead of allowing the team to
decide. Typo+[Link]+2
o Scrum Master acting like a manager or technical lead rather than
coach/servant leader. [Link]
3. Overcommitment & Unrealistic Sprint Goals
o Taking on more work than the team can reliably complete, often due to
pressure or optimism bias. Leads to incomplete stories, constant
spillover. [Link]+2DZone+2
o Also under-committing sometimes, but more typical is
overcommitment. Medium+1
4. Ceremonies that only “go through the motions” / Event anti-patterns
o Daily Scrum becoming status report to SM or PO rather than inspection of
what’s next. [Link]+[Link]+3DZone+3
o Retrospectives that are repetitive, unengaging, or where issues are not surfaced
or addressed. [Link]+2Scrum Master #1+2
o Sprint Reviews treated merely as demos with no stakeholder feedback or
collaboration. Medium+1
5. Role Conflicts and Poor Role Understanding
o Scrum Master acting also as Product Owner, or technical lead, or manager.
Conflict of interest / mixed accountability. [Link]+1
o Scrum Master being silent / laissez faire; or conversely overly directive. Both
extremes are bad. [Link]+[Link]+2
6. Poor Communication, Missing Transparency, and Impediments Ignored
o Not sharing progress toward Sprint Goal; artifacts (like Definition of Done,
Sprint Goal) not visible or understood. DZone+1
o Impediments go unreported or unresolved; conflict avoided rather than
surfaced. [Link]+1
7. Stakeholder / Management Interference or Disruption
o Stakeholders pulling devs into meetings mid-sprint, changing scope, asking
for ad-hoc work. Interrupting flow. Scrum Master #1+1
o Management reassigning team members frequently, or pushing for 100%
utilization. [Link]+2DZone+2
Proposed Solutions: How a Scrum Master Can Help
Here are practical actions that a Scrum Master can use to help the team and organization
address and overcome those anti-patterns:
Anti-Pattern Scrum Master Actions / Interventions
• Lead by example: ensure Scrum events, roles, artifacts are
understood and used properly.
• Facilitate a session to re-examine the Scrum Guide with team
and stakeholders so that everyone is aligned on what Scrum
“Scrum-but” /
means in context.
Backsliding
• Encourage continuous inspection & adaptation: intentionally
inspect whether Scrum is being followed or being “waterfalled”.
• Use retrospectives to surface where Scrum has diverged and
agree on corrections.
• Clarify roles & responsibilities (PO, Dev Team, SM). Use RACI
or other clarity tools.
• Coach the PO, stakeholders, and organization on why self-
Micro-management / organization matters.
Role Overlap • When you see instances of micromanagement, intervene: ask
“How might this decision be made by the team?” or “What
support does the team need?” rather than giving direction.
• Encourage autonomy by giving space for team decision‐making.
• Track past velocity or throughput and use it to guide sprint
planning.
• Limit work in progress; leave buffer for unplanned tasks or
Overcommitment / impediments.
Unrealistic Sprint Goals • Make scope changes visible; ensure Sprint Goal is meaningful
and not compromised.
• If overcommitment becomes routine, inspect root causes (e.g.
estimation issues, stakeholder pressure) and coach accordingly.
• Revamp events: stand-ups with good formats, retrospective
techniques that vary and truly encourage candor.
• Ensure they are time-boxed and stay focused.
Ceremony fatigue /
• For reviews, invite stakeholders, co-create feedback
superficial events
mechanisms.
• Ensure the purpose of each event is understood, not just that the
meeting happens.
• Ensure Scrum Master is not doing things that conflict with other
roles; coach leadership/management to respect role boundaries.
• If someone is both SM & PO, discuss openly the risks and
Role Conflict
conflicts; push for separation or clarity in delegation.
• Provide training or mentoring for the SM to understand servant-
leadership vs managing.
Poor Communication & • Make artifacts visible: display backlog, Definition of Done,
Impediments Sprint Goal, etc.
• Encourage transparency: daily updates, visibility of progress,
impediments.
• Maintain and follow up on impediment list; escalate
Anti-Pattern Scrum Master Actions / Interventions
organizational impediments as needed.
• Foster psychological safety so team members feel safe raising
issues.
• Act as shield for the team: enforce boundaries around Sprint
(scope changes, meetings).
• Educate stakeholders about Scrum commitments and why
Stakeholder / interruptions are harmful.
Management Disruption • Work with Product Owner to be the primary point of contact for
features/scope so that external pressure is channeled properly.
• Negotiate with management to preserve team stability (e.g.
avoid mid-sprint reassignments).
Example: “Zombie Scrum” & How to Fix It
The term “Zombie Scrum” is sometimes used to refer to a Scrum implementation that has all
the ceremonies, artifacts, roles etc., but no real agility: no learning, no adaptation, no
empowerment of the team — just the motions. It’s a classic “going through the motions” anti-
pattern. Elements:
Retrospectives don’t lead to changes.
The team never questions or changes the way they work.
No real ownership by the development team.
Over time, momentum dies, motivation drops.
How a Scrum Master could help with Zombie Scrum:
1. Reignite purpose: Facilitate a workshop with the team & stakeholders to remind
everyone why Scrum was adopted; revisit goals, values.
2. Spice up retrospectives: Use novel formats, dig deeper with root-cause analysis, try
small experiments each Sprint to improve.
3. Empowerment: Push decisions to the team, let them fail fast safely, get feedback.
4. Measure improvements: Define what “better” means (faster throughput, fewer
defects, happier team), and track small wins.
5. Visibility: Use metrics, story maps, user feedback to show the impact of what the
team builds, so people feel connection to outcomes.
These anti-patterns are often deeply rooted in organizational culture, stakeholder
expectations, or team dynamics. The Scrum Master is not alone in fixing them, but can serve
as the main change agent, facilitator, educator, and protector of the Scrum framework. With
patience, consistency, and by leading change from within, many of these issues can be
gradually reduced or eliminated.