If you develop software professionally, chances are you use an agile process as the framework for scheduling and dividing work.  You probably don’t love it, but your level of frustration may lie anywhere on a broad spectrum from benign resignation to brain-damaging rage. 

In this episode, Mike and Erik talk about the history of Agile and what the original Agile manifesto was all about. Then, in part II, they'll cover criticisms of Agile because nobody really loves the stuff and if you've been paying attention lately, most of the chatter in our field seems to be actively bashing it and, in truth, our podcast hosts do not want to be left out of that.

References

• Manifesto for Agile Software Development
• See also “Principles behind the Agile Manifesto”
• Agile and the Long Crisis of Software (by Miriam Posner, a professor at UCLA)
• Who Builds a House Without Drawing Blueprints?
• “Study finds 268% higher failure rates for Agile software projects” (the “study”)
• “Agile Manifesto co-author blasts failure rates report, talks up 'reimagining' project”

Send us a text