History of Agile

Image Attribution: Noun Project

The History of Agile: From Manufacturing to Software Revolution

The history of agile is a story of adaptation, learning from diverse industries, and ultimately transforming how we approach complex work.

Pre-Agile Roots: Learning from Manufacturing

The foundations of agile thinking emerged long before software development. In the 1940s and 1950s, Toyota revolutionised manufacturing with the Toyota Production System, emphasising waste reduction, continuous improvement (kaizen), and respect for people. Taiichi Ohno and Shigeo Shingo developed principles like just-in-time production and jidoka (automation with a human touch) that would later influence agile thinking profoundly.

In the 1980s, Eliyahu Goldratt introduced the Theory of Constraints through his book The Goal, highlighting the importance of identifying and managing bottlenecks—a concept that would resonate with agile's focus on flow and value delivery.

Early Software Experimentation (1990s)

As software projects grew increasingly complex and traditional waterfall approaches showed their limitations, practitioners began experimenting with iterative approaches:

• 1991: James Martin introduced Rapid Application Development (RAD), emphasising user involvement and iterative prototyping
• 1995: Ken Schwaber and Jeff Sutherland first presented Scrum at OOPSLA, drawing inspiration from a 1986 Harvard Business Review article by Takeuchi and Nonaka about product development
• 1996: Kent Beck began developing Extreme Programming (XP) at Chrysler, introducing practices like pair programming, test-driven development, and continuous integration
• Late 1990s: Other methods emerged, including Crystal (Alistair Cockburn), Feature-Driven Development (Jeff De Luca), and Dynamic Systems Development Method (DSDM Consortium)

The Agile Manifesto (2001)

In February 2001, seventeen software practitioners gathered at Snowbird ski resort in Utah. They came from different methodological backgrounds but shared frustration with heavyweight, documentation-driven processes. This group—including Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, and Dave Thomas—created the Agile Manifesto.

The manifesto declared four core values:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

They also articulated twelve supporting principles that emphasised customer satisfaction, welcoming change, frequent delivery, collaboration, sustainable pace, technical excellence, and simplicity.

Growth and Adoption (2001-2010)

Following the manifesto, agile gained rapid traction:

• 2001: The Agile Alliance formed to support agile practitioners
• 2002: Scrum Alliance established, promoting Scrum specifically
• Mid-2000s: Large organisations began experimenting with agile, initially in IT departments
• 2004: The first Agile conference brought together the growing community
• 2009-2010: Kanban method for knowledge work gained prominence through David Anderson's work

During this period, agile evolved from a fringe movement to mainstream practice, though adoption was often limited to development teams rather than whole organisations.

Scaling and Enterprise Adoption (2010-Present)

As agile proved successful at team level, attention turned to scaling:

• 2011: SAFe (Scaled Agile Framework) launched by Dean Leffingwell, providing structured guidance for enterprise agile
• 2013: The Scrum Alliance introduced LeSS (Large-Scale Scrum)
• 2015: Disciplined Agile Delivery (DAD) offered a toolkit approach to scaling
• Mid-2010s: Spotify's engineering culture model influenced thinking about scaling agile organically

The concept of business agility emerged—applying agile principles beyond software to entire organisations, including HR, finance, marketing, and strategy.

Contemporary Developments

Today's agile landscape includes:

• DevOps integration: Extending agile principles through deployment and operations with continuous delivery and infrastructure as code
• Agile beyond IT: Marketing, HR, and other functions adopting agile approaches
• Remote and distributed agile: The COVID-19 pandemic accelerated adaptation of agile practices for remote teams
• Product thinking: Shift from project to product mindset, with persistent teams and continuous value delivery
• Data-driven agile: Greater emphasis on metrics, flow analytics, and evidence-based improvement

Ongoing Debates and Evolution

The agile community continues to grapple with questions about:

• Whether scaled frameworks remain true to agile principles
• How to balance agility with governance and compliance requirements
• The role of certifications and formal training
• Whether "agile" has become diluted or commercialised
• How to measure and demonstrate business value from agile adoption

The history of agile demonstrates that it's not a fixed methodology but an evolving mindset—one that continues to learn, adapt, and respond to changing contexts, much as its values suggest we should.