Understanding the Context of Large-Scale IT Project Failures

Large-scale information technology IT projects experience higher failure or abandonment rates than smaller IT projects and represent significant costs to both organizations and society. This paper describes the context of a three-decade long attempt to modernize a critical IT application in the U.S. government. The project has been revamped, stopped and restarted several times, and as of the writing of this paper has not been completed. Archival analysis of this implementation history reveals a set of emerging project characteristics and how these contributed to a pair of capability gaps which, in turn, influenced modernization efforts both pre-and post-abandonment. From a systems perspective, the problem appears to be related to dynamic and repeating management failures with an embedded project management model. The authors illustrate their hypothesis with a simulation model of project managements and show that even a relatively small but persistent introduction of new requirements has a dramatic effect on project overruns, setting the stage for abandonment and restart.

[1]  Stuart E. Madnick,et al.  The elusive silver lining: how we fail to learn from failure in software development , 2011 .

[2]  A. Levy Second-order planned change: Definition and conceptualization , 1986 .

[3]  Joel Slemrod,et al.  Did the Tax Reform Act of 1986 Simplify Tax Matters , 1992 .

[4]  Barry M. Staw,et al.  Escalation: The Determinants of Commitment to a Chosen Course of Action , 1977 .

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

[6]  Rajiv Sabherwal,et al.  Determinants of Commitment to Information Systems Development: A Longitudinal Investigation , 1996, MIS Q..

[7]  Kenneth Cooper Naval Ship Production: A Claim Settled and a Framework Built , 1980 .

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

[9]  Barry M. Staw,et al.  Behavior in escalation situations: Antecedents, prototypes, and solutions. , 1987 .

[10]  Helga Drummond,et al.  Too Little Too Late: A Case Study of Escalation in Decision Making , 1994 .

[11]  George P. Richardson,et al.  Introduction to System Dynamics Modeling with DYNAMO , 1981 .

[12]  George P. Richardson,et al.  Teamwork in group model building , 1995 .

[13]  William Weitzel,et al.  Decline in Organizations: A Literature Integration and Extension. , 1989 .

[14]  W. Wayt Gibbs,et al.  Software's Chronic Crisis , 1994 .

[15]  J. Lyneis,et al.  The dynamics of project performance: benchmarking the drivers of cost and schedule overrun , 1999 .

[16]  Stuart E. Madnick,et al.  Software Project Dynamics: An Integrated Approach , 1991 .

[17]  Raymond Madachy,et al.  Software Process Dynamics , 2008 .

[18]  Ramiro Montealegre,et al.  De-escalating Information Technology Projects: Lessons from the Denver International Airport , 2000, MIS Q..

[19]  Mark Keil,et al.  Why software projects escalate: the importance of project management constructs , 2003, IEEE Trans. Engineering Management.