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)
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)
| Original language | English |
|---|---|
| Article number | //doi.org/10.1109/ACCESS.2020.2986545 |
| Journal | IEEE Access |
| Volume | 8 |
| Number of pages | 10 |
| ISSN | 2169-3536 |
| DOIs | |
| Publication status | Published - Apr 2020 |