I’ll make a clear statement. I don’t like the Agile vs Waterfall or the Waterfall vs Agile arguments where there is an obvious bias toward one approach, with the exclusion of the other. Agile and waterfall methodologies both have pros and cons.
I believe that either methodology can be applied within the suitable context. And as a Business Analyst, my job is to assess and recommend viable solutions according business needs. Therefore the type of methodology to be used can also be determined according to what is best for the organisation.
This week’s link roundup brings you articles comparing the Agile and Waterfall software development methodologies. They examine the pros and cons of using each, and introduces the concept of the agile-waterfall hybrid methodology (also called wet agile or w-agile).
- Agile & Waterfall Methodologies – A Side-By-Side Comparison. This is a fair and informative comparison of the agile and waterfall software development methodologies. It includes the definition, advantages and disadvantages, and advice on when to use them respectively. I like this article because it states that both the agile and waterfall methodologies have their strengths and weaknesses.
Waterfall vs. Agile: Which is the Right Development Methodology for Your Project? Again, this is a fair and informative comparison of agile and waterfall methodologies. I like this article because it states that both methodologies are usable, mature methodologies.
Agile-Waterfall Hybrid: Smart Approach or Terrible Solution? This is an interesting article that explores an Agile-Waterfall hybrid approach. This ‘compromise’ also it has its advantages and disadvantages.
So what’s your opinion? Weigh in on the conversation by leaving a comment below.