Waterfall as described in the original paper was always meant as an iterative means of developing software. Sadly, that iterative part was overlooked. You can read the original paper and you'll see it's clearly stated there.
At any event, the current business of Scrum isn't much different with the exception they've added short iterations instead of large up front design. Everything else is as rigid as it comes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Waterfall as described in the original paper was always meant as an iterative means of developing software. Sadly, that iterative part was overlooked. You can read the original paper and you'll see it's clearly stated there.
At any event, the current business of Scrum isn't much different with the exception they've added short iterations instead of large up front design. Everything else is as rigid as it comes.