Agile

In February 2001, seventeen software developers gathered at the Lodge at Snowbird ski resort in Utah. They represented competing methodologies — Extreme Programming, Scrum, Crystal, Adaptive Software Development, DSDP — and had little in common besides a shared conviction that the dominant approach to building software was fundamentally broken. Three days of argument produced a single page: the Agile Manifesto. Four values. Twelve principles. No methodology prescribed. 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 signatories included Kent Beck (XP), Ken Schwaber and Jeff Sutherland (Scrum), Alistair Cockburn (Crystal), and Martin Fowler — names that would define software development practice for the next two decades.

The manifesto was a direct response to waterfall — the sequential, phase-gated development model that had dominated software engineering since Winston Royce's 1970 paper (which, ironically, described the approach only to argue against it). Waterfall demanded that you specify every requirement before writing a single line of code, design the complete architecture before building anything, and test only after the entire system was assembled. The Department of Defense codified waterfall into MIL-STD-2167 in 1985, making it the standard for government software contracts. The results were catastrophic. The Standish Group's 1994 CHAOS Report found that 31% of software projects were cancelled before completion and 53% exceeded their budget by an average of 189%. Only 16% finished on time and on budget. Waterfall projects failed because they assumed requirements could be fixed at the start of a multi-year process — an assumption that was false for virtually every software project of meaningful complexity.

Agile replaced the sequential pipeline with iterative cycles. Instead of planning for two years and building for two more, an Agile team delivers working software in sprints of one to four weeks. Each sprint produces a functional increment that can be tested by users, evaluated against real-world conditions, and adjusted in the next cycle. Scrum — the most widely adopted Agile framework — structures these cycles around sprint planning, daily standups, sprint reviews, and retrospectives. Extreme Programming adds technical practices: pair programming, test-driven development, continuous integration. Kanban (adapted from Toyota's production system) focuses on flow, limiting work in progress to prevent bottleneck buildup. The specific rituals differ. The shared principle is that short feedback loops produce better outcomes than long planning horizons — because the probability that your initial assumptions are correct declines with the complexity of the system you're building.

But Agile has metastasized far beyond its origins. By 2024, the methodology — or at least the vocabulary — had colonized marketing ("Agile marketing sprints"), human resources ("Agile talent management"), strategy consulting ("Agile transformation"), and military planning. The Scaled Agile Framework (SAFe), introduced in 2011, grafted Agile terminology onto enterprise bureaucracy, producing a 40-page process diagram that the original manifesto signatories would barely recognise. The irony is exquisite: a philosophy born to destroy process overhead has been industrialised into one of the largest process-consulting revenue streams in business. The manifesto's first value — "individuals and interactions over processes and tools" — is now routinely violated by the very frameworks that claim to implement it.