Author List: Keil, Mark;
MIS Quarterly, 1995, Volume 19, Issue 4, Page 421-447.
Information technology (IT) projects can fail for any number of reasons and in some cases can result in considerable financial losses for the organizations that undertake them. One pattern of failure that has been observed but seldom studied is the IT project that seems to take on a life of its own, continuing to absorb valuable resources without reaching its objective. A significant number of these projects will ultimately fail, potentially weakening a firm's competitive position while siphoning off resources that could be spent developing and implementing successful systems. The escalation literature provides a promising theoretical base for explaining this type of IT failure. Using a model of escalation based on the literature, a case study of IT project escalation is discussed and analyzed. The results suggest that escalation is promoted by a combination of project, psychological, social, and organizational factors. The managerial implications of these findings are discussed along with prescriptions for how to avoid the problem of escalation.
Keywords: escalating commitment; escalation; implementation; IS failure; Software project management
Algorithm:

List of Topics

#139 0.440 project projects failure software commitment escalation cost factors study problem resources continue prior escalate overruns taken failing troubled sunk fail
#108 0.142 model research data results study using theoretical influence findings theory support implications test collected tested based empirical empirically context paper
#185 0.124 change organizational implementation case study changes management organizations technology organization analysis successful success equilibrium radical efforts initiatives managing resistance individuals
#123 0.079 information strategy strategic technology management systems competitive executives role cio chief senior executive cios sis support organization officer position ceos