Avoiding IT project failure
Last week we published an article by Andrea Maritan on the importance of fixing your processes before implementing new software. His opening sentence – i.e. “New software implementations are a risky task” – describes an all too common scenario.
We’ve all heard of major IT projects failing … or being cancelled, bungled, delayed, or running over budget. Just this week the AFR reported that the West Australian government is junking a payroll system on which it has already spent $400 million. And last year, the Queensland government ran into major issues with a payroll implementation. But they’re not alone in suffering these unfortunate outcomes.
According to ZDNet, a recent survey revealed that 75% of people closely involved in IT projects believe they are always or usually “doomed from the start”. This is a staggering result and one that business owners and software vendors alike should be very concerned about.
One of the reasons highlighted by ZDNet for IT failures is that “almost 50 percent of projects do not have defined end criteria”. Or, as author Lawrence J Peter once put it: “if you don’t know where you’re going, you’ll probably end up somewhere else”.
So if you’re about to embark on the selection and implementation of a new software system for your organization, make sure you start with a shared understanding of what you are trying to achieve and why, and invest plenty of resources in ironing out key organizational and process issues before you start!
