Creator Of Agile Manifesto Doesn't Like Agile???

Agile’s original promise—short feedback loops, frequent releases, and teams shaping how they work—has been steadily undermined by management’s demand for control, reporting, and “numbers,” turning lightweight iteration into heavy process and framework theater. John Kern, a co-author of the Agile Manifesto, is cited for calling this drift the “agile industrial complex,” a world where agile becomes a label wrapped around dashboards, metrics, and bureaucracy rather than a method for delivering value.

The transcript traces how this transformation happens in practice. Agile’s per-team autonomy can create organizational anxiety, so companies respond by standardizing process “company-wide,” effectively centralizing decisions that were meant to stay local. From there, familiar waterfall-era habits reappear in new forms: planning poker replaces long planning, “in production” replaces formal testing, and release cycles become tightly managed—sometimes alongside buzzwords and tooling such as CI/CD, TDD, story points, and velocity. The result, critics say, is a system that can reward speed and predictability over quality, encouraging broken software “slen[__]ification” and metric-driven behavior.

A second, deeper critique targets who gets hired into the process machine. Many roles in large tech organizations are not hands-on engineering; managers and program leaders often lack direct coding experience, so they seek numeric proxies for progress—percent completion, velocity, and other indicators—because they can’t otherwise judge whether work is truly moving forward. Meanwhile, engineering talent and tribal knowledge become harder to retain as tenure drops, and the loss of experienced people forces more documentation, coordination, and process overhead. The transcript argues that startups often “do agile in purity” early because teams are small and technical, but the approach degrades as organizations scale and non-technical stakeholders gain influence.

The discussion also challenges research that claims agile is harmful. A cited study is criticized for weak methodology: a short data collection window (May 3–May 7), a relatively small sample (600 engineers), and reliance on perception-based survey responses rather than objective outcomes like feature completion, production bugs, or real usage metrics over time. The critique is that “agile” gets blamed for organizational failures—especially when requirements are unclear or when management manipulates metrics—rather than being evaluated on measurable delivery results.

Finally, Kern’s proposed remedy is to “reimagine agile remaining agile” by seeking “agile exemplars”—teams where agile still works—and interviewing them to identify what “good” looks like. Skeptics in the transcript warn that this can trigger a “no true Scotsman” problem and that true agile may be rare at scale, since teams that can keep autonomy and quality intact often face structural pressures in large enterprises. The conversation ends on a blunt tension: low-process freedom may work when stakes are smaller, but leaders at massive companies may feel forced to add rigor—sometimes at the cost of the very agility they’re trying to preserve.