Going over the waterfall

An article today in IT-Director says that IT projects fail because the old model of specifying what you want and then acquiring – or developing – it no longer makes sense. It’s an amazing argument, really.

Apparently, the new method works better because there’s a toolkit of methods to choose from (but only once you’ve got a clear idea of the risks and problems) – but it looks like you don’t actually need to do any requirements specification at all.

I’m not sure that the new approach will help much.