Why tech projects get canned

This article was originally published in VSJ, which is now part of Developer Fusion.
Almost a half (43%) of organisations have ‘killed’ an IT project before it was fully implemented, according to a survey at the North America Computer Audit, Control and Security conference sponsored by ISACA.

The top two reasons cited by the 386 respondents for ending projects prematurely were that business needs had changed (30%) and the project did not deliver as promised (23%). Other reasons were that the project was no longer a priority (14%), exceeded its budget (13%) and no longer supported the business strategy (7%). To help organisations reduce the costs resulting from inefficient investments, ISACA’s research affiliate, the IT Governance Institute (ITGI), has developed Val IT, a collection of proven management practices and techniques for evaluating and managing investment in business change and innovation that is freely available for download from ISACA’s web site.

You might also like...



Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Engineers are all basically high-functioning autistics who have no idea how normal people do stuff.” - Cory Doctorow