- The waterfall method is very difficult to adapt to any changes in requirements as they have to be contractually negotiated with the customer (which takes time) and then software rewritten in order to incorporate them (which also takes time). It's almost impossible to guess at how long a project is going to take, how many people will be needed over time, and how much money the entire thing is going to cost (even if the requirements never change). The Agile method seems very adaptable to changing customer requirements/expectations and after each iteration there is at least some working system, instead of lots of pieces of a super broken system.
- It's popular because the customer almost never knows exactly what they want from the beginning, and as they see the product start to develop they get new ideas about how they might want to do things which need to be incorporated easily. Agile allows and encourages these things, especially continual communication with the customer.
- YES, even though large industries/corporations choose not to use it because they're run by a bunch fo 60 year old white men who don't know how to do anything different and don't want to change. My previous program building satellite ground system software just wasted an entire year and MILLIONS of dollars accomplishing nothing because they chose to stick with the waterfall method instead of trying to use agile. PS - the system is still broken, still not fully tested, and the customer is super pissed off about it.
Created
December 7, 2015 17:24
-
-
Save ToniRib/39e9e5f5b87f5bdc23a5 to your computer and use it in GitHub Desktop.
Waterfall vs. Agile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment