Overview

• What you’ll learn: The most common anti-patterns that undermine Agile adoption, how to recognize them, and how to address them.
• Prerequisites: Lesson 7 — Agile Mindset
• Estimated reading time: 14 minutes

Introduction

Every team thinks they’re “doing Agile.” Many teams are actually doing something that looks like Agile from the outside but completely misses the point. These patterns are so common they have names — and recognizing them is the first step to fixing them.

ScrumBut

“We do Scrum, but…” followed by an exception that defeats the purpose:

• “We do Scrum, but we skip retrospectives because we’re too busy.” — Then you’ve removed the primary mechanism for improvement.
• “We do Scrum, but our Sprints are 3 months long.” — That’s not a Sprint, that’s a quarter.
• “We do Scrum, but we don’t have a Product Owner.” — Then who decides what to build?
• “We do Scrum, but the Sprint scope changes every day.” — Then you don’t have a Sprint.

ScrumBut usually indicates that the team has adopted the form of Scrum but not the substance. The “but” reveals which value or principle they’re unwilling to embrace.

Cargo Cult Agile

Teams perform Agile rituals without understanding why. They have standups (but nobody listens). They have boards (but nobody updates them). They have retrospectives (but nothing ever changes). The ceremonies are present; the results are absent.

Water-Scrum-Fall

Requirements are defined upfront in a Waterfall manner. Development uses Sprints. Deployment happens months later. The team has Agile development sandwiched between Waterfall planning and Waterfall deployment — the worst of both worlds.

The Feature Factory

The team churns out features without measuring whether they deliver value. Velocity becomes the sole metric. Nobody asks “did anyone actually use this feature?” or “did it improve customer satisfaction?” Output is celebrated while outcomes are ignored.

Dark Scrum

Management uses Scrum events to micromanage rather than empower. Daily Scrum becomes surveillance. Sprint velocity becomes a productivity target. The framework meant to liberate developers becomes their cage.

Other Anti-Patterns

• Estimation as commitment: Story points become deadlines instead of planning tools.
• Eternal Sprint Zero: The team spends months “preparing” and never delivers an Increment.
• No Definition of Done: “Done” means whatever is convenient at the moment.
• Mini-Waterfall Sprints: Each Sprint has its own requirements phase, design phase, coding phase, and testing phase — just shorter.
• Hero culture: One person saves every Sprint with overtime heroics, masking systemic problems.

How to Address Anti-Patterns

1. Name it. Anti-patterns thrive in darkness. Bring them to the Retrospective.
2. Understand the root cause. ScrumBut usually indicates fear, organizational constraint, or misunderstanding.
3. Experiment. Don’t try to fix everything at once. Pick one anti-pattern, try a countermeasure for one Sprint, inspect the result.
4. Get coaching. An experienced Scrum Master or Agile Coach can see patterns the team is blind to.

Key Takeaways

• Anti-patterns are common, recognizable, and fixable — but only if you’re willing to look honestly.
• ScrumBut reveals which values a team is unwilling to embrace.
• Cargo Cult Agile has the rituals without the results.
• The Retrospective is your primary tool for identifying and addressing anti-patterns.
• Fix one thing at a time. Empiricism applies to process improvement too.

What’s Next

Congratulations — you’ve completed Module 1: Agile Foundations! You now have a solid understanding of Agile philosophy, frameworks, and mindset. In Module 2, you will dive into the three accountabilities in Scrum: the Product Owner, the Scrum Master, and the Developers.