3 ms·
It's not a misconception, it's the way it is, including in the paper that has been quoted in this thread. For instance, "Step 2: document the design" advocates
by mytailorisrich 5y ago
It's not a misconception, it's the way it is, including in the paper that has been quoted in this thread.
For instance, "Step 2: document the design" advocates extensive documentation upfront.
Of course there is feedback but the loop is very large and slow, and the paper emphasises that feedback ought "to be confined to sucessive steps", which, in addition is problematic when requirements change mid-way.
Agile is trying to solve a real issue with the waterfall model in general and, especially, when requirements are fluid.