loading...
Understanding the Nature and Extent of IS Project Escalation: Results from a Survey of IS Audit and Control Professionals
Maui, Hawaii January 03-January 06
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/HICSS.1997.66158230th Hawaii International Conference ...
 This Article 
 
PURCHASE ARTICLE: $0
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Mark Keil, Georgia State University
Joan Mann, Old Dominion University
Runaway IS projects continue to be reported regularly in the trade press, but surprisingly little is known about: (1) how widespread the problem actually is, and (2) the factors that cause it to occur. Many runaway IS projects appear to represent what can be described as escalating commitment to a failing course of action. A survey of Information Systems Audit and Control Association (ISACA) members was undertaken in order to understand more about the prevalence of IS project escalation and the factors that cause it. The results are startling: Escalation occurs in 30-40% of IS projects and projects that escalate are rarely completed and implemented successfully. What is more, escalation appears to be caused by a combination of project management as well as psychological, social, and organizational factors.
Citation:
Mark Keil, Joan Mann, "Understanding the Nature and Extent of IS Project Escalation: Results from a Survey of IS Audit and Control Professionals," hicss, vol. 3, pp.139, 30th Hawaii International Conference on System Sciences (HICSS) Volume 3: Information System Track-Organizational Systems and Technology, 1997
Usage of this product signifies your acceptance of the Terms of Use.