It seems like every time we post on the subject of Agile dev & testing, two things happen:
- We get a lot of comments from the pro-agile crowd
- We get a lot of comments from the anti-agile crowd
So far the conversation has been passionate yet professional, which is why I’m excited to let our readers debate the pros and cons of Agile in a dedicated open forum, the first of its kind on the uTest blog.
To get the conversation started, I wanted to share some snippets from a few recent agile news stories. Take a look:
The Pros of Agile
“Agile is not a fad. It’s a mega trend that is revolutionizing software development worldwide. It is being adopted for one simple reason: It works better than anything we have done before. Software/business outcomes are better, and that goodness spreads from users to customers to management to development teams. I’ve been at this for 40 years now, and have seen three separate waves of development practices overtake the industry, with agile being the latest. I wouldn’t even hazard a guess as to what happens after agile, but we have to go through agile to find it.” – Dean Leffingwell (link)
“There’s often an assumption that attending a class or seminar and implementing some of the points learned leads to “Agile.” (The same assumption dogs SOA projects as well, by the way.) Every organization is different, and is constantly evolving. Continuous learning and improvement is at the core of Agile. Agile isn’t a prescribed process or set of practices; it’s a philosophy that can be supported by a practice and no two agile approaches are the same.” – Joe McKendrick (link)
The Cons of Agile
“The problem with agile is that it is most of the time used as a methodology smoke-screen for having no methodology. It works fine if you have a complete specification first and a have a design for the system worked out first. Then you can deliver frequent iterations to make sure that what is in the specification and what has been designed is actually what the customer wants (it frequently isn’t). The notion that you can use “agile” development methodology to avoid a thorough requirements analysis, detailed specification gathering, and working out a reasonably detailed design is laughable.” – Anonymous commenter (link)
“Agile is just a euphemism for shipping alpha and beta quality code and letting the user test it. But hey, if its got its own buzzword is sounds so much more professional.” – Anonymous commenter (link)
Let the debate begin! Be sure to weigh in with your thoughts in the comments section.