project failure

Found On The Web - Why IT Projects Really Fail

CIO New Zealand

By Hemant Kogekar

05 December, 2013 11:46


You have probably read about the Queensland Department of Health payroll project, which ended in debacle with costs estimated at $1.2 billion. In the US, the Expeditionary Combat Support System project was cancelled after the US Air Force spent $1bn on its development.

The sad fact is these failures are not isolated instances; they’re just the most visible. Based on industry norms, less than 50 per cent of IT projects finish on time and on budget.

Discussions with experienced CIOs, consultants and project managers indicate there are many reasons for the failure of IT projects. If you step back from the individual causes, common themes emerge. A few are obvious; others are not well recognised.

Fuzzy goals: Many large projects fail because what they are trying to achieve isn’t made clear enough. There is no clear problem definition or clarity about the requirements, and the full scope of the project is not understood. One executive has an objective, but as the project moves forward new people, such as other executives, risk managers, and architects are introduced, adding their ideas of what would be best. The net result is unclear goals, expanding project scope and poor project design, all of which lead to unending debates and sliding timelines.

Over-optimism: Salespeople and internal project champions both want their proposal to succeed. However, in their desire to make the ‘sell’, they often underestimate the costs and over-emphasise the benef its. While preparing business cases, there is a tendency to maximise benefits and reduce costs to achieve the right return on investment (ROI). At times, this under-estimation is not intentional, but a result of the CIO having a poor understanding of the current situation and requirements. The CIO does not consider, or budget for, the effort to move from installing a system to actually achieving the benefits (new products, customers, capability).

Over-optimism results in unrealistic schedules. There is often an unjustified faith in technology (product, vendor or internal capability). Solution complexity is not evaluated either.