Agile Software Development – What’s The Real Deal? Tathagat Varma Head of Strategic Programs and Business Operations Yahoo! India R&D
Pace of Innovation and Adoption …getting faster…http://www.phibetaiota.net/2011/12/john-robb-digital-empowerment-of-resilient-communities/
Waterfall Software Development Limitations and Assumptions 1. Wrong analogy: Software development ≠ Production 2. Customers know EVERYTHING upfront and that requirement won’t change 3. Legacy from the past: implicitly assumes CPU time is costly, so focuses on doing everything upfront to minimize ‘machine time’ for trial and error 4. “Wicked Problem”: Designers and developers know how exactly how to build 5. Very long feedback cycles not suitable for today’s pace of innovationPicture from http://damonpoole.blogspot.in/2009/07/traditional-development-game-of.html
Feedback Loops in Traditional Techniques vs. Agile Techniques
Agile Development Value Propositionhttp://www.versionone.com/Agile101/Agile_Benefits.asp
Does Agile work?http://www.bigvisible.com/2009/12/taking-agile-beyond-faster/http://www.testingthefuture.net/page/2/
Conclusion• Pace of Innovation, Adoption and Obsolescence is …accelerating• We don’t always know enough about all the problems to design big-upfront solutions, nor have enough resources to keep them locked-up for a long ROI cycle• Adapting to early feedback can help make in-flight course corrections faster, cheaper and more gracefully• Agile frameworks and methods allow ‘inspect and adapt’ to deliver smaller chunks of functionality faster, thereby improving TTM• Agile methods facilitate early creation of business value…but don’t guarantee it!
Afterthoughts…“In the struggle of survival, thefittest win out at the expense oftheir rivals because theysucceed in adapting themselvesbest to their environment.” – Charles Darwin