Making IT Project De-Escalation Happen: An Exploration into Key Roles
Given the persistent and costly problem of escalating IT projects, it is important to understand how projects can be de-escalated successfully, resulting in project turnaround if possible, or termination if necessary. Recent work suggests that the instantiation of specific roles may be central in br...
Uloženo v:
| Vydáno v: | Journal of the Association for Information Systems Ročník 9; číslo 8; s. 462 - 496 |
|---|---|
| Hlavní autoři: | , , , |
| Médium: | Journal Article |
| Jazyk: | angličtina |
| Vydáno: |
Atlanta
Association for Information Systems
01.01.2008
|
| Témata: | |
| ISSN: | 1536-9323, 1536-9323 |
| On-line přístup: | Získat plný text |
| Tagy: |
Přidat tag
Žádné tagy, Buďte první, kdo vytvoří štítek k tomuto záznamu!
|
| Shrnutí: | Given the persistent and costly problem of escalating IT projects, it is important to understand how projects can be de-escalated successfully, resulting in project turnaround if possible, or termination if necessary. Recent work suggests that the instantiation of specific roles may be central in bringing about de-escalation. However, few such roles have been identified to date and there has been no systematic study of key roles. In this paper, we therefore explore roles in IT project de-escalation using a single-case approach. Results suggest that de-escalation not only depends on the existence of particular roles, but also on role interaction. We identify seven roles that are of substantial importance in shaping whether and how de-escalation is carried out: messenger, exit sponsor, exit champion, exit blocker, exit catalyst, legitimizer, and scapegoat. Furthermore, we offer a set of propositions that capture key role interactions during de-escalation. Implications for research and practice are discussed. [PUBLICATION ABSTRACT] |
|---|---|
| Bibliografie: | SourceType-Scholarly Journals-1 ObjectType-Feature-1 content type line 14 |
| ISSN: | 1536-9323 1536-9323 |
| DOI: | 10.17705/1jais.00165 |