The Secret History of Agile: From Japan to America

Note: Click on the video above to watch.

The Secret History of Agile: Unveiling the Roots of a Revolutionary Methodology

The Agile methodology, a transformative approach in software development, is often mistakenly attributed solely to the Agile Manifesto of 2001. However, the roots of Agile stretch much deeper into history, with influences from manufacturing and even early industrial practices. Let’s check out the lesser-known origins of Agile, and see how it has really evolved from the 19th century to today.

The Waterfall Model: A Misunderstood Beginning

The story of Agile cannot be told without mentioning the Waterfall model, traditionally seen as the “enemy” of Agile. Interestingly, Winston Royce, who formalized the Waterfall model, came up with a more iterative and feedback-driven approach in his final notes. Royce emphasized the importance of integrating feedback from testing into design and requirements, advocating for an iterative process and customer involvement.

This philosophy, remarkably similar to Agile, shows that even the origins of the Waterfall model came from principles that Agile later embraced.

Early Industrial Influences: Toyota’s Innovations

Agile’s principles can be traced back to early industrial practices, particularly those pioneered by Toyota. In 1896, Sakichi Toyoda introduced the “Stop and Notify” concept, also known as Jidoka or autonomation. His invention of an automatic loom that halted production if a needle broke was revolutionary, combining human oversight with machine efficiency. This concept of built-in quality control is a cornerstone of Lean manufacturing and, subsequently, Agile.

Post-War Innovation: The Birth of Lean and Kanban

The real transformation began in 1948 when Toyota faced severe resource constraints post-World War II. This led to the creation of the Toyota Production System, the precursor to Lean manufacturing. Lean emphasizes waste reduction and Kaizen, or continuous improvement. From Lean, Kanban emerged, a method of visualizing the work to optimize flow. This later became integral to Agile software development.

The Agile Manifesto: A Culmination of Decades of Ideas

Agile as formally recognized today was crystallized in 2001 with the Agile Manifesto, but its foundations were laid much earlier. The Manifesto was influenced by various methodologies, including Lean, Kanban, Extreme Programming, Feature Driven Development and Scrum. These frameworks collectively contributed to Agile’s emphasis on flexibility, customer collaboration, and iterative development.

Scrum: A Revolutionary Approach

Scrum, often synonymous with Agile, has its roots in a 1986 white paper titled “The New New Product Development Game” by Japanese researchers Hirotaka Takeuchi and Ikujiro Nonaka. They proposed a holistic, team-based approach to product development, likening it to a rugby team working together to move the ball down the field. This approach emphasized overlapping development phases, self-organizing teams, and continuous learning—key principles that underpin Scrum and Agile.

The Six Secrets of The New New Product Development Game

Takeuchi and Nonaka identified six characteristics of successful product development teams, which resonate strongly with Agile principles:

Built-in Instability: Assigning broad goals to capable teams, granting them autonomy and flexibility to meet that goal.
Self-organizing Teams: Teams acting like startups, from ideation to implementation, fostering autonomy, self-transcendence, and cross-functional collaboration (the Product Owner idea in Scrum today).
Overlapping Development Phases: Continuous interaction between research and development and production to ensure constant progress and iteration.
Multi-learning: Encouraging team members to pursue ongoing learning, both within and outside their areas of expertise.
Subtle Control: Implementing visual management and maintaining open workspaces to facilitate communication and collaboration.
Organizational Transfer of Learning: Converting project activities into standard practices to spread knowledge throughout the organization.

As you can see there are many similarities between Scrum as we know it today, and The New New Product Development Game introduced in 1986, even if some of the names are different.

Conclusion: The Ever-Evolving Journey of Agile

The history of Agile is rich and multifaceted, drawing from various disciplines and evolving over decades. From Royce’s iterative vision for Waterfall to Toyota’s Lean principles and the collaborative ethos of Scrum, Agile embodies a continuous pursuit of improvement and adaptability. Understanding this deep and varied history not only enriches our appreciation of Agile but also underscores its enduring relevance in today’s fast-paced, ever-changing technological landscape.

For those eager to dive deeper into Agile’s principles and practices, comprehensive courses and coaching can offer valuable insights and practical skills. Embracing Agile is not just about adopting a methodology; it’s about joining a long-standing tradition of innovation and excellence in product development.

See more PMP Articles and Tips for Passing your Exam: