Early Indicators of Troubled IS Development Projects

10th Americas Conference on Information Systems, AMCIS 2004

Volumn , Issue , 2004, Pages 828-833

  Havelka, Douglas ^a   Serve, Patrick ^a   Rajkumar, T M ^a  

^a MIAMI UNIVERSITY   (United States)

Author keywords

early detection; field study; Systems development; troubled projects

Indexed keywords

INFORMATION SYSTEMS; INFORMATION USE; PROJECT MANAGEMENT;

BUSINESS MANAGERS; CORRECTIVE ACTIONS; DEVELOPMENT PROGRAMMES; EARLY DETECTION; EARLY INDICATORS; FIELD STUDIES; INFORMATION SYSTEMS DEVELOPMENT PROJECTS; IS DEVELOPMENT; SYSTEM DEVELOPMENT; TROUBLED PROJECT;

MANAGERS;

EID: 85139065861     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (6)

1. Feldman, J. (2001). Project Recovery: Saving Troubled Projects. Information Strategy 17, 6-11.
2. Glass, R. L. (1998). Software Runaways. Prentice-Hall, Upper Saddle River, NJ.
3. Keil, M., and Robey, D. (1999). Turning around troubled software projects: an exploratory study of the deescalation of commitment to failing courses of action. Journal of Management Information Systems 15, 63.
4. Partlow, J., and Wynes, D. (2002). Teamwork puts a troubled project back on track: a case study in relationship building. Information Strategy-The Executive's Journal 18, 12-22.
5. Tarek, A. M., and Madnick, S. (1990). The elusive silver lining: How we fail to learn from project management failures. Sloan Management Review, 39-49.
6. Whittaker, B. (1999). What went wrong? Unsuccessful information technology projects. Information Management and Computer Security 7, 23-29.