Early warning signs of it project failure: the dominant Dozen

EDPACS

Volumn 35, Issue 1, 2007, Pages 1-10

  Kappelman, Leon A ^a   McKeeman, Robert ^c   Zhang, Lixuan ^b  

^a UNIVERSITY OF NORTH TEXAS   (United States)

^b School of Business   (United States)

^c NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 70349663473     PISSN: 07366981     EISSN: 19361009     Source Type: Journal    
DOI: 10.1080/07366980701238939     Document Type: Article

References (21)

1. 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.
2. Bernstein, P.L., 1996. Against the Gods: The Remarkable Story of Risk, New York: John Wiley & Sons.
3. Boehm, B.W., 1991. Software Risk Management Principles and Practices. IEEE Software, 8 (1): 32–41.
4. DeMarco, T., and Lister, T., 2003. Waltzing with Bears: Managing Risk on Software Projects Dorset House, New York
5. Havelka, D., Rajkuma, T., and Serve, P., 2004. “Early Indicators of Troubled IS Development Projects,”. Proceedings of Americas Conference on Information Systems. Aug6–82004, New York.
6. Jiang, J.J., Klein, G., and Ellis, T.S., 2002. A Measure of Software Development Risk. Project Management Journal, 33 (3): 30–41.
7. Jones, C., 2004. Software Project Management Practices: Failure Versus Success,. CrossTalk: The Journal of Defense Software Engineering, October: 5–9.
8. Jones C. (2000) You're Worth Your Weight in Gold April http://www.projectmanagement.com/pm/article.cfm?ID=5665
9. Jones, C., 1995. Patterns of Software System Failure and Success, Boston, MA: International Thomson Computer Press.
10. Keil, M., and Montealegre, R., 2001. Cutting Your Losses: Extricating Your Organization When a Big Project Goes Awry. MIT Sloan Management Review, 41 (3): 55–68.
11. Kurzweil, R., and Grossman, T.M.D., 2004. Fantastic Voyage: Live Long Enough to Live Forever, Emmaus, PA: Rodale Books.
12. May, L.J., 1998. Major Causes of Software Project Failures. CrossTalk: The Journal of Defense Software Engineering, July: 9–12.
13. McFarlan, W., 1982. Portfolio Approach to Information Systems. Journal of Systems Management, January: 12–19.
14. McKeeman, R. (2001). Early Warning Signs of Project Failure. Report for University of North Texas Information Systems Research Center.
15. 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.
16. Standish Group. (2004). CHAOS Report. West Yarmouth, MA: The Standish Group International, Inc.
17. Tiwana, A., and Keil, M., 2004. The One-Minute Risk Assessment Tool. Communications of the ACM, 47 (11): 73–77.
18. 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.
19. Ward, J. L. (2003). “Recognizing Project Warning Signs,” http://www.esi-intl.com/public/publications/122003executivewarningsigns.asp
20. Winters, F. (2002). “The Top 10 Reasons Project Fail,” http://www.gantthead.com/article.cfm?ID=147229
21. Yourdon, E., 2003. Death March: The Complete Software Developer's Guide to Surviving “Mission Impossible” Projects, 2nd, NY: Prentice Hall.