Why software projects escalate: The importance of project management constructs

IEEE Transactions on Engineering Management

Volumn 50, Issue 3, 2003, Pages 251-261

  Keil, Mark ^a   Rai, Arun ^a   Mann, Joan Ellen Cheney ^b   Zhang, G Peter ^a  

^a GEORGIA STATE UNIVERSITY   (United States)

^b OLD DOMINION UNIVERSITY   (United States)

Author keywords

Escalation; Information technology; Project management; Software

Indexed keywords

INFORMATION TECHNOLOGY; MATHEMATICAL MODELS; REGRESSION ANALYSIS; SOFTWARE ENGINEERING;

ESCALATION; LOGISTIC REGRESSION; SOFTWARE PROJECTS;

PROJECT MANAGEMENT;

EID: 0242270696     PISSN: 00189391     EISSN: None     Source Type: Journal    
DOI: 10.1109/TEM.2003.817312     Document Type: Article

References (32)

1. B. Wysocki, "Some firms, let down by costly computers opt to 'de-engineer'," Wall Str. J., p. A1, A6, 1998.
2. S. Flowers, Software Failure: Management Failure. New York: Wiley, 1996.
3. R. L. Glass, Software Runaways. Englewood Cliffs, NJ: Prentice-Hall, 1998.
4. ____, Computing Calamities. Englewood Cliffs, NJ: Prentice-Hall, 1999.
5. K. Nash, "Top 10 disasters," Computerworld, vol. 36, pp. 1, 32-33, Oct. 30, 2000.
6. M. Mehler, "Reining in runaways," Inform. Week, pp. 20-24, Dec. 16, 1991.
7. J. A. Willbern, "Runaway computer systems," Best's Rev. (Life/Health), vol. 89, pp. 90-92, 1989.
8. J. Brockner, "The escalation of commitment to a failing course of action: Toward theoretical progress," Acad. Manage. Rev., vol. 17, pp. 39-61, 1992.
9. M. Keil, "Pulling the plug: Software project management and the problem of project escalation," MIS Quart., vol. 19, pp. 421-447, 1995.
10. 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, pp. 67-87, 1995.
11. M. Newman and R. Sabherwal, "Determinants of commitment to information systems development: A longitudinal investigation," MIS Quart., vol. 20, pp. 23-54, 1996.
12. H. Drummond, Escalation in Decision-Making: The Tragedy of Taurus. Oxford, U.K.: Oxford Univ. Press, 1996.
13. M. Keil, J. Mann, and A. Rai, "Why software projects escalate: An empirical analysis and test of four theoretical models," MIS Quart., vol. 24, pp. 631-664, 2000.
14. G. P. Zhang, M. Keil, A. Rai, and J. Mann, "Predicting information technology project escalation: A neural network approach," Eur. J. Oper. Res., 2003, to be published.
15. M. Keil and J. Flatto, "Information systems project escalation: A reinterpretation based on options theory," Account., Manage. Inform. Technol., vol. 9, pp. 115-139, 1997.
16. R. Schmidt, K. Lyytinen, M. Keil, and P. Cule, "Identifying software project risks: An international delphi study," J. Manage. Inform. Syst., vol. 14, pp. 5-36, 2001.
17. M. Keil, P. E. Cule, K. Lyytinen, and R. C. Schmidt, "A framework for identifying software project risks," Commun. ACM, vol. 41, pp. 76-83, 1998.
18. S. Alter and M. Ginzberg, "Managing uncertainty in MIS implementation," Sloan Manage. Rev., vol. 20, pp. 23-31, 1978.
19. M. M. Jones and E. McLean, "Management problems in large-scale software development projects," Ind. Manage. Rev., vol. 11, pp. 1-15, 1970.
20. D. P. Slevin and J. K. Pinto, "The project implementation profile: New tool for project managers," Proj. Manage. J., vol. 17, pp. 57-70, 1986.
21. A Guide to the Project Management Body of Knowledge. Newtown Square, PA: Project Management Institute (PMI), 2000.
22. D. D. Phan and J. Nunamaker, "The search for perfect project management," Computerworld, pp. 95-100, Sept. 26, 1988.
23. J. W. Schmitt and K. A. Kozar, "Management's role in information system development failures: A case study," MIS Quart., vol. 2, pp. 7-16, 1978.
24. R. H. Thayer, A. Pyster, and R. C. Wood, "Validating solutions to major problems in software engineering project management," Computer, vol. 15, pp. 65-77, 1982.
25. R. F. Powers and G. W. Dickson, "MIS project management: Myths, opinions, and reality," Calif. Manage. Rev., vol. 15, pp. 147-156, 1973.
26. K. Lyytinen, "Expectation failure concept and systems analysts' view of information system failures: Results of an exploratory study," Inform. Manage., vol. 14, pp. 45-56, 1988.
27. H. Barki, S. Rivard, and J. Talbot, "Toward an assessment of software development risk," J. Manage. Inform. Syst., vol. 10, pp. 203-225, 1993.
28. G. Gunawardane, "Implementing a management information system in an extremely dynamic (and somewhat hostile) environment - A case study," Interfaces, vol. 15, pp. 93-99, 1985.
29. H. L. Morgan and J. V. Soden, "Understanding MIS failures," Data Base, vol. 5, pp. 157-167, 1973.
30. T. Abdel-Hamid and S. E. Madnick, Software Project Dynamics: An Integrated Approach. Englewood Cliffs, NJ: Prentice-Hall, 1991.
31. J. Mann, The Role of Project Escalation in Explaining Runaway Information Systems Development Projects: A Field Study. Atlanta, GA: Dept. Comput. Inform. Syst., Georgia State Univ., 1996.
32. D. G. Morrison, "On the interpretation of discriminant analysis," J. Market. Res., vol. 6, pp. 156-163, 1969.