Runaway information systems projects and escalating commitment

Permission to make digital or hard copies ofall or part ofthis work for personal or classroom use is granted without fee probided that copies are not made or distrihuted for prolit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise. to republish. to post on servers or to redistribute to lists. requires prior specific permission and:or a fee. SIGCPR ‘99 New Orleans LA USA Copyright ACM 1999 I-581 13-063-5/99/04...$5.00 ns Projects and Escalating itment

[1]  B. M. Staw.  The Escalation of Commitment To a Course of Action , 1981 .

[2]  Barry M. Staw,et al.  Knee-deep in the Big Muddy: A study of escalating commitment to a chosen course of action. , 1976 .

[3]  Sigal G. Barsade,et al.  Escalation at the Credit Window: A Longitudinal Study of Bank Executives' Recognition and Write-Off of Problem Loans , 1997 .

[4]  KeilMark,et al.  Understanding runaway information technology projects , 1994 .

[5]  Robert L. Glass.  Software runaways—some surprising findings , 1997, DATB.

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

[7]  Jeffrey Rothfeder,et al.  It's late, costly, incompetent—but try firing a computer system , 1989 .

[8]  Barry M. Staw,et al.  The Trapped Administrator: Effects of Job Insecurity and Policy Resistance upon Commitment to a Course of Action. , 1979 .

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

[10]  K. Eisenhardt.  Agency Theory: An Assessment and Review , 1989 .

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

[12]  Grady Booch,et al.  When bad things happen to good projects , 1994 .

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

[14]  Richard A. Huff.  An experimental investigation of information systems project escalation : an examination of contributory factors in a business environment , 1997 .

[15]  Barry M. Staw,et al.  Commitment to a Policy Decision: A Multi-Theoretical Perspective. , 1978 .

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

[17]  Timo Saarinen,et al.  Understanding Runaway Information Technology Projects: Results from an International Research Program Based on Escalation Theory , 1994, J. Manag. Inf. Syst..

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

[19]  H. Garland.  Throwing Good Money After Bad: The Effect of Sunk Costs on the Decision to Escalate Commitment to an Ongoing Project , 1990 .

[20]  W. H. Keown.  Fundamentals of management. , 1956, Journal of the American Dietetic Association.

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

[22]  Albert L. Lederer,et al.  Causes of inaccurate software development cost estimates , 1995, J. Syst. Softw..