4 ms·
The problem is that waterfall is a myth propagated by the Agile evangelists. Development waterfalls were not frozen and rigid as claimed by Agile advocates, but
by oxfordmale 5y ago
The problem is that waterfall is a myth propagated by the Agile evangelists. Development waterfalls were not frozen and rigid as claimed by Agile advocates, but we're in fact fluid allowing certain steps to start before others were finished.
- tonyedgecombe 5y agoEverywhere I've seen it management had the expectation that the requirements were frozen, that the project would be on time and costs were fixed.
- oxfordmale 5y agoThis gives a good historical overview: http://www.bawiki.com/wiki/Waterfall.html http://www.bawiki.com/wiki/Waterfall.html Wikipedia gives a shorter version: In fact Royce, known for his 1970 paper from which the Waterfall model for software development was mistakenly drawn, demonstrated that while the development of large software systems required a more thorough approach, there was inherent risk in a single-pass sequential approach. He proposed an iterative approach and advocated that projects should pass through this at least twice.