Early Warning Signs of IT Project Failure: The Dangerous DozenFootnote¹

¹This is a reprint of an article the final and definitive form of which was published in Information Systems Management, 23(4), pp. 31–36, 2006, © Taylor & Francis. Information Systems Managementis available online at: http://www.informaworld.com.

REFERENCES

• Barki , H. , Rivard , S. and Talbot , J. 2001 . An Integrative Contingency Model of Software Project Risk Management . Journal of Management Information Systems , 17 ( 4 ) : 37 – 69 .
   Web of Science ®Google Scholar
• Bernstein , P.L. 1996 . Against the Gods: The Remarkable Story of Risk , New York : John Wiley & Sons .
   Google Scholar
• Boehm , B.W. 1991 . Software Risk Management Principles and Practices . IEEE Software , 8 ( 1 ) : 32 – 41 .
   Web of Science ®Google Scholar
• DeMarco , T. and Lister , T. 2003 . Waltzing with Bears: Managing Risk on Software Projects , New York : Dorset House .
   Google Scholar
• Havelka , D. , Rajkuma , T. and Serve , P. . Early Indicators of Troubled 13 Development Projects . Proceedings of Americas Conference on Information Systems . Aug 6–8 , New York.
   Google Scholar
• Jiang , J.J. , Klein , G. and Ellis , T.S. 2002 . A Measure of Software Development Risk . Project Management Journal , 33 ( 3 ) : 30 – 41 .
   Google Scholar
• Jones , C. 2004 . Software Project Management Practices: Failure Versus Success . CrossTalk: The Journal of Defense Software Engineering , October, 5–9
   Google Scholar
• Jones, C. (2000). You're Worth Your Weight in Gold atApril http:www.projectmanagement.com/pm/article.cfm?ID=5665
   Google Scholar
• Jones , C. 1995 . Patterns of Software System Failure and Success , Boston, MA : International Thomson Computer Press .
   Google Scholar
• Keil , M. and Montealegre , R. 2001 . Cutting Your Losses: Extricating Your Organization When a Big Project Goes Away . MIT Sloan Management Review , 41 ( 3 ) : 55 – 68 .
   Google Scholar
• Kurzweil , R. and Grossman , T.M.D. 2004 . Fantastic Voyage: Live Long Enough to Live Forever , Emmaus, PA : Rodale Books .
   Google Scholar
• May , L.J. 1998 . Major Causes of Software Project Failure . CrossTalk: The Journal of Defense Software Engineering , July, 9–12
   Google Scholar
• McFarlan , W. 1982 . Portfolio Approach to Information Systems . Journal of Systems Management , January, 12–19
   Google Scholar
• McKeeman , R. 2001 . “ Early Warning Signs of Project Failure ” . Report for University of North Texas Information Systems Research Center .
   Google Scholar
• Schmidt , R. , Lyytinen , K. , Keil , M. and Cule , P. 2001 . Identifying Software Project Risks: An International Delphi Study . Journal of Management Information Systems , 17 ( 4 ) : 5 – 36 .
   Web of Science ®Google Scholar
• Standish Group . 2004 . CHAOS Report , West Yarmouth, MA : The Standish Group International, Inc .
   Google Scholar
• Tiwana , A and Keil , M. 2004 . The One-Minute Risk Assessment Tool . Communications of the ACM , 47 ( 11 ) : 73 – 77 .
   Web of Science ®Google Scholar
• Wallace , L. , Keil , M. and Rai , A. 2004 . How Software Project Risk Affects Project Performance: An Investigation of the Dimensions of Risk and an Exploratory Model . Decision Science , 35 ( 2 ) : 289 – 321 . &
   Web of Science ®Google Scholar
• Ward, J. L. (2003). “Recognizing Project Warning Signs,” available online at http:www.esi-intl.com/public/publications/122003 executivewarningsigns.asp
   Google Scholar
• Winters, F. (2002). “The Top 10 Reasons Project Fail,” available online at http:www.gantthead.com/article.cfm?ID=147229
   Google Scholar
• Yourdon , E. 2003 . Death March: The Complete Software Developer's Guide to Surviving “Mission Impossible” Projects , 2nd Prentice Hall, NY
   Google Scholar