When is it time to stop an IT project

IT projects should deliver value to organizations but there are cases when, however well planned a project may have been, changes in the environment and/or in the strategic priorities of the organization mean it can never deliver value. Value is a subjective term and simply means, in this context, something that is important to the organization which would generally result in profit, in a commercial entity, or improved service, in a public entity. This paper addresses the problem of how to ensure that you will have the capabilities in place to know when your project can no longer deliver value and to take appropriate action. It does not discuss in detail the technical issues of project management execution, as a well-executed project can still fail to deliver value. Rather, it looks at the specific question of knowing when projects can no longer deliver value and putting measures in place to both prevent and address project escalation. We show how a capability based approach supported by the IT-CMF framework can improve your ability to quickly identify projects that have started but now can no longer deliver value. This capability approach increases the agility of the organization and makes it easier to develop and maintain competitive advantage.

[1]  Joe Peppard,et al.  DESIGNED TO FAIL: WHY IT PROJECTS UNDERACHIEVE AND WHAT TO DO ABOUT IT , 2008 .

[2]  Shan Ling Pan,et al.  Escalation and de‐escalation of commitment: a commitment transformation analysis of an e‐government project , 2006, Inf. Syst. J..

[3]  J. Brockner The Escalation of Commitment to a Failing Course of Action: Toward Theoretical Progress , 1992 .

[4]  Brian Donnellan,et al.  A Capability Maturity Framework for Sustainable Information and Communication Technology , 2011, IT Professional.

[5]  Bud Baker The Fall of the Firefly: An Assessment of a Failed Project Strategy , 2002 .

[6]  M A Beasley,et al.  Knowing when to pull the plug. Several key factors reveal when it's time to terminate a program. , 1991, Food management.

[7]  Hy Sockel,et al.  A confirmatory factor analysis of IS employee motivation and retention , 2001, Inf. Manag..

[8]  J. Smyrk A General Framework for Gauging the Performance of Initiatives to Enhance Organizational Value , 2012 .

[9]  Sinéad Murnane,et al.  Leveraging IT Capabilities to Accelerate Business Value Impact from Electronic Medical Record Adoption , 2013 .

[10]  Mark Keil,et al.  De-escalating IT projects: the DMM model , 2009, CACM.

[11]  John M. Ward,et al.  Beyond strategic information systems: towards an IS capability , 2004, J. Strateg. Inf. Syst..

[12]  Paul L. Bannerman,et al.  Why Good Project Management Is Not Enough: Liabilities of Incumbency and Newness , 2012 .

[13]  Salvatore T. March,et al.  Design and natural science research on information technology , 1995, Decis. Support Syst..

[14]  Sunder Kekre,et al.  Business Value of Information Technology: A Study of Electronic Data Interchange , 1995, MIS Q..

[15]  Christina Soh,et al.  How IT Creates Business Value: A Process Theory Synthesis , 1995, ICIS.

[16]  Saleem Abuleil,et al.  A Taxonomy of an IT Project Failure: Root Causes , 2009 .

[17]  Gary S. C. Pan Information systems project abandonment: a stakeholder analysis , 2005, Int. J. Inf. Manag..

[18]  Marian Carcary,et al.  Design Science Research: The Case of the IT Capability Maturity Framework (IT CMF) , 2011 .

[19]  Bernard C. Y. Tan,et al.  A Cross-Cultural Study on Escalation of Commitment Behavior in Software Projects , 2000, MIS Q..

[20]  M. Keil,et al.  Is Your Project Turning into a Black Hole? , 2010 .

[21]  Gary S. C. Pan The Hidden Dilemmas in Software Development Project Decisionmaking: Persist or Desist? , 2006, PACIS.

[22]  Kenneth L. Kraemer,et al.  Review: Information Technology and Organizational Performance: An Integrative Model of IT Business Value , 2004, MIS Q..

[23]  Martin Curley,et al.  The IT Transformation at Intel , 2006, MIS Q. Executive.

[24]  Chris Sauer,et al.  Lessons from a failed information systems initiative: issues for complex organisations , 1999, Int. J. Medical Informatics.

[25]  Martin Curley,et al.  Creating a New IT Management Framework Using Design Science , 2011 .

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

[27]  Mark Keil,et al.  Turning Around Troubled Software Projects: An Exploratory Study of the Deescalation of Commitment to Failing Courses of Action , 1999, J. Manag. Inf. Syst..

[28]  N. Carr IT doesn't matter , 2003, IEEE Engineering Management Review.