4 ms·
Waterfall sucks. I say this as a guy with experience in the kind of systems you mention (though not the F-22). Waterfall itself leaves little room for early fee
by Jtsummers 9y ago
Waterfall sucks. I say this as a guy with experience in the kind of systems you mention (though not the F-22). Waterfall itself leaves little room for early feedback which means schedules are always delayed and problems are pushed to the next block cycle (a 12-24 month activity). Integration of changes is delayed until the last minute (versus the lean software concept of the last responsible moment). Testing turns into a massive clusterfuck at PFQT and FQT which is the last stage of a waterfall cycle.
Waterfall assumes you can know too many things at the start and have everything go right. It fails when it encounters the real world but is still pushed by program offices across the DOD despite extreme cost and schedule overruns and quality issues.
I’m out now and on mobile. But I can write in more detail later if you want about the problems of the pervasive waterfall method in DOD projects. Even the DOD systems acquisition documents have endorsed iterative/incremental (a slow motion agile/lean when you dig into it) development models since 1985 but still Waterfall lives on.