The Effects of Sunk Cost and Project Completion on Information Technology Project Escalation

IEEE Transactions on Engineering Management

Volumn 42, Issue 4, 1995, Pages 372-381

  KeiL, Mark ^a   Truex, Duane P ^a   Mixon, Richard ^a  

^a GEORGIA STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

AVAILABILITY; COSTS; DECISION MAKING; RESEARCH AND DEVELOPMENT MANAGEMENT; RESOURCE ALLOCATION; SOCIAL ASPECTS;

PROJECT COMPLETION; SUNK COST EFFECT;

INFORMATION TECHNOLOGY;

EID: 0029403762     PISSN: 00189391     EISSN: 15580040     Source Type: Journal    
DOI: 10.1109/17.482086     Document Type: Article

References (45)

1. T. Abdel-Hamid and S. E. Madnick, Software Project Dynamics: An Integrated Approach. Englewood Cliffs, NJ: Prentice Hall, 1991.
2. T. K. Abdel-Hamid, “Understanding the ‘90% syndrome’ in software project management: A simulation-based case study,” J. Syst. and Software, vol. 8, no. 4, pp. 319-330, 1988.
3. “Investigating the cost/schedule trade-off in software development,” IEEE Software, pp. 97-105, Jan. 1990.
4. T. K. Abdel-Hamid and S. E. Madnick, “Lessons learned from modeling the dynamics of software development,” CACM, vol. 32, no. 12, pp. 1426-1438, 1989.
5. S. Alter, Decision Support Systems. Reading, MA: Addison-Wesley, 1980.
6. S. Alter and M. Ginzberg, “Managing uncertainty in MIS implementation,” Sloan Manage. Rev., vol. 20, no. 1, pp. 23-31, 1978.
7. H. R. Arkes and C. Blumer, “The psychology of sunk cost,” Organizational Behavior and Human Decision Processes, vol. 35, pp. 124-140, 1985.
8. R. H. Ashton and S. S. Kramer, “Students as surrogates in behavioral accounting research: Some evidence,” J. Account. Res., vol. 18, no. 1, pp. 1-15, 1980.
9. M. Betts, “Feds debate handling of failing IS projects,” Computerworld, Nov. 2, 1992, p. 103.
10. B. W. Boehm, Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
11. C. P. Bonini, “Capital investment under uncertainty with abandonment options,” J. Finan. and Quantitative Analysis, vol. 12, no. 1, pp. 39-54, 1977.
12. J. Brockner, “The escalation of commitment to a failing course of action: Toward theoretical progress,” Acad. Manage. Rev.,\ol. 17, no. 1, pp. 39-61, 1992.
13. F. P. Brooks, The Mythical Man-Month: Essays on Software Engineering. Reading, MA: Addison-Wesley, 1975.
14. D. E. Conlon and H. Garland, “The role of project completion information in resource allocation decisions,” Acad. Manage. J., vol. 36, no. 2, pp. 402-413, 1993.
15. T. DeMarco, Controlling Software Projects. New York: Yourdon, 1982.
16. E. A. Dyl and H. W. Long, “Abandonment value and capital budgeting: Comment,” J Finance, vol. 24, no. 1, pp. 88-95, 1969.
17. H. Garland, “Throwing good money after bad: The effect of sunk costs on the decision to escalate commitment to an ongoing project,” J. Appl. Psych., vol. 75, no. 6, pp. 728-731, 1990.
18. H. Garland and S. Newport, “Effects of absolute and relative sunk costs on the decision to persist with a course of action,” Organizational Behavior and Human Decision Processes, vol. 48, pp. 55-69, 1991.
19. H. Garland, C. A. Sandefur, and A. C. Rogers, “De-escalation of commitment in oil exploration: When sunk costs and negative feedback coincide,” J. Appl. Psych., vol. 75, no. 6, pp. 721-727, 1990.
20. J. E. Gaumnitz and D. R. Emery, “Asset growth, abandonment value and the replacement decision of like-for-like capital assets,” J Finan. and Quantitative Anal, vol. 15, no. 2, pp. 407-419 1980.
21. M. J. Ginzberg, “Early diagnosis of MIS implementation failure: Promising results and unanswered questions,” Manage. Sci., vol. 27, no. 4, pp. 459-478, 1981.
22. M. E. Gordon, L. A. Slade, and N. Schmitt, “The ‘Science of the Sophomore’ revisited: From conjecture to empiricism,” Acad. Manage. Rev., vol. 11, no. 1, pp. 191-207, 1986.
23. K. M. Howe and G. M. McCabe, “On optimal asset abandonment and replacement,” J Finan. and Quantitative Anal.,- vol. 18, no. 3, pp. 295-305, 1983.
24. C. T. Hughes and M. L. Gibson, “Students as surrogates for managers. in a decision-making environment: An experimentallstudy,” J. Manage. Inform. Syst., vol. 8, no. 2, pp. 153-166, 1991.
25. D. Kahneman and A. Tversky, “Prospect theory: An analysis of decisions under risk,” Econometrica, vol. 47, pp. 263-291, 1979.
26. D. Kahneman and A. Tversky, “Choices, values, and frames,” Amer. Psychologist, vol. 39, pp. 341-350; 1984.
27. S. P. Keider, “Why systems development projects fail,” J. Inform. Syst. Manage., vol. 1, no. 3, pp. 33-38, 1984.
28. M. Keil, “Pulling the plug: Software project management and the problem of project escalation,” MIS Quart., in press.
29. M. Keil, R. Mixon, T. Saarinen, and V. Tuunainen, “Understanding runaway information technology projects: Results from an international research program based on escalation theory,” J. Manage. Inform. Syst, vol. 11, no. 3, pp. 67-87, 1995.
30. C. F. Kemerer, “An empirical validation of software cost estimation models,” CACM, vol. 30, no. 5, pp. 416-429, 1987.
31. S. Kindel, “The computer that ate the company,” Finan. World, vol. 161, no. 7, pp. 96-98, Mar. 31, 1992.
32. F. W. McFarlan, “Portfolio approach to information systems,” Harvard Bus. Rev., vol. 59, no. 5, pp. 142-150, 1981.
33. F. W. McFarlan and J. L. McKenney, Corporate Information Systems Management: The Issues Facing Senior Executives. Homewood, IL: Irwin, 1983.
34. G. B. Northcraft and M. A. Neale, “Opportunity costs and the framing of resource allocation decisions,” Organizational Behavior and Human Decision Processes, vol. 37, no. 3, pp. 348-356, 19,86.
35. A. A. Robichek and J. C. Van Home, “Abandonment value and capital budgeting,” J. Finance, vol. 22, pp. 577-589, 1967.
36. “Abandonment value and capital budgeting: Reply,” J. Finance, vol. 24, no. 1, pp. 96-97, 1969.
37. J. Ross and B. M. Staw, “Expo86: An escalation prototype,” Admin. Sci. Quart., vol. 31, pp. 274-297, 1986.
38. “Organizational escalation and exit: Lessons from the Shoreham nuclear power plant,” Acad. Manage. J., vol. 36, no. 4, pp. 701-732, 1993.
39. J. Rothfeder, “It's late, costly, incompetent-But try firing a computer system,” Business Week, pp. 164-165, Nov. 7, 1988.
40. R. Sabherwal, M. K. Sein, and G. Marakas, WhylDo Organizations Increase Commitment to Failing Information Systems Projects?, working paper, Florida Int. Univ., Nov. 1994.
41. D. P. Slevin and J. K. Pinto, “The project implementation profile: New tool for project managers,” Proj. Manage. J., vol. 17, no. 4, pp. 57-70, 1986.
42. B. M. Staw and J. Ross, “Behavior in escalation situations: Antecedents, prototypes, and solutions,” in Research in Organizational Behavior, B. M. Staw and L. L. Cummings, Eds. Greenwich, CT: JAI, 1987, vol. 9, pp. 39-78.
43. “Understanding behavior in escalation situations,” Sci, vol. 246, pp. 216-220, 1989.
44. A. I. Teger, Too Much Invested to Quit, Pergamon Gen. Psychol. Series. New York: Pergamon, 1980.
45. A. Tversky and D. Kahneman, “The framing of decisions and the psychology of choice,” Sci., vol. 211, pp. 453-458,1981 R. W. Zmud, “Management of large software efforts,” MIS Quart., vol. 4, no. 2, pp. 45-55, 1980.