Waterfall or Agile? Which Methodology Should you Choose?

My Scrum Master Certification Guide is now available on Amazon!

************

The great Agile versus Waterfall debate continues to rage on, with advocates on both sides of the debate. In this quick discussion on how to choose between Waterfall or Agile, we'll look at the pros and cons of Agile and Waterfall, show you their benefits and drawbacks, and explain why the industry trend has been away from Waterfall towards Agile software development methodologies like Scrum, Kanban, XP, Lean and Crystal.

If you want to know the difference between Waterfall and Agile, and compare their relative benefits and drawbacks, this Agile Waterfall comparison video is for you.

[nmbr]

Worked in both ... in the end I'm a big fan of the progmofo methodology - just personal preference ...
... no, sry, okay - just wanted to comment ... for the YT algorithm ... this is an excellent video and definitely deserves much much more views!

[ivanphone]

Great look at agile and waterfall software methodologies.

[scottfitzpatrick]

For SAAS projects where the software is not being developed but rather configured I think waterfall is best. When customer's buy off the shelf software as a service they expect lower cost and faster implementation times. Agile is flexible but that flexibility also costs time and I have seen a regimented waterfall milestone approach work best. I think Agile is better for ground up custom development of new solutions. No one is ever going to gather requirements 100% correct or even sometimes 50% correct on a first pass so inflexibility of waterfall makes a functioning software program on first pass nearly impossible. I think Agile is best in situations where you know there is no way to gather all the requirements in one pass and that the end customers are going to realize new things as soon as they start seeing the first parts of the software.