Introduction
The concept of agility in software development has evolved significantly over the years, leading to the emergence of distinct waves. Each wave has brought its unique contributions and challenges, shaping the way we approach software development today.
Let's explore those waves.
Wave 1: Introduction of The Agile Manifesto (2001)
The first wave of agility was marked by the publication of the Agile Manifesto in 2001. This seminal document outlined a set of values and principles that would form the foundation of agile methodologies.
The Agile Manifesto emphasized:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
In other words, this moved the focus of software development towards flexibility, collaboration, and customer satisfaction.
Wave 2: Agile Project Management and the Introduction of the Agile Frameworks (2003-2010)
Building upon the Agile Manifesto, the second wave saw the emergence of specific agile frameworks, such as Scrum and Kanban (specifically with it being applied software development). These frameworks provided structured methodologies for implementing agile principles in software development projects.
-
Scrum:
- A framework that emphasizes iterative development, time-boxes, and self-organizing teams.
- Origins date back to an article in the Harvard Business Review in 1986.
- Introduced to teams in 1993.
- Started gaining traction in 2003.
-
Kanban:
- A visual system for managing work that focuses on continuous flow and limiting work in progress.
- Origins date back to the 1940s by Taiichi Ohno, an industrial engineer at Toyota.
- Introduced to software development in 2003 by the publication of "Lean Software Development: An Agile Toolkit" by Mary and Tom Poppendieck.
- Truly took off in the software industry in 2009.
Wave 3: Business Agility and Scaling (2010-2020)
As agile methodologies gained popularity, organizations faced the challenge of scaling agile practices to larger teams and projects. The third wave of agility focused on developing frameworks and techniques for scaling agile across the enterprise.
Some examples of scaled agile frameworks that have been adopted:
-
SAFe (Scaled Agile Framework):
- Introduced in 2011, a comprehensive framework that provides a structured approach to scaling Agile across large enterprises.
- Centralized, structured.
- Best suited for large organizations with complex systems and a need for standardization.
-
Spotify Model:
- Introduced in 2012, a decentralized approach inspired by the Spotify organization.
- De-centralized, flexible, incorporates other Agile practices.
- Best suited for organizations that value autonomy and prefer a more organic approach to scaling.
-
DA (Disciplined Agile):
- Introduced in 2015, a hybrid framework that combines elements of Scrum, Kanban, and other Agile practices.
- De-centralized, flexible, incorporates other Agile practices.
- Best suited for organizations that seek a flexible and adaptable approach to scaling Agile.
-
S@S (Scrum At Scale):
- Introduced in 2015, a framework for scaling Scrum to large organizations, emphasizing the use of Scrum Masters, Product Owners, and Development Teams.
- Centralized, structured, focus on Scrum.
- Best suited for organizations that want to maintain a strong focus on Scrum principles while scaling.
-
LeSS (Large-Scale Scrum):
- Introduced in 2015, a framework for scaling Scrum to large organizations, emphasizing simplicity and self-organization.
- Lightweight.
- Best suited for organizations that prefer a minimalist and lightweight approach to scaling.
-
Nexus Model:
- Introduced in 2015, a framework for scaling Scrum to multi-team development.
- Focus on Scrum.
- Best suited for organizations with multiple Scrum teams working on a single product.
Wave 4: DevOps, Continuous Delivery, and Psychological Safety (2015-present)
The fourth wave of agility shifted the focus from software development to the entire software delivery lifecycle. DevOps, a cultural movement that promotes collaboration between development and operations teams, emerged as a key component of this wave.
- DevOps: A set of practices that aim to shorten the development lifecycle and improve the reliability of software releases.
- Continuous Delivery: A set of practices that enable organizations to deliver software changes to production frequently and reliably.
It's worth noting that this fourth wave also involved a focus on psychological safety and creating safe spaces for teams to work in.
- Psychological Safety: Refers to an environment where team members feel safe to take risks, express their ideas, and make mistakes without fear of retribution.
- Safe Spaces: Intentional efforts from leaders and team members to encourage open communication, active listening, and acknowledging each team member's contributions.
Summary
The four waves of agility have significantly impacted the way software development is done today. Each wave has brought its unique contributions, from the foundational principles of the Agile Manifesto to the scaling frameworks and DevOps practices of the present.
As technology continues to evolve, it is likely that new waves of agility will emerge, further shaping the future of software development.
Prefer to consume this information from a video?
This blog is available on my 
channel as well!
A direct link to this blog's video can be found here.