Managing information technology project escalation and de-escalation: An approach-avoidance perspective

IEEE Transactions on Engineering Management

Volumn 56, Issue 1, 2009, Pages 76-94

  Pan, Gary ^a   Pan, Shan L ^b   Newman, Michael ^c,d  

^a SINGAPORE MANAGEMENT UNIVERSITY   (Singapore)

^b NATIONAL UNIVERSITY OF SINGAPORE   (Singapore)

^c UNIVERSITY OF MANCHESTER   (United Kingdom)

^d NORWEGIAN SCHOOL OF ECONOMICS   (Norway)

Author keywords

Approach avoidance theory; Case study; De escalation; Escalation; Process theory

Indexed keywords

PROGRAMMING THEORY;

APPROACH-AVOIDANCE THEORY; CASE STUDY; DE-ESCALATION; ESCALATION; PROCESS THEORY;

PROJECT MANAGEMENT;

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

References (58)

1. S. Alter, "Which life cycle - Work system, information systems, or software?," Commun. AIS, vol. 7, no. 17, pp. 1-54, 2001.
2. M. Bowen, "The escalation phenomenon reconsidered: Decision dilemmas or decision errors," Acad. Manage. Rev., vol. 12, no. 1, pp. 52-66, 1987.
3. J. Brockner, "The escalation of commitment to a failing course of action: Toward theoretical progress," Acad. Manage. Rev., vol. 17, no. 1, pp. 39-61, 1992.
4. E. Carmel and S. Becker, "A process model for packaged software development," IEEE Trans. Eng. Manage., vol. 42, no. 1, pp. 50-61, Feb. 1995.
5. C. Ciborra, "A critical review of the literature on the management of corporate information infrastructure," in From Control to Drift, C. Ciborra, Ed. Oxford, U.K.: Oxford Univ. Press, 2000.
6. P. Cule and D. Robey, "A dual-motor, constructive process model of organizational transition," Org. Stud., vol. 25, no. 2, pp. 229-260, 2004.
7. R. Cyert and J. March, The Behavioral Theory of the Firm. Englewood Cliffs, NJ: Prentice-Hall, 1963.
8. H. Drummond, "De-escalation in decision making: A case of a disastrous partnership," J. Manage. Stud., vol. 32, no. 3, pp. 265-281, 1995.
9. H. Drummond, Escalation in Decision-Making: The Tragedy of Taurus. Oxford, U.K.: Oxford Univ. Press, 1996.
10. H. Drummond, "What we never have, we never miss? Decision error and the risks of premature termination," J. Inf. Tech., vol. 20, no. 3, pp. 170-176, 2005.
11. K. Eisenhardt, "Building theories from case study research," Acad. Manage. Rev., vol. 14, no. 4, pp. 532-550, 1989.
12. L. Festinger, A Theory of Cognitive Dissonance. Evanston, IL: Row, 1957.
13. H. Garland, C. Sandefur, and A. Rogers, "De-escalation of commitment in oil exploration: When sunk costs and negative feedback coincide," J. Appl. Psychol., vol. 75, no. 6, pp. 721-727, 1990.
14. R. Garud and P. Karnoe, "Path creation as a process of mindful deviation," in Path Dependency and Creation, R. Garud and P. Karnoe, Eds. New York: Lawrence Erlbaum, 2001, pp. 1-38.
15. C. Gersick, "Revolutionary change theories: A multilevel exploration of the punctuated equilibrium paradigm," Acad. Manage. Rev., vol. 16, no. 1, pp. 10-36, 1991.
16. B. Hargrave and R. Johnson, "Toward an ISD acceptance model: The case of object-oriented systems development," IEEE Trans. Eng. Manage. vol. 50, no. 3, pp. 322-336, Aug. 2003.
17. R. Hirschheim, H. Klein, and M. Newman, "Information systems development as social action: Theoretical perspective and practice," Omega, vol. 19, pp. 587-608, 1991.
18. C. Iacovou and A. Dexter, "Turning around runaway information technology projects," Cal. Manage. Rev., vol. 46, no. 4, pp. 68-88, 2004.
19. M. Jensen and W. Meckling, "Theory of the firm: Managerial behaviour, agency costs, and ownership structure," J. Financial Econ., vol. 3, pp. 305-360, 1976.
20. M. Keil, "Pulling the plug: Software project management and the problem of project escalation," MIS Quart., vol. 19, no. 4, pp. 421-447, 1995.
21. M. Keil and J. Mann, "The nature and extent of it project escalation: Results from a survey of IS audit and control professionals," IS Audit Control J., vol. 1, pp. 40-48, 1997.
22. M. Keil and D. Robey, "Turning around troubled software projects: An exploratory study of the deescalation of commitment to failing courses of action," J. Manage. Inf. Syst., vol. 15, no. 4, pp. 63-87, 1999.
23. M. Keil, J. Mann, and A. Rai, "Why software projects escalate: An empirical analysis and test of four theoretical models," MIS Quart. vol. 24, no. 4, pp. 631-664, 2000.
24. M. Keil, "Software project escalation and de-escalation: What do we know?," Cutter IT J., vol. 16, no. 12, pp. 5-11, 2003.
25. H. Klein and M. Myers, "A set of principles for conducting and evaluating interpretive field studies in information systems," MIS Quart., vol. 23, no. 1, pp. 67-94, 1999.
26. A. Langley, "Strategies for theorizing from process data," Acad. Manage. Rev., vol. 24, no. 4, pp. 691-710, 1999.
27. K. Lewin, A Dynamic Theory of Personality. New York: McGraw-Hill, 1935.
28. K. Lyytinen and M. Newman, "Information systems development as punctuated socio-technical change," Working paper, Case Western Reserve Univ., Cleveland, OH, 2005.
29. K. Lyytinen and D. Robey, "Learning failure in information systems development," Inf. Syst. J., vol. 9, no. 2, pp. 85-101, 1999.
30. M. Mähring and M. Keil, "Information technology project escalation: A process model," presented at the 8th Annu. Inf. Conf. Inf. Syst. Technol., Atlanta, GA, Oct. 18-19, 2003.
31. J. Mann in The role of project escalation in explaining runaway information systems development projects: A field study, Ph.D. dissertation, Georgia State Univ., Atlanta, 1996.
32. J. Mann, "Preventing runaway IT projects: Protecting auditors from entrapment," presented at the Amer. Conf. Inf. Syst., Tampa, FL, Aug. 4-5, 2003.
33. M. Miles and A. Huberman, Qualitative Data Analysis: A Sourcebook of New Methods. Beverly Hills, CA: Sage, 1994.
34. R. Mittelstaedt, Will Your Next Mistake be Fatal? Avoiding the Chain of Mistakes That Can Destroy Your Organization. NJ: Pearson Education, 2005.
35. R. Montealegre and M. Keil, "De-escalating information technology projects: Lessons from the Denver International Airport," MIS Quart. vol. 24, no. 3, pp. 417-447, 2000.
36. M. Newman, S. Pan, and G. Pan, "Can information systems development "form" teach us anything?," Working paper, Manchester Accounting and Finance Group, Manchester, U.K., 2007.
37. M. Newman and D. Robey, "A social process model of user-analyst relationships," MIS Quart., vol. 16, no. 2, pp. 249-266, 1992.
38. M. Newman and R. Sabherwal, "Determinants of commitment to information systems development: A longitudinal investigation," MIS Quart., vol. 20, no. 1, pp. 23-54, 1996.
39. M. Newman and S. Zhu, "Process modeling information systems development: The SellCo case," in IFIP, vol. 235, Organizational Dynamics of Technology-Based Innovation: Diversifying the Research Agenda, T. McMaster, D. Wastell, E. Ferneley, and J. DeGross, Eds. Boston, MA: Springer-Verlag, 2007, pp. 63-81.
40. W. Orlikowski and J. Hofman, "An improvisational model for change management: The case of groupware technologies," Sloan Manage. Rev. vol. 38, no. 2, pp. 11-21, 1997.
41. G. Pan, S. Pan, and D. Flynn, "De-escalation of commitment to information systems projects: A process perspective," J. Strat. Inf. Syst., vol. 13, no. 3, pp. 247-270, 2004.
42. G. Pan and S. Pan, "Examining the coalition dynamics affecting IS project abandonment decision-making," Decis. Support Syst., vol. 42, no. 2, pp. 639-655, 2006.
43. G. Pan, S. Pan, M. Newman, and D. Flynn, "Escalation and de-escalation of commitment to information technology projects: A commitment transformation analysis of an E-government project," Inf. Syst. J. vol. 16, no. 1, pp. 3-21, 2006.
44. S. Pan, G. Pan, M. Newman, and D. Flynn, "Escalation and de-escalation of commitment to information systems projects: Insights from a project evaluation model," Eur. J. Oper. Res., vol. 173, no. 3, pp. 1139-1160, 2006.
45. B. Pentland, "Building process theory with narrative: From description to explanation," Acad. Manage. Rev., vol. 24, no. 4, pp. 711-724, 1999.
46. D. Robey and M. Newman, "Sequential patterns in information systems development: An application of a social process model," ACM Trans. Inf. Syst., vol. 14, no. 1, pp. 30-63, 1996.
47. J. Ross and B. Staw, "Expo 86: An escalation prototype," Admin. Sci. Quart., vol. 31, no. 2, pp. 274-297, 1986.
48. J. Ross and B. Staw, "Organizational escalation and exit: Lessons from the shoreham nuclear plant," Acad. Manage. J., vol. 36, no. 4, pp. 701-732, 1993.
49. I. Royer, "Escalation in organizations: The role of collective belief," Working paper, Univ. Paris-Dauphine, presented at the Acad.Manage. Meeting, Denver, CO, 2002.
50. J. Rubin and J. Brockner, "Factors affecting entrapment in waiting situations: The Rosencrantz and Guildenstein effect," J. Pers. Soc. Psychol., vol. 31, pp. 1054-1063, 1975.
51. R. Sabherwal and D. Robey, "An empirical taxonomy of implementation processes based on sequences of events in information system development," Org. Sci., vol. 4, no. 4, pp. 548-576, 1993.
52. R. Sabherwal, M. Sein, and G. Marakas, "Escalating commitment to information system projects: Findings from two simulated experiments," Inf. Manage., vol. 2032, pp. 1-18, 2002.
53. B. Staw and J. Ross, "Commitment to a policy decision: A multi-theoretical perspective," Admin. Sci. Quart., vol. 23, pp. 40-64, 1978.
54. B. Staw and J. Ross, "Understanding escalation situations: Antecedents, prototypes, and solutions," in Research in Organizational Behavior vol. 9, B. M. Staw and L. L. Cummings, Eds. Greenwich, CT: JAI Press, 1987, pp. 39-78.
55. C. Stubbart and R. Smalley, "The deceptive allure of stage models of strategic processes," J. Manage. Inquiry, vol. 8, no. 3, pp. 273-287, 1999.
56. A. Tiwana and M. Keil, "Functionality risk in information systems development: An empirical investigation," IEEE Trans. Eng. Manage. vol. 53, no. 3, pp. 412-425, Aug. 2006.
57. G. Whyte, "Escalating commitment to a course of action: A reinterpretation," Acad. Manage. Rev., vol. 11, no. 2, pp. 311-321, 1986.
58. R. Yin, Case Study Research: Design and Methods, 2nd ed. Newbury Park, CA: Sage, 1994.