This is an empirical qualitative article. It attempts to study the phenomenon of project escalation in Information Systems. The methodology employed has been to choose a project that escalated, carry out an in depth analysis of the various endogenous and exogenous factors involved and identify possible reasons for such escalation. The antecedants of project esacalation thus identified can be subjected to empirical research in future.
BrocknerJ. (1992). The escalation of commitment to a failing course of action: Toward theoretical progress. Academy of Management Review, 17(1), 39–61.
2.
KeilM.DepledgeG.RaiA. (2007). Escalation: The role of problem recognition and cognitive bias. Decision Sciences, 38(3), 391–421.
3.
KeilM.TanB.C.WeiK.K.SaarinenT.TuunainenV.WassenaarA. (2000). A cross cultural study on escalation of commitment behavior in software projects. MIS Quarterly, 299–325.
4.
KielM. (1995). Pulling the plug: Software project management and the problem of project escalation. MIS Quarterly, 421–447.
5.
LeeJ.S.KielM.KasiV. (2012). The effect of an initial budget and schedule goal on software project escalation. Journal of Management Information Systems, 29(1), 53–77.
6.
StawB.M. (1981). The escalation of commitment to a course of action. Academy of Management Review, 6(4), 577–587.
7.
StawB.M. (1974). Attitudinal and behavioral consequences of changing a major organizational reward: A natural field experiment. Journal of Personality and Social Psychology, 29(6), 742–751.
8.
WhyteG. (1991). Diffusion of responsibility: Effects on the escalation tendency. Journal of Applied Psychology, 76(3), 408–415.
