Pulling the plug: Software project management and the problem of project escalation

MIS Quarterly: Management Information Systems

Volumn 19, Issue 4, 1995, Pages 421-443

  Keil, Mark ^a  

^a GEORGIA STATE UNIVERSITY   (United States)

Author keywords

Escalating commitment; Escalation; Implementation; IS failure; Software project management

Indexed keywords

EID: 53349163773     PISSN: 02767783     EISSN: None     Source Type: Journal    
DOI: 10.2307/249627     Document Type: Article

References (48)

1. Allen, T.J. and Marquis, D.G. "Positive and Negative Biasing Sets: The Effects of Prior Experience on Research Performance," IEEE Transactions on Engineering Management (11:4), December 1964, pp. 158-161.
2. Alter, S. and Ginzberg, M. "Managing Uncertainty in MIS Implementation," Sloan Management Review (20:1), Fall 1978, pp. 23-31.
3. Balachandra, R. and Raelin, J.A. "How to Decide When to Abandon a Project," Research Management (23:4), July 1980, pp. 24-29.
4. Betts, M. "Feds Debate Handling of Failing IS Projects," Computerworld, November 2, 1992, p. 103.
5. Boehm, B.W. Software Engineering Economics, Prentice Hall, Englewood Cliffs, NJ, 1981.
6. Brockner, J. "The Escalation of Commitment to a Failing Course of Action: Toward Theoretical Progress," Academy of Management Review (17:1), January 1992, pp. 39-61.
7. Brockner, J. and Rubin, J.Z. Entrapment in Escalating Conflicts: A Social Psychological Analysis, Springer-Verlag, New York, NY, 1985.
8. Brooks, F.P. The Mythical Man-Month: Essays on Software Engineering, Addison-Wesley, Reading, MA, 1975.
9. Cohen, J. "A Coefficient of Agreement for Nominal Scales," Educational and Psychological Measurement (20:1), Spring 1960, pp. 37-46.
10. Cringely, R.X. "When Disaster Strikes IS," Forbes ASAP, August 29, 1994, pp. 60-64.
11. Ellis, V. "Audit Says DMV Ignored Warning," Los Angeles Times, August 18, 1994, pp. A3, A24.
12. Ewusi-Mensah, K. and Przasnyski, Z.H. "On Information Systems Project Abandonment: An Exploratory Study of Organizational Practices," MIS Quarterly (15:1), March 1991, pp. 67-85.
13. Garland, H. "Throwing Good Money After Bad: The Effect of Sunk Costs on the Decision to Escalate Commitment to an Ongoing Project," Journal of Applied Psychology (75:6), December 1990, pp. 728-731.
14. Garland, H., Sandefur, C.A., and Rogers, A.C. "De-Escalation of Commitment in Oil Exploration: When Sunk Costs and Negative Feedback Coincide," Journal of Applied Psychology (75:6), December 1990, pp. 721-727.
15. Gibbs, W.W. "Software's Chronic Crisis," Scientific American (271:3), September 1994, pp. 86-95.
16. Ginzberg, M.J. "Early Diagnosis of MIS Implementation Failure: Promising Results and Unanswered Questions," Management Science (27:4), April 1981, pp. 459-478.
17. Gladden, G.R. "Stop the Life-Cycle, I Want to Get Off," ACM SIGSOFT Software Engineering Notes (7:2), April 1982, pp. 35-39.
18. Hastorf, A.M. and Cantril, H. "They Saw a Game: A Case Study," Journal of Abnormal and Social Psychology (49:1), January 1954, pp. 129-134.
19. Hogarth, R.M. Judgement and Choice: The Psychology of Decision, John Wiley & Sons, New York, 1979.
20. Johnson, J. "Chaos: The Dollar Drain of IT Project Failures," Application Development Trends (2:1), January 1995, pp. 41-47
21. Kahneman, D. and Tversky, A. "The Psychology of Preferences," Scientific American (246:1), January 1982, pp. 160-173.
22. Keider, S.P. "Why Projects Fail," Datamation (20:12), December 1974, pp. 53-55.
23. Keil, M. "Escalation of Commitment in Information Systems Development: A Comparison of Three Theories," Academy of Management Best Papers Proceedings, 55th Annual Meeting, Vancouver, British Columbia, August 4-8, 1995a,pp. 348-352.
24. Keil, M. "Identifying and Preventing Runaway Systems Projects," American Programmer (8:3), March 1995b, pp. 16-22.
25. Keil, M., Beranek, P.M., and Konsynski, B.R. "Usefulness and Ease of Use: Field Study Evidence Regarding Task Considerations," Decision Support Systems (13:1), January 1995a, pp. 75-91.
26. Keil, M., Mixon, R., Saarinen, T., and Tuunainen, V. "Understanding Runaway Information Technology Projects: Results from an International Research Program Based on Escalation Theory," Journal of Management Information Systems (11:3), Winter 1995b, pp. 67-87.
27. Kemerer, C.F. "An Empirical Validation of Software Cost Estimation Models," Communications of the ACM (30:5), May 1987, pp. 416-429.
28. Kindel, S. "The Computer That Ate the Company," Financial World (161:7), March 31, 1992, pp. 96-98.
29. Kull, D. "Anatomy of a 4GL Disaster," Computer Decisions, February 11, 1986, pp. 58-65.
30. Landis, J.R. and Koch, G.G. "The Measurement of Observer Agreement for Categorical Data," Biometrics (33:1), March 1977, pp. 159-174.
31. Lyytinen, K. and Hirschheim, R. "Information Systems Failures - A Survey and Classification of the Empirical Literature," in Oxford Surveys in Information Technology (4), P. I. Zorkoczy (ed.), Oxford University Press, Oxford, 1987, pp. 257-309.
32. Markus, M.L. and Keil, M. "If We Build It, They Will Come: Designing Information Systems That Users Want To Use," Sloan Management Review (35:4), Summer 1994, pp. 11-25.
33. McFarlan, F.W. "Portfolio Approach to Information Systems," Harvard Business Review (59:5), September-October 1981, pp. 142-150.
34. McPartlin, J.P. "The Collapse of Confirm," Information Week, October 19, 1992, pp. 12-19.
35. Mehler, M. "Reining in Runaways," Information Week, December 16, 1991, pp. 20-24.
36. Meredith, J. "Project Monitoring For Early Termination," Project Management Journal (19:5), November 1988, pp. 31-38.
37. Neuman, M. and Robey, D. "A Social Process Model of User-Analyst Relationships," MIS Quarterly (16:2), June 1992, pp. 249-266.
38. Neumann, P.G. and Hoffman, R. "Risks to the Public in Computers and Related Systems: Details of BofA's Costly Computer Foul-up," Software Engineering Notes (13:2), April 1988, pp. 6-7.
39. Newman, M. and Sabherwal, R. "Determinants of Commitment to Information System Development: A Longitudinal Investigation," MIS Quarterly, 1996 (forthcoming).
40. Northcraft, G.B. and Neale, M.A. "Opportunity Costs and the Framing of Resource Allocation Decisions," Organizational Behavior and Human Decision Processes (37:3), June 1986, pp. 348-356.
41. Ropponen, J. and Lyytinen, K. "How Software Risk Management Can Improve System Development: An Explorative Study," working paper, University of Jyvaskyla, Jyvaskyla, Finland, 1993.
42. Ross, J. and Staw, B.M. "Expo86: An Escalation Prototype," Administrative Science Quarterly (31:2), June 1986, pp. 274-297.
43. Ross, J. and Staw, B.M. "Organizational Escalation and Exit: Lessons From the Shoreham Nuclear Power Plant," Academy of Management Journal (36:4), August 1993, pp. 701-732.
44. Rothfeder, J. "It's Late, Costly, Incompetent - But Try Firing a Computer System," Business Week, November 7, 1988, pp. 164-165.
45. Staw, B.M. and Ross, J. "Commitment to a Policy Decision: A Multi-Theoretical Perspective," Administrative Science Quarterly (23:1), March 1978, pp. 40-64.
46. Staw, B.M. and Ross, J. "Behavior in Escalation Situations: Antecedents, Prototypes, and Solutions," in Research in Organizational Behavior (9), B. M. Staw and L. L. Cummings (eds.), JAI Press Inc., Greenwich, CT, 1987a, pp. 39-78.
47. Staw, B.M. and Ross, J. "Knowing When to Pull the Plug," Harvard Business Review (65:2), March-April 1987b, pp. 68-74.
48. Yin, R.K. Case Study Research: Design and Methods, Sage, Beverly Hills, CA, 1984.