Agile Software Development Method: From Waterfall to Modern Practices

Defining Agile Software Development

• 💡 Agile software development is a philosophy focused on incremental delivery, team collaboration, continual planning, and continual learning.
• 🎯 It's described as a mindset that guides the approach to building software.

The Evolution from Waterfall

• 💧 The waterfall model, originating from Herbert Bennington's work and popularized by Dr. Winston Royce, emphasized a top-to-bottom flow: requirements, analysis, design, implementation, testing, and operations.
• 🧊 Adopted by the US Department of Defense in 1985, the waterfall model led to ponderous progress, with projects taking years and significant time spent on documentation.
• 🚀 In the 1990s, rebel developers experimented with alternatives like the rational unified process, scrum, and extreme programming.

The Agile Manifesto and its Impact

• 📜 In February 2001, 17 men met in Utah to create the agile manifesto, rejecting the waterfall model in favor of producing real working code.
• 🌟 The manifesto's four key values are: individuals and interactions over process and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
• 📈 Agile methods spurred innovations like infrastructure as code, DevOps, and DevSecOps, enabling 10 new deployments a day compared to the waterfall method's roughly once every 3 years.

Addressing the Software Crisis

• 🧩 Barbara Liskoff discussed the software crisis of the 1960s-80s, where large, expensive programs often failed and had to be scrapped.
• 🧠 The problem was the immense complexity of software programs (millions of lines of code), making them impossible to fully comprehend without a way to break them into small, independently workable pieces.
• 🛠️ Early pioneers like Edger Dykstra and Tony Dave Parnes worked on programming methodology to address this by finding ways to decompose programs.