This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Replicated Survey of IT Software Project Failures
Sept.-Oct. 2008 (vol. 25 no. 5)
pp. 84-90
Khaled El Emam, University of Ottawa
A. Günes Koru, University of Maryland, Baltimore County
Despite various industry reports about the failure rates of software projects, there's still uncertainty about the actual figures. Researchers performed a global Web survey of IT departments in 2005 and 2007. The results suggest that the software crisis is perhaps exaggerated and that most software projects deliver. However, the overall project failure rate, including cancelled and completed but poorly performing projects, remains arguably high for an applied discipline.

1. Chaos Report Standish Group, 1994.
2. R.L. Glass, "IT Failure Rates—70 Percent or 10–15 Percent?" IEEE Software, vol. 22, no. 3, 2005, pp. 110–112.
3. R.L. Glass, "Failure Is Looking More Like Success These Days," IEEE Software, vol. 19, no. 1, 2002, pp. 103–104.
4. M. Jorgensen and K. Molokken-Ostvold, "How Large Are Software Cost Overruns? Critical Comments on the Standish Group's CHAOSReports," Information and Software Technology, vol. 48, no. 4, 2006, pp. 297–301.
5. K.R. Linberg, "Software Developer Perceptions about Software Project Failure: A Case Study," J. Systems and Software, vol. 49, nos. 2–3, 1999, pp. 177–192.
6. C.L. Iacovou and A.S. Dexter, "Surviving IT Project Cancellations," Comm. ACM, vol. 48, no. 4, 2005, pp. 83–86.
7. C. Jones, Software Assessments, Benchmarks, and Best Practices, Addison-Wesley, 2000.
8. C. Sauer and C. Cuthbertson, "The State of IT Project Management in the UK 2002–2003," Computer Weekly,15 Apr. 2003.
9. "Extreme Chaos," Standish Group, 2001.
10. C. Jones, "Project Management Tools and Software Failures and Successes," Crosstalk, July 1998, pp. 13–17.
11. D.R. Goldenson and J.D. Herbsleb, After the Appraisal: A Systematic Survey of Process Improvement, Its Benefits, and Factors That Influence Success, tech. report CMU/SEI-95-TR-009, Software Eng. Inst., Carnegie Mellon Univ., 1995.
12. K. El Emam and A. Birk, "Validating the ISO/IEC 15504 Measure of Software Requirements Analysis Process Capability," IEEE Trans. Software Eng., vol. 26, no. 6, 2000, pp. 541–566.
13. J.R. Lindner, T.H. Murphy, and G.E. Briers, "Handling Nonresponse in Social Science Research," J. Agricultural Education, vol. 42, no. 4, 2001, pp. 43–53.
14. S. Siegel and J. Castellan, Nonparametric Statistics for the Behavioral Sciences, McGraw-Hill, 1988.
15. S. Selvin, Statistical Analysis of Epidemiologic Data, Oxford Univ. Press, 1996.
1. "Latest Standish Group CHAOSReport Shows Project Success Rates Have Improved by 50%," Standish Group, 2003.
2. 2004 Third Quarter Research Report, Standish Group, 2004.
3. Extreme CHAOS, Standish Group, 2001.
4. CHAOSReport, Standish Group, 1994.
5. CHAOS: A Recipe for Success, Standish Group, 1999.
6. J. Johnson, "Turning CHAOSinto Success," Softwaremag.com, Dec. 1999, www.softwaremag.com/L.cfm?doc=archive/1999dec Success.html.
7. D. Rubinstein, "Standish Group Report: There's Less Development CHAOSToday," Software Development Times, 2007.
8. C. Jones, "Project Management Tools and Software Failures and Successes," Crosstalk, July 1998, pp. 13–17.
9. C. Sauer and C. Cuthbertson, "The State of IT Project Management in the UK 2002–2003," Computer Weekly,15 Apr. 2003.
10. R. Sonnekus and L. Labuschagne, "Establishing the Relationship between IT Project Management Maturity and IT Project Success in a South African Context," Proc. 2004 PMSA Global Knowledge Conf., Project Management South Africa, 2004, pp. 183–192.
11. M. Schonlau, R.D. Fricker, and M.N. Elliott, Conducting Research Surveys via Email and the Web, Rand, 2002.

Index Terms:
software engineering management, productivity, programming teams, project control and modeling, review and evaluation, risk management, schedule and organizational issues
Citation:
Khaled El Emam, A. Günes Koru, "A Replicated Survey of IT Software Project Failures," IEEE Software, vol. 25, no. 5, pp. 84-90, Sept.-Oct. 2008, doi:10.1109/MS.2008.107
Usage of this product signifies your acceptance of the Terms of Use.