Eliminating Failure by Learning from It - Systematic Review of IS Project Failure

Researchers analyzing project success and failure emphasize the prevailing challenge of successfully completing information system (IS) projects. We conduct an extensive systematic literature review of factors that contributed to failure of real-life IS projects. Our resulting overview entails 54 failure factors, which we grouped in 10 categories applying data-driven qualitative content analysis. We extend our holistic overview by linking the factors to specific project failure dimensions and integrating a stakeholder perspective to account for failure responsibility. Our analysis yields widely acknowledged failure factors like insufficient stakeholder involvement as well as less common factors like history of prior successes. Researchers gain insights into project failure factors along with responsible stakeholders and affected failure dimensions, and can use our overview to identify factors or areas of concern to guide future research. Our overview provides a pillar for IS practitioners to learn from others and to eliminate failure by avoiding past mistakes.

[1]  A. Shenhar,et al.  Project Success: A Multidimensional Strategic Concept , 2001 .

[2]  Walid Belassi,et al.  A new framework for determining critical success/failure factors in projects , 1996 .

[3]  R. Müller,et al.  The Influence of Project Managers on Project Success Criteria and Project Success by Type of Project , 2007 .

[4]  Mark A. Fuller,et al.  Information Systems Project Management: A Process and Team Approach , 2010 .

[5]  Carl B Traylor Project Management: A Systems Approach to Planning, Scheduling, and Controlling , 2014 .

[6]  Marco Torchiano,et al.  Stakeholders' Perception of Success: An Empirical Investigation , 2009, 2009 35th Euromicro Conference on Software Engineering and Advanced Applications.

[7]  Kenneth A. Kozar,et al.  Management's Role in Information System Development Failures: A Case Study , 1978, MIS Q..

[8]  Urvashi Rathod,et al.  Defining ‘success’ for software projects: An exploratory revelation , 2006 .

[9]  Jakub Miler,et al.  Proc. of 17th International Conference " Software & Systems Engineering and Their Applications " Identifying Software Project Risks with the Process Model , 2004 .

[10]  Jan Pries-Heje,et al.  Making IT Project De-Escalation Happen: An Exploration into Key Roles , 2008, J. Assoc. Inf. Syst..

[11]  Herman Steyn,et al.  Project management for business, engineering, and technology : principles and practice , 2008 .

[12]  Walter Fernandez,et al.  Success in IT projects: A matter of definition? , 2008 .

[13]  Claudia Löbbecke,et al.  Project managers' perception of IS project success factors - a repertory grid investigation , 2011, ECIS.

[14]  A. Michael Huberman,et al.  An expanded sourcebook qualitative data analysis , 1994 .

[15]  B. N. Baker,et al.  Factors Affecting Project Success , 2008 .

[16]  W SchmittJohn,et al.  Management's role in information system development failures , 1978 .

[17]  John Wateridge,et al.  How can IS/IT projects be measured for success? , 1998 .

[18]  Irja Hyväri,et al.  Success of Projects in Different Organizational Conditions , 2006 .

[19]  C. Lance,et al.  The Sources of Four Commonly Reported Cutoff Criteria , 2006 .

[20]  June M. Verner,et al.  Software project managers and project success: An exploratory study , 2006, J. Syst. Softw..

[21]  J. Rockart Chief executives define their own data needs. , 1979, Harvard business review.

[22]  R. Ryan Nelson,et al.  Project Retrospectives: Evaluating Project Success, Failure, and Everything in Between , 2005, MIS Q. Executive.

[23]  Raymond Young,et al.  Top management support - fuzzy set analysis finding TMS the most important , 2011 .

[24]  Nannette P. Napier,et al.  IT project managers' construction of successful project management practice: a repertory grid investigation , 2009, Inf. Syst. J..

[25]  B MilesMatthew,et al.  Qualitative Data Analysis , 2009, Approaches and Processes of Social Science Research.

[26]  Adam Collins,et al.  PROJECT SUCCESS — A SURVEY , 2004 .

[27]  Joyce Fortune,et al.  Framing of project critical success factors by a systems model , 2006 .

[28]  Andrew Martin,et al.  A model of information systems development project performance , 2000, Inf. Syst. J..

[29]  Stacie Petter,et al.  Managing User Expectations on Software Projects: Lessons from the Trenches , 2008 .

[30]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[31]  Richard T. Watson,et al.  Analyzing the Past to Prepare for the Future: Writing a Literature Review , 2002, MIS Q..

[32]  Kalle Lyytinen,et al.  A framework for identifying software project risks , 1998, CACM.

[33]  H. Goldstein,et al.  Who killed the virtual case file? [case management software] , 2005, IEEE Spectrum.

[34]  Ernest Jordan,et al.  Top management support: mantra or necessity? , 2008 .

[35]  Mark Keil,et al.  Software project risks and their effect on outcomes , 2004, CACM.

