Usually we talk about waterfall being riskier, in that there is no validation that your approach is leading to a working system, or that the working system is meeting business needs, until the very end. The big bang integration step might fail, the testing might reveal show-stopper bugs, or the customer might go "oh, that's not what I meant," etc. but by the time you're learning any of that, it's too late.
Why do you think it's preferred in risk averse industries? Is the agile-partisan view of the relative risk incorrect? Missing something?
Why do you think it's preferred in risk averse industries? Is the agile-partisan view of the relative risk incorrect? Missing something?