One of my colleagues just sent me this article : Scrummerfall: The World's Worst Software Development Methodology - it is worth a quick read if you are interested in development processes. Most agree that there are pros and cons to Agile versus Waterfall depending on the organization. Pretty much everyone agrees that half-assing Agile is worse than not doing it at all. Hence the definition:
Scrummerfall. n. The practice of combining Scrum and Waterfall so as to ensure failure at a much faster rate than you had with Waterfall alone.
For those who are well aware of these pros and cons, this won't offer any deep insights. But it is a pretty funny take on it all, with spot on analysis of many organizations' cultural resistance to Agile.
Saturday, September 26, 2009
Subscribe to:
Post Comments (Atom)
Posts
1 comments:
*Begin Rant*
Interesting take. One of the things I have never understood about methodologies is how they become religion. This article is an example of the polarization of IT development methods. You are either purely Agile (Agilista) or purely Waterfall (Fallies). The truth that I observe over and over again is successful development tends to occur when teams decide on a process and actually practice it. Most of the time there seems to be a lot of focus on what method should be used and less focus on actually using it.
I think I am going to come up with my own methodology. "Do what works" - It's all about using the practices that work for the situation you are in and worrying about results as opposed to methods.
*End Rant*
Post a Comment