Runaway Information Technology Projects: A Punctuated Equilibrium Analysis

This paper presents an in-depth insider's case study of a "runaway" information systems IS project in a U.S. State government agency. Because such projects are politically sensitive matters and often obscured from public view, details of how such projects operate are not well understood. This case study adds new details to the body of knowledge surrounding IS project escalation and de-escalation. The authors' resulting project narrative details how this project went out of control for so long, raising important questions for future research in theory development for both IS project escalation and de-escalation. The paper argues that a punctuated equilibrium approach to analyzing "runaway" IS projects are a more fruitful area to explore than are "stage models."

[1]  James M. Utterback,et al.  Radical Innovation and Corporate Regeneration , 1994 .

[2]  H. Klein,et al.  Information systems development as social action: Theoretical perspective and practice , 1991 .

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

[4]  Joan CheneyMann,et al.  Preventing Runaway IT Projects: Protecting Auditors from Entrapment , 2003, AMCIS.

[5]  Laurie J. Kirsch,et al.  Portfolios of Control Modes and IS Project Management , 1997, Inf. Syst. Res..

[6]  Udechukwu Ojiako,et al.  A Management Perspective on the Failure of IS&T Projects , 2012, Int. J. Inf. Technol. Proj. Manag..

[7]  Joel Mokyr,et al.  The Lever of Riches: Technological Creativity and Economic Progress , 1991 .

[8]  Michael J. Cuellar,et al.  The Deaf Effect Response to Bad News Reporting in Information Systems Projects , 2006 .

[9]  Ulrike Schultze,et al.  A Confessional Account of an Ethnography About Knowledge Work , 2000, MIS Q..

[10]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[11]  C. Gersick.  MARKING TIME: PREDICTABLE TRANSITIONS IN TASK GROUPS , 1989 .

[12]  Janet Toland,et al.  E-Mail Usage in South Pacific Distance Education , 2005, Encyclopedia of Information Science and Technology.

[13]  Richard Staelin,et al.  Pulling the Plug to Stop the New Product Drain , 1997 .

[14]  Mark Keil,et al.  The reluctance to report bad news on troubled software projects: a theoretical model , 2003, Inf. Syst. J..

[15]  W. R. King,et al.  Decision Processes for Developing Strategic Applications of Information Systems: A Contingency Approach* , 1992 .

[16]  William A. Kahn.  Psychological Conditions of Personal Engagement and Disengagement at Work , 1990 .

[17]  Antonio Cartelli,et al.  Encyclopedia of Information Communication Technology , 2008 .

[18]  Mark Keil,et al.  The challenge of accurate software project status reporting: a two-stage model incorporating status errors and reporting bias , 2002, IEEE Trans. Engineering Management.

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

[20]  Kimberly D. Elsbach,et al.  Acquiring Organizational Legitimacy Through Illegitimate Actions: A Marriage of Institutional and Impression Management Theories , 1992 .

[21]  Sumeet Gupta,et al.  Developing the Commitment to Virtual Community: The Balanced Effects of Cognition and Affect , 2007, Inf. Resour. Manag. J..

[22]  Donald E. Conlon,et al.  Too Close to Quit: The Role of Project Completion in Maintaining Commitment1 , 1998 .

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

[24]  Mehdi Khosrow-Pour,et al.  Printed at: , 2011 .

[25]  Giorgio Poletti.  Comparison of Technologies and Methodologies in the E-Learning EXPO Experience , 2009 .

[26]  A. Pettigrew.  Longitudinal Field Research on Change: Theory and Practice , 1990 .

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

[28]  Barry M. Staw,et al.  Expo 86: An Escalation Prototype. , 1986 .

[29]  Cheng-Suang Heng,et al.  De-escalation of commitment in software projects: Who matters? What matters? , 2003, Inf. Manag..

[30]  R. P. Sundarraj,et al.  Application of an Extended TAM Model for Online Banking Adoption: A Study at a Gulf-region University , 2011, Inf. Resour. Manag. J..

[31]  Glen Whyte,et al.  Escalating Commitment to a Course of Action: A Reinterpretation , 1986 .

[32]  R. I. Sutton.  The Process of Organizational Death: Disbanding and Reconnecting , 1987 .

[33]  L. Festinger,et al.  A Theory of Cognitive Dissonance , 2017 .

[34]  Laurie J. Kirsch,et al.  Requirements determination for common systems: turning a global vision into a local reality , 2006, J. Strateg. Inf. Syst..

[35]  J. Utterback.  One Point of View: Radical Innovation and Corporate Regeneration , 1994 .

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

[37]  Glen Whyte,et al.  ESCALATING COMMITMENT IN GROUP DECISION MAKING. , 2007 .

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

[39]  Michael M. J. Fischer,et al.  [Book review] anthropology as cultural critique, an experimental moment in the human sciences , 1986 .

[40]  William J. Abernathy,et al.  Patterns of Industrial Innovation , 1978 .

[41]  Joel Brockner,et al.  Entrapment in Escalating Conflicts: A Social Psychological Analysis , 2011 .

[42]  Mehdi Khosrowpour,et al.  Dictionary of Information Science and Technology , 2006 .

[43]  M. Hammersley,et al.  Ethnography and participant observation. , 1994 .

[44]  Tom DeMarco,et al.  Controlling Software Projects , 1982 .

