Perceived causes of software project failures - An analysis of their relationships

Information and Software Technology

Volumn 56, Issue 6, 2014, Pages 623-643

  Lehtinen, Timo O A ^a   Mäntylä, Mika V ^a   Vanhanen, Jari ^a   Itkonen, Juha ^a   Lassenius, Casper ^a  

^a AALTO UNIVERSITY   (Finland)

Author keywords

Cause and effect relationships; Multiple case study; Root cause analysis; Software project failure

Indexed keywords

INFORMATION SYSTEMS; SOFTWARE ENGINEERING;

CAUSAL RELATIONSHIPS; CAUSE-AND-EFFECT RELATIONSHIPS; COMMON DENOMINATORS; MULTIPLE-CASE STUDY; PROCESS IMPROVEMENT; ROOT CAUSE ANALYSIS; SOFTWARE PRODUCT COMPANIES; SOFTWARE PROJECT;

SOFTWARE TESTING;

EID: 84897063809     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.infsof.2014.01.015     Document Type: Article

References (84)

1. P. Naur, B. Randel, Software Engineering: A Report on a Conference Sponsored by the NATO Science Committee, NATO, 1969.
2. A. Burr, M. Owen (Eds.), Statistical Methods for Software Quality: Using Metrics for Process Improvement. ITP A Division of International Thomson Publishing Inc., 1996.
3. J.J. Rooney, and L.N. Vanden Heuvel Root cause analysis for beginners Qual. Prog. 37 7 2004 45 53
4. T.O.A. Lehtinen, M.V. Mäntylä, and J. Vanhanen Development and evaluation of a lightweight root cause analysis method (ARCA method) - field studies at four software companies Inform. Softw. Technol. 53 10 2011 1045 1061
5. D.N. Card Learning from our mistakes with defect causal analysis IEEE Softw. 15 1 1998 56 63
6. R. Chillarege, I.S. Bhandari, J.K. Chaar, M.J. Halliday, D.S. Moebus, B.K. Ray, and M. Wong Orthogonal defect classification - a concept for in-process measurements IEEE Trans. Softw. Eng. 18 11 1992 943 956
7. K. Ishikawa Introduction to Quality Control 1990 JUSE Press Ltd. 3A Corporation, Shoei., 6-3, Sarugaku-cho 2-chome, Chiyoda-ku, Tokyo 101, Japan
8. N. Cerpa, and J.M. Verner Why did your project fail? Commun. ACM 52 2009 130 134
9. J. Dye, and T. van der Schaaf PRISMA as a quality tool for promoting customer satisfaction in the telecommunications industry Reliab. Eng. Syst. Saf. 75 3 2002 303 311
10. J. Capers Social and technical reasons for software project failures Crosstalk J. Defense Softw. Eng. 6 2006 4 9
11. M. Keil, P.E. Cule, K. Lyytinen, and R.C. Schmidt A framework for identifying software project risks Commun. ACM 41 11 1998 76 83
12. K.A. Demir, A survey on challenges of software project management, in: Proceedings of the 2009 International Conference on Software Engineering Research Practice, 2009, pp. 13-16.
13. L.A. Kappelman, R. McKeeman, and L. Zhang Early warning signs of IT project failure: the dominant dozen Inform. Syst. Manage. 23 2006 31 36
14. K. Moløkken-Østvold, and M. Jørgensen A comparison of software project overruns - flexible versus sequential development models IEEE Trans. Softw. Eng. 31 9 2005 754 766
15. K. Moløkken-Østvold, M. Jørgensen, A review of survey on software effort estimation, in: Proc. 2003 ACM-IEEE Int'l Symp. Empirical Software Eng. (ISESE 2003), 2003, pp. 220-230.
16. J. Verner, J. Sampson, N. Cerpa, What factors lead to software project failure, in: Proceedings of Research Challenges in Information Science (RCIS 2008), 2008, pp. 71-80.
17. L.J. May Major causes of software project failures Crosstalk J. Defense Softw. Eng. 11 1998 9 12
18. J.M. Verner, and L.M. Abdullah Exploratory case study research: outsourced project failure Inf. Softw. Technol. 54 2012 866 886
19. R.B. Grady Software failure analysis for high-return process improvement decisions Hewlett-Packard J. 47 4 1996 15 25
20. J. Jacobs, J. Van Moll, P. Krause, R. Kusters, J. Trienekens, and A. Brombacher Exploring defect causes in products developed by virtual teams Inf. Softw. Technol. 47 2005 399 410
21. M. Leszak, D.E. Perry, D. Stoll, A case study in root cause defect analysis, in: Proceedings of the 2000 International Conference on Software Engineering, 2000, pp. 428-437.
22. T. Nakashima, M. Oyama, H. Hisada, and N. Ishii Analysis of software bug causes and its prevention Inf. Softw. Technol. 41 1999 1059 1068
23. T. Stålhane, Root cause analysis and gap analysis - a tale of two methods, in: EuroSPI 2004, Trondheim, Norway, 2004, pp. 150-160.
24. M. Kalinowski, G.H. Travassos, D.N. Card, Towards a defect prevention based process improvement approach, in: Proceedings of the 34th EUROMICRO Conference on Software Engineering and Advanced Applications, Parma, Italy, 2008, pp. 199-206.
25. L. Xiangnan, L. Hong, Y. Weijie, Analysis failure factors for small & medium software projects based on PLS method, in: The 2nd IEEE International Conference on Information Management and Engineering (ICIME), 2010, pp. 676-680.
26. X. Lu, H. Liu, W. Ye, Analysis failure factors for small & medium software projects based on PLS, in: Proceedings of Information Management and Engineering (ICIME 2010), 2010, pp. 676-680.
27. L. McLeod, and S.G. MacDonell Factors that affect software systems development project outcomes: a survey of research ACM Comput. Surv. 43 2011 24 55
28. R.J. Latino, and K.C. Latino Root Cause Analysis: Improving Performance for Bottom-Line Results 2006 CRC Press 6000 Broken Sound Parkway NW, Suite 300, Boca Raton, FL 33487-2742
29. F.O. Bjørnson, A.I. Wang, and E. Arisholm Improving the effectiveness of root cause analysis in post mortem analysis: a controlled experiment Inf. Softw. Technol. 51 1 2009 150 161
30. P. Jalote, N. Agrawal, Using defect analysis feedback for improving quality and productivity in iterative software development, in: Proceedings of the Information Science and Communications Technology (ICICT 2005), 2005, pp. 701-714.
31. R.G. Mays Applications of defect prevention in software development IEEE J. Sel. Areas Commun. 8 1990 164 168
32. S.O. Al-Mamory, and H. Zhang Intrusion detection alarms reduction using root cause analysis and clustering Comput. Commun. 32 2 2009 419 430
33. M. Siekkinen, G. Urvoy-Keller, E.W. Biersack, and D. Collange A root cause analysis toolkit for TCP Comput. Netw. 2008 1846 1858
34. A. Traeger, I. Deras, E. Zadok, DARC: dynamic analysis of root causes of latency distributions, in: SIGMETRICS '08, Annapolis, Maryland, USA, 2008, pp. 277-288.
35. I. Bhandari, M. Halliday, E. Tarver, D. Brown, J. Chaar, and R. Chillarege A case study of software process improvement during development IEEE Trans. Softw. Eng. 19 12 1993 1157 1170
36. Z.X. Jin, J. Hajdukiewicz, G. Ho, D. Chan, Y. Kow, Using root cause data analysis for requirements and knowledge elicitation, in: International Conference on Engineering Psychology and Cognitive Ergonomics (HCII 2007), Berlin, Germany, 2007, pp. 79-88.
37. W. Al-Ahmad, K. Al-Fagih, K. Khanfar, K. Alsamara, S. Abuleil, and H. Abu-Salem A taxonomy of an IT project failure: root causes Int. Manage. Rev. 5 2009 93 104
38. R.L. Glass Evolving a new theory of project success Commun. ACM 42 1999 17 19
39. N. Agarwal, and U. Rathod Defining 'success' for software projects: an exploratory revelation Int. J. Project Manage. 24 2006 358 370
40. J.D. Procaccino, J.M. Verner, K.M. Shelfer, and D. Gefen What do software practitioners really think about project success: an exploratory study J. Syst. Softw. 78 2005 194 203
41. T.O.A. Lehtinen, M.V. Mäntylä, What are problem causes of software projects? Data of root cause analysis at four software companies, in: ESEM '11 Proc. of the 2011 International Symposium on Empirical Software Engineering and Measurement, 2011, pp. 388-391.
42. M. Nasir, and S. Sahibuddin Critical success factors for software projects: a comparative study Sci. Res. Essays 6 2011 2174 2186
43. N.H. Arshad, A. Mohamed, Z. Matnor, Risk factors in software development projects, in: Proceedings of the 6th WSEAS Int. Conf. on Software Engineering, Parallel and Distributed Systems, 2007, pp. 51-56.
44. M. Tarawneh, H. AL-Tarawneh, A. Elsheikh, Software development projects: an investigation into the factors that affect software project success/failure in Jordanian firms, in: First International Conference on the Applications of Digital Information and Web Technologies, ICADIWT, 2008, pp. 246-251.
45. K. El Emam, and A.G. Koru A replicated survey of IT software project failures Softw. IEEE 25 2008 84 90
46. E. Egorova, M. Torchiano, and M. Morisio Actual vs. perceived effect of software engineering practices in the Italian industry JSS 83 2010 1907 1916
47. R.C. Mahaney, and A.L. Lederer The effect of intrinsic and extrinsic rewards for developers on information systems project success Proj. Manage. J. 37 2006 42
48. J. Drew Procaccino, J.M. Verner, S.P. Overmyer, and M.E. Darter Case study: factors for early prediction of software development success Inf. Softw. Technol. 44 2002 53 62
49. N. Cerpa, M. Bardeen, B. Kitchenham, and J. Verner Evaluating logistic regression models to estimate software project outcomes Inf. Softw. Technol. 52 2010 934 944
50. C. Jones Software tracking: the last defense against failure Crosstalk J. Defense Softw. Eng. 21 2008
51. R. Kaur, and J. Sengupta Software process models and analysis on failure of software development projects Int. J. Sci. Eng. Res. 2 2011 2 3
52. M.P. Álvarez The four causes of behavior: Aristotle and Skinner Int. J. Psychol. Psychol. Ther. 9 2009 45 57
53. D. Hume A Treatise of Human Nature [1739] 1896 Clarendon Press Oxford
54. J. Pearl Causality: Models Reasoning, and Inference 2000 Cambridge University Press United States of America
55. C.W. Granger Some recent development in a concept of causality J. Econ. 39 1988 199 211
56. D. Galles, and J. Pearl Axioms of causal relevance Artif. Intell. 97 1997 9 43
57. C. Eden Analyzing cognitive maps to help structure issues or problems Eur. J. Oper. Res. 2004 673 686
58. P. Monteiro, R.J. Machado, R. Kazman, and C. Henriques Dependency analysis between CMMI process areas PROFES, LNCS 6156 2010 263 275
59. Y. Wang, and G. King Software Engineering Processes: Principles and Applications 2000 CRC Press LLC
60. K. Lyytinen, and D. Robey Learning failure in information systems development Info Syst. 1999 85 101
61. D.L. Cooke, Learning from incidents, in: Proceedings of the 21st International Conference of the System Dynamics Society, New York, NY, USA, 2003, pp. 1-30.
62. T. Dingsøyr Postmortem reviews: purpose and approaches in software engineering Inf. Softw. Technol. 47 2005 293 303
63. B. Collier, T. DeMarco, and P. Fearey A defined process for project post mortem review Softw. IEEE 13 1996 65 72
64. D.N. Card Defect-causal analysis drives down error rates Qual. Time 10 4 1993 98 99
65. A. Gupta, J. Li, R. Conradi, H. Rönneberg, and E. Landre A case study comparing defect profiles of a reused framework and of applications reusing it Empir. Softw. Eng. 14 2 2008 227 255
66. R.K. Yin Case Study Research: Design and Methods 1994 SAGE Publications United States of America
67. P. Runeson, and M. Höst Guidelines for conducting and reporting case study research in software engineering Empir. Softw. Eng. 14 2008 131 164
68. T.D. Jick Mixing qualitative and quantitative methods: triangulation in action Adm. Sci. Q. 24 1979 602 611
69. W. Foddy Constructing Questions for Interviews and Questionnaires 1994 Cambridge University Press Hong Kong by Colorcraft
70. S. Salinger, L. Plonka, L. Prechelt, A coding scheme development methodology using grounded theory for qualitative analysis of pair programming, in: 19th Annual Psychology of Programming Workshop, Joensuu, 2007, pp. 144-157.
71. I. Jacobson, G. Booch, and J. Rumbaugh The Unified Software Development Process 1998 Addison-Wesley
72. W. Royce Managing the development of large software systems Proc. IEEE WESCON 26 August 1970 328 338
73. CMMI Product Team, "Capability Maturity Model Integration, Version 1.2, CMMI for Development" CMU/SEI-2006-TR-008, ESC-TR-2006-008, 2006.
74. P. Conroy Technical debt: where are the shareholders' interests? IEEE Softw. 29 2012 87 88
75. T. DeMarco All late projects are the same IEEE Softw. 2011 103 104
76. F. Reyes, N. Cerpa, A. Candia-Véjar, and M. Bardeen The optimization of success probability for software projects using genetic algorithms J. Syst. Softw. 84 2011 775 785
77. Y. Takagi, O. Mizuno, and T. Kikuno An empirical approach to characterizing risky software projects based on logistic regression analysis Empir. Softw. Eng. 10 2005 495 515
78. H. Steck, V. Tresp, Bayesian belief networks for data mining, in: Proceedings of the 2nd Workshop on Data Mining Und Data Warehousing Als Grundlage Moderner Entschidungsunterstuezender Systeme, DWDW99, Sammelband, Universität Magdeburg, 1999.
79. A. Alaeddini, and I. Dogan Using Bayesian networks for root cause analysis in statistical process control Expert Syst. Appl. 2011 11230 11243
80. J. Cheng, R. Greiner, Comparing Bayesian network classifiers, In: Proceedings of the Fifteenth Conference on Uncertainty in Artificial Intelligence, 1999, pp. 101-108.
81. A. Ayad Critical thinking and business process improvement J. Manage. Dev. 29 2010 556 564
82. K. El Emam, I. Wieczorek, The repeatability of code defect classifications, In: ISSRE '98 Proceedings of the Ninth International Symposium on Software, Reliability Engineering, 1998.
83. M.V. Mäntylä, and C. Lassenius What types of defects are really discovered in code reviews? IEEE Trans. Softw. Eng. 35 2009 430 448
84. R.M. Daniel, M.G. Kenward, S.N. Cousens, and B.L. De Stavola Using causal diagrams to guide analysis in missing data problems Pubmed 21 2012 243 256