Abstract
We have known for decades that IT projects often fail. The usual explanation is that the cause is poor project management, poor cost estimation, poor requirements, etc. But how can we prevent these causes? To answer this question, it is not sufficient to know that there was poor project management, etc. Would it suffice to educate better project managers? And what would we have to teach them that they don't learn today? We have to know what actually took place in the projects, identify the root causes, and find ways to prevent them (cures). This is similar to accident investigations in aviation. This paper reports the results of five accident investigations of large government IT projects in Denmark. We identified 37 root causes and 22 potential cures. Surprisingly, only one of the causes is programming-related. Each project suffered from around 15 of the causes. Twenty-seven of the causes are not reported in the research literature on IT project failures (e.g. surprises with system integration and wrong estimate of human performance). Half of the cures are familiar to developers, but were ignored in the specific project (example: usability test). The rest are unfamiliar (e.g. problem-oriented requirements and monitoring remaining work).
Highlights
We have known for decades that IT projects often fail
The usual explanation is that it is caused by poor project management, poor cost estimation, poor requirements, etc. [2], [13], [22] But how can we prevent these causes? To answer this question, it is not sufficient to know that there was poor project management, etc
Accident investigations in IT projects are rarely published, and as a result, we know little about the root causes [2]
Summary
We have known for decades that IT projects often fail. The usual explanation is that it is caused by poor project management, poor cost estimation, poor requirements, etc. [2], [13], [22] But how can we prevent these causes? To answer this question, it is not sufficient to know that there was poor project management, etc. We have to know what took place in the projects, identify the root causes and find ways to prevent them (cures). When the board knows the causes, they can come up with ways to prevent similar accidents in future flights. Finding out what happened and why, is usually difficult It may require technical investigations, interviews, flight recorder data, medical records of the pilot, weather data. In the IT world, we will define an accident as a project with significant damage, e.g. large cost or schedule overrun, failing business goals, low usability, etc. Accident investigations in IT projects are rarely published, and as a result, we know little about the root causes [2]. This paper reports the results of five accident investigations of large government IT projects in Denmark. IT developers in industry say that they see the same causes, but industry practices a few more cures
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