[45]  M. Miles.  Qualitative Data as an Attractive Nuisance: The Problem of Analysis , 1979 .

[46]  Barry M. Staw,et al.  ORGANIZATIONAL ESCALATION AND EXIT: LESSONS FROM THE SHOREHAM NUCLEAR POWER PLANT , 1993 .

[47]  M. Tushman,et al.  Technological Discontinuities and Dominant Designs: A Cyclical Model of Technological Change , 1990 .

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

[49]  Nicolaj Siggelkow.  Persuasion with case studies , 2007 .

[50]  Lynn A. Isabella.  Evolving Interpretations as a Change Unfolds: How Managers Construe Key Organizational Events , 1990 .

[51]  Elaine Romanelli,et al.  Convergence and Upheaval: Managing the Unsteady Pace of Organizational Evolution , 1986 .

[52]  C. Gersick.  REVOLUTIONARY CHANGE THEORIES: A MULTILEVEL EXPLORATION OF THE PUNCTUATED EQUILIBRIUM PARADIGM , 1991 .

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

[54]  H. Russell Johnston,et al.  Developing Capabilities to Use Information Strategically , 1988, MIS Q..

[55]  H. Arkes.  Costs and benefits of judgment errors: Implications for debiasing. , 1991 .

[56]  KeilMark,et al.  Why software projects escalate , 2000 .

[57]  Ashley A. Bush,et al.  A Comparison of Transaction Cost, Agency, and Knowledge-Based Predictors of IT Outsourcing Decisions: A U.S.-Japan Cross-Cultural Field Study , 2007, J. Manag. Inf. Syst..

[58]  Joel Brockner,et al.  Factors affecting withdrawal from an escalating conflict: Quitting before it's too late , 1979 .

[59]  Barry M. Staw,et al.  Organizational decision making: The escalation of commitment: An update and appraisal , 1996 .

[60]  Ivan Bruha.  Knowledge Combination vs. Meta-Learning , 2009 .

[61]  Charles J. Capps,et al.  Information Technology Customer Service: ―Best Practices‖ Processes For Operations , 2011 .

[62]  Mark Keil,et al.  The effects of optimistic and pessimistic biasing on software project status reporting , 2007, Inf. Manag..

[63]  Dennis Duchon,et al.  An Empirical Test of Staw and Ross's Prescriptions for the Management of Escalation of Commitment Behavior in Organizations* , 1989 .

[64]  Deborah G. . Ancona.  Outward Bound: Strategic for Team Survival in an Organization , 1990 .

[65]  Joel Brockner,et al.  Factors affecting entrapment in waiting situations: The Rosencrantz and Guildenstern effect. , 1975 .

[66]  Joel Brockner,et al.  Factors Affecting Entry into Psychological Traps , 1980 .

[67]  I. Royer.  Why bad projects are so hard to kill. , 2003, Harvard business review.

[68]  Stanley Baiman,et al.  AGENCY RESEARCH IN MANAGERIAL ACCOUNTING: A SECOND LOOK. , 1990 .

[69]  B. Turner,et al.  Grounded Theory and Organizational Research , 1986 .

[70]  M. Tushman,et al.  Organizational Evolution: A Metamorphosis Model of Convergence and Reorientation , 1985 .

[71]  Paula M. Bach,et al.  Knowledge Management Challenges in the Non-Profit Sector , 2009 .

[72]  R. Calantone,et al.  Escalation of commitment during new product development , 2002 .

[73]  Charles I. Stubbart,et al.  The Deceptive Allure of Stage Models of Strategic Processes , 1999 .

[74]  A. Tversky,et al.  The framing of decisions and the psychology of choice. , 1981, Science.

[75]  W. Firestone,et al.  Multisite Qualitative Policy Research: Optimizing Description and Generalizability , 1983 .

[76]  Mark Keil,et al.  Information Technology Project Escalation: A Process Model , 2008, Decis. Sci..

[77]  M. Tushman,et al.  Technological Discontinuities and Organizational Environments , 1986 .

[78]  Mark Keil,et al.  Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models , 2000, MIS Q..

[79]  Cynthia Mathis Beath,et al.  Linking Information Technology and Corporate Strategy: an Organizational View , 1986, ICIS.

[80]  Robert W. Zmud,et al.  Management of Large Software Development Efforts , 1980, MIS Q..

[81]  Laurie J. Kirsch,et al.  Deploying Common Systems Globally: The Dynamics of Control , 2004, Inf. Syst. Res..

[82]  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..

[83]  Daniel Robey,et al.  A Dual-Motor, Constructive Process Model of Organizational Transition , 2004 .

[84]  M. C. Jensen,et al.  THEORY OF THE FIRM: MANAGERIAL BEHAVIOR, AGENCY COSTS AND OWNERSHIP STRUCTURE , 1976 .

[85]  Helga Drummond,et al.  Is Escalation Always Irrational? , 1998 .

[86]  Aaron J. Shenhar,et al.  From theory to practice: toward a typology of project-management styles , 1998 .

[87]  Wanda J. Orlikowski,et al.  CASE Tools as Organizational Change: Investigating Incremental and Radical Changes in Systems Development , 1993, MIS Q..

[88]  Charalambos L. Iacovou,et al.  The linkage between reporting quality and performance in IS projects , 2007, Inf. Manag..