Making IT project de-escalation happen: An exploration into key roles

Journal of the Association for Information Systems

Volumn 9, Issue 8, 2008, Pages 462-496

  Mähring, Magnus ^a   Keil, Mark ^b   Mathiassen, Lars ^b,c   Pries Heje, Jan ^d  

^a STOCKHOLM SCHOOL OF ECONOMICS   (Sweden)

^b GEORGIA STATE UNIVERSITY   (United States)

^c GEORGIA STATE UNIVERSITY   (United States)

^d ROSKILDE UNIVERSITY   (Denmark)

Author keywords

Case study; De escalation; Escalation; IT projects; Role interaction; Roles

Indexed keywords

CASE-STUDIES; DE-ESCALATION; ESCALATION; IT PROJECT; ROLE; ROLE INTERACTION; SYSTEMATIC STUDY; ]+ CATALYST;

INFORMATION SYSTEMS;

EID: 57049156037     PISSN: 15583457     EISSN: 15369323     Source Type: Journal    
DOI: 10.17705/1jais.00165     Document Type: Article

References (106)

1. Aalborg University (1999). Minutes of the Supreme Governing Body of Aalborg University, April 28, section 7.a.
2. Abdel-Hamid, T.K. (1988) "Understanding the '90% Syndrome' in Software Project Management: A Simulation-Based Case Study," The Journal of Systems and Software (8) 4, pp. 319-330.
3. Amnitzboell, L. "Forskningsministeriet på Kant af loven (Ministry of Research at the Edge of the Law)," Magisterbladet, October 1999.
4. Ashforth, B.A. and R.T. Lee (1990) "Defensive Behavior in Organizations: A Preliminary Model," Human Relations (43) 7, pp. 621-648.
5. Backhouse, J. and G. Dhillon (1996) "Structures of Responsibility and Security of Information Systems," European Journal of Information Systems (5) 1, pp. 2-9.
6. Barki, H. and J. Hartwick (2001) "Interpersonal Conflict and Its Management in Information Systems Development," MIS Quarterly (25) 2, pp. 195-228.
7. Bartkus, B. (1997) "Employee Ownership as Catalyst of Organizational Change," Journal of Organizational Change Management (10) 4, pp. 331-344.
8. Baskerville, R.L. (1999) "Investigating Information Systems with Action Research," Communications of the AIS (2) 19, pp. 1-32.
9. Beath, C.M. (1991) "Supporting the Information Technology Champion," MIS Quarterly (15) 3, pp. 355-372.
10. Benbasat, I., D.K. Goldstein, and M. Mead (1987) "The Case Research Strategy in Studies of Information Systems," MIS Quarterly (11) 3, pp. 369-386.
11. Boeker, W. (1992) "Power and Managerial Dismissal: Scapegoating at the Top," Administrative Science Quarterly (37) 3, pp. 400-421.
12. Bonazzi, G. (1983) "Scapegoating in Complex Organizations: The Results of a Comparative Study of Symbolic Blame-Giving in Italian and French Public Administration," Organization Studies (4) 1, pp. 1-18.
13. Brockner, J. (1992) "The Escalation of Commitment to a Failing Course of Action: Toward Theoretical Progress," Academy of Management Review (17) 1, pp. 39-61.
14. Brooks, F.P. (1975) The Mythical Man-Month: Essays on Software Engineering. Reading, MA: Addison-Wesley.
15. Brunsson, N. (1985) The Irrational Organization: Irrationality as a Basis for Organizational Action and Change. Chichester: Wiley.
16. Bulkeley, W.M. (1996) "When Things Go Wrong: FoxMeyer Drug Took a Huge High-Tech Gamble; It Didn't Work," Wall Street Journal, November 18, pp. R25.
17. Child, J. (1972) "Organizational Structure, Environment and Performance: The Role of Strategic Choice," Sociology (6) 1, pp. 1-22.
18. Ciborra, C. and G. Lanzara (1994) "Formative Contexts and Information Technology: Understanding the Dynamics of Innovation in Organizations," Accounting, Management and Information Technologies (4) 2, pp. 61-86.
19. Clausen, R.A. "Bedre ledelse af IT-projekter ("Better Management of IT Projects")," Ingeniøren, June 25 1999, http://www.ingenioren.net.
20. Cyert, R.M. and J.G. March (1963) A Behavioral Theory of the Firm. Englewood Cliffs, NJ: Prentice-Hall.
21. Davison, R.M., M.G. Martinsons, and N. Kock (2004) "Principles of Canonical Action Research," information Systems Journal (14, pp. 65-86.
22. DeMarco, T. (1982) Controlling Software Projects. New York: Yourdon Press.
23. Djørup, C. "Ministerium slipper I VUE-Sag (the Ministry Is Being Let Off in VUE Case)," Ingeniøren, May 2000.
24. Drummond, H. (1995) "De-Escalation in Decision Making: A Case of a Disastrous Partnership," Journal of Management Studies (32)3, pp. 265-281.
25. Drummond, H. (1996) Escalation in Decision-Making: The Tragedy of Taurus. Oxford: Oxford University Press.
26. Drummond, H. (2005) "What We Never Have, We Never Miss? Decision Error and the Risks of Premature Termination," Journal of Information Technology (20) 3, pp. 170-176.
27. Eagle, J. and P.M. Newton (1981) "Scapegoating in Small Groups: An Organizational Approach," Human Relations (34) 4, pp. 283-296.
28. Edwards, B. (1996) "The Project Sponsor," in, M.J. Earl (Ed.) Information Management: The Organizational Dimension, Oxford: Oxford University Press, pp. 359-380.
29. Eisenhardt, K. (1989) "Building Theories from Case Study Research," Academy of Management Review (14) 4, pp. 532-550.
30. Fisher, J. (1999) "Improving the Usability of Information Systems: The Role of the Technical Communicator," European Journal of Information Systems (8) 4, pp. 294-303.
31. French, J.R.P. and B. Raven (1959) "The Bases of Social Power," in, D. Cartwright (Ed.) Studies in Social Power, Ann Arbor, MI: Institute for Social Research, pp. 150-167.
32. Frost, D.E. and A.J. Stahelski (1988) "The Systematic Measurement of French and Raven's Bases of Social Power in Workgroups," Journal of Applied Social Psychology (18) 5, pp. 375-389.
33. Gladwell, M. (2000) The Tipping Point: How Little Things Can Make a Big Difference. New York, NY: I Little, Brown and Company.
34. Golden, B.R. (1997) "Further Remarks on Retrospective Accounts in Organizational and Strategic Management Research," Academy of Management Journal (40) 5, pp. 1243-1252.
35. Grover, S.L. (1993) "Lying, Deceit, and Subterfuge: A Model of Dishonesty in the Workplace," Organization Science (4) 3, pp. 478-495.
36. Harder, P. (2000) Redegørelse Vedrørende visse embedsmænds forhold I forbindelse Med Videregående Uddannelsers Edb-System (VUE-projektet), (Memorandum Concerning Certain Government Policy Administrators Relations to the IT System for Further and Higher Education Institutions (VUE Project)), Copenhagen.
37. Heng, C.-S., B.C.Y. Tan, and K.-K. Wei (2003a) "De-Escalation of Commitment in Software Projects: Who Matters? What Matters?," Information & Management (41) 1, pp. 99-110.
38. Heng, C.-S., B.C.Y. Tan, and K.-K. Wei (2003b) "Willingness to Continue with Software Projects: Effects of Feedback Direction and Optimism under High and Low Accountability Conditions," Journal of the Association for Information Systems (4) 4, pp. 171-194.
39. Iivari, J. (1990) "Implementation of in-House Developed Vs Application Package Based Information Systems," ACM SIGMIS Database (21) 1, pp. 1-10.
40. Katz, D. and R.L. Kahn (1978) The Social Psychology of Organisations. New York, NY: Wiley.
41. Keil, M. (1995) "Pulling the Plug: Software Project Management and the Problem of Project Escalation," MIS Quarterly (19) 4, pp. 421-447.
42. Keil, M., G. Im, and M. Mähring (2004) "The Effects of Scapegoating on Willingness to Report Bad News on Troubled Software Projects," The Tenth Americas Conference on Information Systems, New York, NY, August 6-8, pp. 834-842.
43. Keil, M., G.P. Im, and M. Mähring (2007) "Reporting Bad News on Software Projects: The Effects of Culturally Constituted Views of Face-Saving," Information Systems Journal (17) 1, pp. 59-87.
44. Keil, M. and J. Mann (1997) "The Nature and Extent of IT Project Escalation: Results from a Survey of IS Audit and Control Professionals," IS Audit and Control Journal (1, pp. 40-48.
45. Keil, M., J. Mann, and A. Rai (2000) "Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models," MIS Quarterly (24) 4, pp. 631-664.
46. Keil, M. and R. Montealegre (2000) "Cutting Your Losses: How Executives Can Extricate Their Organizations When Big Projects Go Awry," Sloan Management Review (41) 3, pp. 55-68.
47. Keil, M., A. Rai, J. Mann, and G.P. Zhang (2003) "Why Software Projects Escalate: The Importance of Project Management Constructs," IEEE Transactions on Engineering Management (50) 3, pp. 251-261.
48. Keil, M. and D. Robey (1999) "Turning around Troubled Software Projects: An Exploratory Study of the Deescalation of Commitment to Failing Courses of Action," Journal of Management Information Systems (15) 4, pp. 63-87.
49. Keil, M. and D. Robey (2001) "Blowing the Whistle on Troubled Software Projects," Communications of the ACM (44) 4, pp. 87-93.
50. Kruglianskas, I. and H.J. Thamhain (2000) "Managing Technology-Based Projects in Multinational Environments," IEEE Transactions on Engineering Management (47) 1, pp. 55-64.
51. Lanzara, G.F. and L. Mathiassen (1988) "Intervening into System Development Ama Projects," in, G.C.V.d. Meer, T.R.G. Green, J.M. Hoc and D.M. Murray (Eds.) Working with Computers: Theory Versus Outcome, London: Academic Press, pp. 177-214.
52. Larsen, P., H.P. Baadsgaard, H. Engell, H. Mortensen, T. Pedersen, and H. Thorup (1999) Beretning fra Rigsrevisor til Folketinget om Videregående Uddannelsers Edb-System, Nr II (Report from the Auditor General of Denmark to the Danish Parliament on the IT System for Further and Higher Education Institutions, No. II), Rigsrevisor, Copenhagen, ISBN 87-7434-111-1, http://www.folketinget.dk/BAGGRUND/ statsrev/00443937.htm.
53. Lederer, A.L. and R. Nath (1991) "Managing Organizational Issues in Information Systems Development," Journal of Systems Management (42) 11, pp. 23-27, 39.
54. Lee, A.S. and R.L. Baskerville (2003) "Generalizing Generalizability in Information Systems Research," Information Systems Research (14) 3, pp. 221-243.
55. Levina, N. and E. Vaast (2005) "The Emergence of Boundary Spanning Competence in Practice: Implications for Implementation and Use of Information Systems," MIS Quarterly (29) 2, pp. 335-363.
56. Lipshitz, R. (1995) "The Road to Desert Storm," Organization Studies (16) 2, pp. 243-263.
57. Mähring, M., J. Holmström, M. Keil, and R. Montealegre (2004) "Trojan Actor-Networks and Swift Translation: Bringing Actor-Network Theory to IT Project Escalation Studies," Information Technology & People (17) 2, pp. 210-238.
58. Mähring, M. and M. Keil (2003) "Information Technology Project Escalation: A Process Model," Eighth INFORMS Conference on Information Systems & Technology (CIST), Atlanta, Georgia, October 18-19.
59. Mähring, M. and M. Keil (2008) "Information Technology Project Escalation: A Process Model," Decision Sciences (39) 2, pp. 239-272.
60. Markus, M.L. and R.I. Benjamin (1996) "Change Agentry - the Next IS Frontier," MIS Quarterly (20) 4, pp. 385-407.
61. Markus, M.L. and J.-Y. Mao (2004) "Participation in Development and Implementation - Updating an Old, Tired Concept for Today's IS Contexts," Journal of the Association for Information Systems (5) 11-12, pp. 514-544.
62. Mason, R.O., J.L. McKenney, and D.G. Copeland (1997) "An Historical Method for MIS Research: Steps and Assumptions," MIS Quarterly (21) 3, pp. 307-320.
63. Mathiassen, L., A. Munk-Madsen, and M. Jacobsen (1998) VUE-leverancerne - Et projektreview (The VUE Deliverables - a Project Review), VUE Center, Denmark.
64. McKenney, J.L., R.O. Mason, and D.C. Copeland (1995) Waves of Change: Business Evolution through Information Technology. Boston, MA: Harvard Business School Press.
65. Miles, M.B. and A.M. Huberman (1994) Qualitative Data Analysis. Beverly Hills, CA: Sage Publications.
66. Montealegre, R. and M. Keil (2000) "De-Escalating Information Technology Projects: Lessons from the Denver International Airport," MIS Quarterly (24) 3, pp. 417-447.
67. Morrison, E.W. and F.J. Milliken (2000) "Organizational Silence: A Barrier to Change and Development in a Pluralistic World," Academy of Management Review (25) 4, pp. 706-725.
68. Nathan, O. (1998) Egne veje (My Own Ways). Copenhagen: Munksgaard-Rosinante.
69. Near, J.P. and M.P. Miceli (1985) "Organizational Dissidence: The Case of Whistle-Blowing," Journal of Business Ethics) 4, pp. 1-16.
70. Newman, M. and D. Robey (1992) "A Social Process Model of Use-Analyst Relationships," MIS Quarterly (16) 2, pp. 249-266.
71. Nielsen, K.W. "Salg af VUE aflyst (the Selling of VUE Cancelled)," Ingeniøren, October 1999.
72. Ørskov, O. "Ministeriet vil saelge VUE (the Ministry Will Sell VUE)," Ingeniøren, March 1999a, http://ing.dk/artikel/122901?highlight=VUE
73. Ørskov, O. "VUE uden overblik (VUE without Oversight)," Ingeniøren, March 1999b, www.ing.dk.
74. Ørskov, O. "VUEs historie ("The History of VUE")," Ingeniøren, October 1999c, http://www.ing.dk/arkiv/1199/vuehistorie.html
75. Pan, G., S.L. Pan, M. Newman, and D. Flynn (2006a) "Escalation and De-Escalation of Commitment: A Commitment Transformation Analysis of an E-Government Project," Information Systems Journal (16) 1, pp. 3-21.
76. Pan, G.S.C., S.L. Pan, and D.J. Flynn (2004) "De-Escalation of Commitment to Information Systems Projects: A Process Perspective," Journal of Strategic Information Systems (13) 3, pp. 247-270.
77. Pan, S.L., G.S.C. Pan, M. Newman, and D. Flynn (2006b) "Escalation and De-Escalation of Commitment to Information Systems Projects: Insights from a Project Evaluation Model," European Journal of Operational Research (173) 3, pp. 1139-1160.
78. Paré, G. (2004) "Investigating Information Systems with Positivist Case Study Research," Communications of the Association of Information Systems (13, pp. 233-264.
79. Pedersen, M.R. and K. Klarskov (1999) "Vestager vil kulegrave Edb-skandale (Vestager Will Initiate a Thorough Investigation of IT Scandal),"Politikens netavis, June 8.
80. Pennings, J.M. and J. Woiceshyn (1987) "A Typology of Organizational Control and Its Metaphors," in, N. DiTomaso and S.B. Bacharach (Eds.) Research in the Sociology of Organizations, Volume 5, Vol. 5, pp. 73-104.
81. Rankin, D. and B. Golden (2002) "CEO-Directors as Catalysts for Substantive or Symbolic Change in Boardroom Self-Governance?," The Academy of Management, Denver, Colorado, August 9-14.
82. Raschke, R. and J. Smith-David (2005) "Business Process Agility," The Eleventh Americas Conference on Information Systems, Omaha, NE, August 11-14, pp. 355-360.
83. Raven, B.H., J. Schwarzwald, and M. Koslowsky (1998) "Conceptualizing and Measuring a Power/Interaction Model of Interpersonal Influence," Journal of Applied Social Psychology (28) 4, pp. 307-332.
84. Ritzaus Bureau (1999a). Skandaleramt VUE Center lukkes naeste aar (Disgraced VUE Center to Be Closed Next Year), October 14.
85. Ritzaus Bureau (1999b). Stort edb-projekt kuldsejlet (Large IT Project Capsized), January 15.
86. Robey, D., R. Welke, and D. Turk (2001) "Traditional, Iterative and Component-Based Development: A Social Analysis of Software Development Paradigms," Information Technology and Management (2) 1, pp. 53-70.
87. Rockart, J.F. and D.W. De Long (1988) Executive Support Systems: The Emergence of Top Management Computer Use. Homewood, IL: Dow Jones-Irwin.
88. Ross, J. and B.M. Staw (1986) "Expo86: An Escalation Prototype," Administrative Science Quarterly (31, pp. 274-297.
89. Ross, J. and B.M. Staw (1993) "Organizational Escalation and Exit: Lessons from the Shoreham Nuclear Power Plant," Academy of Management Journal (36) 4, pp. 701-732.
90. Royer, I. (2002) "Escalation in Organizations: The Role of Collective Belief," Paper presented at the Academy of Management Annual Meeting, Denver, Colorado, August 9-14.
91. Royer, I. (2003) "Why Bad Projects Are So Hard to Kill," Harvard Business Review (81) 2, pp. 48-56.
92. Sauer, C. (1993) Why Information Systems Fail: A Case Study Approach. Henley-on-Thames: Waller.
93. Shenhar, A.J. (1998) "From Theory to Practice: Toward a Typology of Project-Management Styles," IEEE Transactions on Engineering Management (45) 1, pp. 33-48.
94. Smith, H.J., M. Keil, and G. Depledge (2001) "Keeping Mum as the Project Goes Under: Toward an Explanatory Model," Journal of Management Information Systems (18) 2, pp. 189-227.
95. Snook, S.A. (2000) Friendly Fire: The Accidental Shootdown of U.S. Black Hawks over Northern Iraq. Princeton, NJ: Princeton University Press.
96. Somers, T.M. and K.G. Nelson (2004) "A Taxonomy of Players and Activities across the ERP Project Life Cycle," Information & Management (41) 3, pp. 257-278.
97. Staw, B.M. (1997) "Escalation of Commitment: An Update and Appraisal," in, Z. Shapira (Ed.) Organizational Decision Making, Cambridge: Cambridge University Press, pp. 191-215.
98. Staw, B.M. and J. Ross (1978) "Commitment to a Policy Decision: A Multi-Theoretical Perspective," Administrative Science Quarterly (23) 1, pp. 40-64.
99. Staw, B.M. and J. Ross (1987) "Behavior in Escalation Situations: Antecedents, Prototypes, and Solutions," in, B.M. Staw and L.L. Cummings (Eds.) Research in Organizational Behavior, Vol. 9: JAI Press Inc., pp. 39-78.
100. Stedman, C. (1999) "Failed ERP Gamble Haunts Hershey," Computerworld, November 1, pp. 1, 89.
101. Tan, B.C.Y., H.J. Smith, M. Keil, and R. Montealegre (2003) "Reporting Bad News about Software Projects: Impact of Organizational Climate and Information Asymmetry in an Individualistic and a Collectivistic Culture," IEEE Transactions on Engineering Management (50) 1, pp. 64-77.
102. Tomsho, R. (1994) "Real Dog: How Greyhound Lines Re-Engineered Itself Right into a Deep Hole," The Wall Street Journal, October 20, 1994, pp. A1-A6.
103. Valcour, P.M. (2002) "Managerial Behavior in a Multiplex Role System," Human Relations (55) 10, pp. 1163-1188.
104. Vaughan, D. (1996) The Challenger Launch Decision: Risky Technology, Culture and Deviance at NASA. Chicago, IL: University of Chicago Press.
105. Yin, R.K. (2003) Case Study Research: Design and Methods, Third edition. Thousand Oaks, CA: Sage Publications.
106. Zmud, R.W. (1980) "Management of Large Software Efforts," MIS Quarterly (4) 2, pp. 45-55.