Oh look it's 20-20 hindsight
Poor requirements, my arse. This study says, after they finished/abandoned the project, if they had known everything they needed to know at the start it would have gone better.
Right now Mr Obvious has STFU, how do we cope with the fact we are not yet in a position to measure how bad the failure is......
It's really very simple, Change is a given, cope or fail, cope does not mean fail to take it in to account!
If the goal turns out to be undesirable, stop !
If it moves, stop shift and head towards it.
Why do IT projects fail, because some pratt somewhere chooses to stick to their old plan.
Whether that's a developer's implementation, a PMs dashboard, a BAs heartfelt dogma, or a beancounters bottom line. If you aren't close to reality, all your succesess are imaginary.
Small iterations, evaluation of unknowns, identification of risks, awareness of scope, management of expectation.
Get the basics right, cease with this chimera of 'perfect' requirements.
I've been hearing this crap for twenty plus years and I'm getting damn tired of it. It projects are not being managed they are being controlled. The difference between those two concepts is amply highlighted by the statistics.
