Agile’s Midlife Crisis: Returning to First Principles

What did Agile promise, and how did that promise get lost?

Agile promised that individuals and interactions would take precedence over processes and tools, but the Agile industry inverted this promise by building an $18 billion certification and consulting ecosystem around processes and tools.

The Agile Manifesto was written by 17 people in a ski lodge in Snowbird, Utah, in February 2001. The document they produced contained 68 words of values and 12 principles. It was deliberately minimal. Kent Beck, one of the signatories, later reflected that the manifesto was intentionally a set of values, not a methodology, because methodologies calcify while values adapt.

Twenty-three years later, the Scrum Guide alone is 14 pages. The SAFe framework contains 42 named practices, 10 core competencies, and 4 configurations. A Certified Scrum Master credential requires a 2-day course and a $500 fee. A SAFe Program Consultant credential requires a 4-day course and a $2,695 fee. The industry that grew around Agile is worth an estimated $18 billion annually. The manifesto’s first value, “individuals and interactions over processes and tools,” has been buried under exactly the processes and tools it warned against.

Where did the calcification happen?

Calcification happened at 3 points: when Scrum ceremonies became mandatory rituals, when story points became management metrics, and when “Agile transformation” became a consulting product rather than a team practice.

I observed the calcification pattern at 10 organizations. The sequence was consistent. A team adopted Scrum and found that the ceremonies (standups, retrospectives, sprint reviews) improved communication. Management noticed the improvement and mandated the ceremonies across all teams. Teams that did not benefit from the specific ceremony (a 3-person team that sat together and did not need a standup, a research team whose work did not fit sprint cadences) were required to adopt them anyway. The ceremony became a compliance requirement rather than a communication tool.

Story points followed the same trajectory. They were designed as a relative estimation tool for teams to plan their own capacity. Management discovered they could be aggregated, compared across teams, and trended over time. Story points became a productivity metric. Teams responded rationally: they inflated their estimates. A task that was a “3” became a “5.” Velocity charts went up. Actual output did not change. The metric was gamed because it was used for a purpose it was never designed to serve.

The most expensive calcification was “Agile transformation,” the practice of hiring consultants to install Agile across an entire organization simultaneously. I participated in 2 such transformations and observed 4 others. The average cost was $1.8 million. The average duration was 12-18 months. In 5 of 6 cases, the organization was using the same processes 24 months after the transformation ended as it had used before, with Agile terminology layered on top. Standups were held, but decisions were still made in separate management meetings. Retrospectives were conducted, but action items were still ignored. Sprint reviews happened, but stakeholder feedback still arrived after features were built.

What does returning to first principles look like in practice?

Returning to first principles means stripping away every ceremony, role, and artifact that does not directly serve one of the 4 manifesto values, and keeping only what survives that test.

At 2 organizations where I led this stripping exercise, the results were revealing. At the first (a 60-person product team), we eliminated the Scrum Master role, reduced ceremonies from 5 to 2 (a weekly planning session and a biweekly retrospective), stopped using story points entirely, and replaced sprint commitments with a continuous flow model. Delivery throughput increased 18% in the first quarter. The team reported higher satisfaction because they spent less time on process overhead and more time on work.

At the second (a 140-person engineering organization), we kept more structure but changed its purpose. Standups became optional and asynchronous (a Slack bot asked 3 questions; people who had updates posted them). Retrospectives were preserved but restructured: action items from retrospectives were the only items in every third sprint’s backlog. Sprint reviews were replaced with continuous stakeholder access to a staging environment. Story points were eliminated in favor of cycle time as the sole planning metric.

Both organizations stopped calling themselves “Agile.” They did not need the label. They practiced the values.

Is the post-Agile movement a rejection or a return?

The post-Agile movement is a return to the original values, not a rejection of them, much like the Reformation was a return to scriptural Christianity rather than a rejection of Christianity itself.

Shape Up from Basecamp. Team Topologies from Matthew Skelton and Manuel Pais. Continuous Discovery Habits from Teresa Torres. These post-Agile frameworks share a common ancestry: they take the manifesto’s values seriously and discard the institutional apparatus that accumulated around them. Shape Up keeps “responding to change” but eliminates the sprint cycle. Team Topologies keeps “individuals and interactions” but replaces Scrum roles with cognitive load analysis. Continuous Discovery keeps “customer collaboration” but replaces sprint reviews with weekly customer interviews.

The parallel to philosophical movements is instructive. Stoicism, as practiced by Marcus Aurelius, was a living philosophy adapted to daily decisions. Stoicism, as codified by later commentators, became a rigid doctrine. The revival of Stoicism in the 21st century is not a new philosophy. It is a return to the practice, stripped of the commentary. Agile’s trajectory follows the same arc: living practice, institutional codification, and now a return to the living practice.

The manifesto’s 68 words are still correct. Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. The values are clear. The industry obscured them. The post-Agile movement is clearing the obscurant growth to let the roots breathe again.

Dave Thomas, another manifesto signatory, wrote in 2014 that “the word Agile has been subverted to the point where it is effectively meaningless.” He proposed using “agility” as a quality rather than “Agile” as a noun. This distinction matters. Agility is a property of how a team works. Agile is a product that consultants sell. The manifesto described agility. The industry built Agile. Returning to first principles means choosing the adjective over the noun.