Agile Theater and Zombie Scrum

Time to say the quiet part out loud. A lot of what's called "agile" in the real world doesn't work. The standups happen, the sprints have numbers, the board is beautiful — and nothing improves, for years. The critics who point this out are not haters. They're often right. Most courses won't tell you that, because most courses are selling you the ritual. We're not — so let's study the disease properly, the way doctors do: so you can recognize it, name it, and not catch it.

By the end of this video, you'll be able to tell healthy agile from two failure modes — zombie scrum and agile theater — recognize five named anti-patterns in the wild, and carry the single diagnostic question that cuts through all of it in ten seconds.

Two related conditions, one distinction worth keeping.

Zombie scrum — the name comes from a book-length diagnosis by Christiaan Verwijs, Johannes Schartau, and Barry Overeem — is scrum with all the ceremonies and none of the pulse. The team meets, plans, boards, reviews… and if you ask what makes their product valuable, nobody can answer. Nothing ships with urgency. Nothing about how they work has changed in a year. The rituals walk; the purpose is dead. Zombie scrum isn't performed for anyone — it's what remains when the why leaks out and the calendar keeps going.

Agile theater is performative: the ceremonies run for an audience. The standup exists so the manager can collect status. Velocity is published so leadership sees a rising line. The retro happens so the transformation dashboard shows a green tick. Theater has spectators; zombie has habits. Both have the same missing organ: no connection between the activity and any outcome.

Five named anti-patterns, so you can spot them on sight.

Feedback Theater. Retros held, minutes taken, nothing ever changes. You built the vaccine last lesson — the owned, reviewed experiment — so you already know exactly what's missing.

The Backlog Black Hole. A thousand items, some three years old, none ever deleted. Remember: a backlog is ordered and living — a list where nothing dies is not a plan, it's a landfill with a search bar. The power of the honest Won't, from Module 3, is precisely what's been refused here.

Chain Sprinting. Sprint ends Friday, next begins Monday, forever, no slack, retros compressed to ten minutes then skipped. Sustainable pace — a principle, you'll recall, not a perk — deleted in practice. Exhausted teams don't inspect and adapt; they survive.

Frankenagile. A mashup stitched from fragments — sprints from Scrum, no retros though, WIP limits nobody enforces, roles renamed but behavior unchanged — assembled by copying visible parts without understanding what any part is for. Blending frameworks thoughtfully is fine, you know that from Scrumban. Frankenagile is different: it's cargo, not craft.

Done-faking. "Done" that isn't — untested, unshipped, unusable, but the ticket moved and the burndown looks great. The Definition of Done from Module 2 exists exactly to make this lie impossible to tell politely.

Here's the ten-second test, and it's two questions welded together. Ask any team: "What outcome improved recently — and what did you change about how you work?"

A healthy team answers both in a sentence: wait times dropped; we started async standups last month. A theater or zombie team goes quiet, or answers with outputs — "we completed forty tickets" — or with ceremonies — "we hold retros every sprint." Silence on both halves is the diagnosis. Notice what the question really is: outcomes from Module 3, improvement from this module. You didn't just learn a test. You are the test.

The cure is never "do the ceremonies harder." It's always a return to purpose: reconnect work to value — Module 3. Rebuild safety so truth can be spoken — Module 2. Restore real inspection and adaptation — the empirical loop everything rests on. The ideas you've already learned aren't just the healthy version; they are, point for point, the treatment.

And your size in this, as someone new: you will very likely meet these patterns, possibly in your first job. You are not required to fix your organization in week one — that's not your job and not this course's promise. Your job is quieter and more valuable: keep your judgment. Recognize the pattern, name it privately, protect your own corner of the work, and know what good looks like so the theater never gets to redefine it for you.

You might conclude from all this that agile is broken and the critics have won. That's understandable — you've just toured the failure museum. Actually, notice what every exhibit had in common: the practices survived while the purpose died. That's not evidence against the ideas; it's evidence that rituals without understanding don't work — which is, in fact, this course's founding argument. You're being taught judgment first, ritual second, for exactly this reason.

Three things to keep. One: zombie scrum is habit without pulse; agile theater is performance for an audience — same missing organ, no outcome connection. Two: five rogues — Feedback Theater, Backlog Black Hole, Chain Sprinting, Frankenagile, Done-faking. Three: the ten-second test — what outcome improved, and what did you change about how you work — and the cure is always a return to purpose, never louder ceremonies.

You can spot fake agility. Time to see the real thing at full scale — beyond software, with an unexpected new teammate, and finally, in your own hands. Module 5.