[36]  Effy Oz,et al.  When professional standards are lax: the CONFIRM failure and its lessons , 1994, CACM.

[37]  Jeffrey K. Pinto,et al.  Critical factors in successful project implementation , 1987, IEEE Transactions on Engineering Management.

[38]  Terry Cooke-Davies,et al.  The “real” success factors on projects , 2002 .

[39]  J. Rodney Turner,et al.  THE HANDBOOK OF PROJECT-BASED MANAGEMENT , 2008 .

[40]  Paul Beynon-Davies,et al.  The utility of rapid application development in large‐scale, complex projects , 2009, Inf. Syst. J..

[41]  Rudy Hirschheim,et al.  Information Systems and User Resistance: Theory and Practice , 1988, Comput. J..

[42]  P. Beynon-Davies,et al.  Information systems ‘failure’: the case of the London Ambulance Service's Computer Aided Despatch project , 1995 .

[43]  Jan Terje Karlsen,et al.  What Characterizes Successful It Projects , 2005, Int. J. Inf. Technol. Decis. Mak..

[44]  A. Shenhar,et al.  Project success: a multidimensional, strategic concept , 1997, Innovation in Technology Management. The Key to Global Leadership. PICMET '97.

[45]  Roger Atkinson,et al.  Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria , 1999 .

[46]  Jane P. Laudon,et al.  Management Information Systems: Managing the Digital Firm , 2010 .

[47]  Chris Sauer,et al.  Why information systems fail: a case study approach , 1993 .

[48]  Jon W. Beard,et al.  Information Systems and Health Care VII - When Success Results in Failure: The Challenge of Extending the IT Infrastructure to Support Organ Procurement and Transplantation , 2005, Commun. Assoc. Inf. Syst..

[49]  Eric G. Kirby The importance of recognizing alternative perspectives: an analysis of a failed project , 1996 .

[50]  K. T. Yeo,et al.  Critical failure factors in information system projects , 2002 .

[51]  Kweku-Muata Osei-Bryson,et al.  Determining the Contribution of IS Projects: An Approach to Measure Performance , 2009, 2009 42nd Hawaii International Conference on System Sciences.

[52]  Alain Abran,et al.  The Guide to the Software Engineering Body of Knowledge , 1999, IEEE Softw..

[53]  Stephen P. Keider,et al.  Why Systems Development Projects Fail , 1984 .

[54]  Korin A. Kendra,et al.  Project Success: A Cultural Framework , 2004 .

[55]  Ramiro and,et al.  De-escalating Information Technology Projects: Lessons from the Denver International Airport , 2000 .

[56]  Jeffrey K. Pinto The Elements of Project Success , 2007 .

[57]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[58]  David Baccarini,et al.  The Logical Framework Method for Defining Project Success , 1999 .

[59]  Charlie C. Chen,et al.  Relationships among interpersonal conflict, requirements uncertainty, and software project performance , 2011 .

[60]  June M. Verner,et al.  Why did your project fail? , 2009, Commun. ACM.

[61]  A Straw,et al.  Guide to the Software Engineering Body of Knowledge , 1998 .

[62]  S. M. Kinsella Activity-Based Costing: Does it Warrant Inclusion in a Guide to the Project Management Body of Knowledge (PMBOK® Guide)? , 2002 .

[63]  Michael D. Myers,et al.  Executive information system failure: a New Zealand case study , 1997, PACIS.

[64]  Jolyon Hallows,et al.  Information systems project management , 1998 .

[65]  Nathalie N. Mitev,et al.  A multiple narrative approach to information systems failure: a successful system that failed , 2008, Eur. J. Inf. Syst..

[66]  Lavagnon A. Ika Project Success as a Topic in Project Management Journals , 2009 .

[67]  S. Barker The Easy Guide to Repertory Grids , 2006 .

[68]  Christian Wagner,et al.  Critical success factors revisited: success and failure cases of information systems for senior executives , 2001, Decis. Support Syst..

[69]  John Wateridge,et al.  IT projects: a basis for success , 1995 .

[70]  Adel M. Aladwani An Integrated Performance Model of Information Systems Projects , 2002, J. Manag. Inf. Syst..

[71]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[72]  Guy Fitzgerald,et al.  The turnaround of the London Ambulance Service Computer-Aided Despatch system (LASCAD) , 2005, Eur. J. Inf. Syst..

[73]  Debra Howcroft,et al.  Re-conceptualising failure: social shaping meets IS research , 2002, Eur. J. Inf. Syst..

[74]  Dov Dvir,et al.  In search of project classification: a non-universal approach to project success factors , 1998 .

[75]  Mark Keil,et al.  The user–developer communication process: a critical case study , 2003, Inf. Syst. J..

[76]  D. Bryde Perceptions of the impact of project sponsorship practices on project success , 2008 .