Fully Inverted — Now a Known Anti-Pattern
Waterfall produced software that was perfectly built to a requirements document that was wrong by the time it shipped. Agile was the correct diagnosis — the world moved while you were documenting. Shipping small and iterating was not a shortcut. It was a structural fix for a real pathology.
The Agile Manifesto of 2001 was the correct diagnosis of a real disease. Waterfall development was producing software that was perfectly built to specifications that were wrong by the time they shipped, because the world moved during the eighteen months it took to document, approve, and execute the plan. The Manifesto's four values were genuine innovations, not shortcuts.
Then Katie's Law took over.
The Inversion Timeline
2001 — the innovation: "Working software over comprehensive documentation" meant: stop writing 200-page requirements documents that no stakeholder ever reads and no developer ever refers to once the project starts. Communicate through working software instead.
2009 — the shortcut: "We're Agile" had become the industry-standard defense against any request for architecture documentation, decision records, or design rationale. The Manifesto says "there is value in the items on the right." The industry read: "the items on the right are optional."
2001 — the innovation: "Responding to change over following a plan" meant: don't death-march through a plan when the requirements have materially changed. Have the humility to adapt.
2012 — the shortcut: "We don't do roadmaps, we're Agile." Sprints with no arc. Backlogs with no architecture. Velocity measured in story points that measure activity, not progress. The team is always busy. The product never arrives.
2001 — the innovation: "Individuals and interactions over processes and tools" meant: stop letting process become a substitute for communication. Talk to each other.
2015 — the shortcut: No onboarding documentation because "just ask someone." Architecture that lives in one person's head. Decisions made in ephemeral Slack threads that no one records. The institutional knowledge walks out the door with every departure.
2001 — the innovation: "Customer collaboration over contract negotiation" meant: keep the customer close to the work so they can course-correct before you've built the wrong thing for eighteen months.
2018 — the shortcut: Scope creep as methodology. Every sprint review becomes a requirements session. Every stakeholder has veto power over every sprint. The product never stabilizes because "customer collaboration" means the requirements are always in motion.
Why It was Noble, Then Lazy
The Agile Manifesto said: "we value the items on the left more." Teams heard: "the items on the right don't matter." That is not a misquote. That is Katie's Law — humans adopt the part of an idea that reduces effort, not the part that increases it.
Teams adopted Agile because:
- No more 200-page requirements documents
- No more committing to an 18-month delivery date
- "We're Agile" became a shield against accountability for planning
- The sprint is always in progress, so you're never wrong about the deadline
The result is not iterative delivery of working software. It is perpetual incompleteness disguised as iteration. You're never done, so you're never wrong — because "we'll address that in a future sprint" is always technically true and practically meaningless.
Where It Lands In The Museum
Every exhibit in the Complex Accretion domain has an Agile story. The God Object grew one method at a time across sprints, each one reasonable, none of them worth a refactor ticket that would consume "twenty points." The runaway migration happened because infrastructure was always deprioritized in favor of user stories. The hardcoded credential shipped because the security review was a "stretch goal" for the next sprint.
The Crowdstrike global outage — 8.5 million machines downed by a single content update with no staged rollout — is Agile at the deployment layer. Move fast. The breakage was global.
The Thesis Line
The Agile Manifesto was a shortcut that was also an innovation. The innovation solved the Waterfall problem. The shortcut created the Agile problem. The context changed — teams got larger, systems got more complex, turnover happened — and the shortcut didn't adapt. That is the complete arc of every exhibit in this museum.
> Katie's Law: the lazier path was to skip the ceremony. The ceremony was protecting something you don't know you need until it's gone.