Strategies for heading off is project failure

Information Systems Management

Volumn 17, Issue 2, 2000, Pages 61-69

  Cule, Paul ^a   Schmidt, Roy ^b   Lyytinen, Kalle ^c   Keil, Mark ^d  

^a MARQUETTE UNIVERSITY   (United States)

^b BRADLEY UNIVERSITY   (United States)

^c UNIVERSITY OF JYVÄSKYLÄ   (Finland)

^d GEORGIA STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

IS PROFESSIONALS; IS PROJECT FAILURES; MANAGERIAL BEHAVIOR; PROJECT SPONSORS; SOFTWARE PROJECT;

INFORMATION SYSTEMS;

EID: 85023885470     PISSN: 10580530     EISSN: None     Source Type: Journal    
DOI: 10.1201/1078/43191.17.2.20000301/31229.8     Document Type: Article

References (14)

1. Brooks, Fred P., Jr. 1987. No Silver Bullet:Essence and Accidents of Software Engineering. IEEE Computer, 20 (4):10–19.
2. Johnson, J., 1995. Chaos:The Dollar Drain of IT Project Failures. Application Development Trends, 2 (1):47
3. Keil, Mark. 1995. Pulling the Plug:Software Project Management and the Problem of Project Escalation. MIS Quarterly, 19 (4):421–447. For example, From another perspective:M. Lynn Markus & Mark Keil, 1994, “If We Build It, They Will Come:Designing Information Systems That People Will Use,” Sloan Management Review, vol. 35(4):pp. 11-25. State of California, Bureau of State Audits. California State Auditor, 1994, The Department of Motor Vehicles and the Office of Information Technology Did Not Minimize the State's Financial Risk In the Database Redevelopment Project.
4. Reimus, Byron. 1997. The IT System That Couldn't Deliver. Harvard Business Review, 75 (3):22–26. This case is discussed by various luminaries in the ensuing pages of the same issue of the HBR
5. March, J. G., and Shapira, Z., 1987. Managerial Perspectives on Risk and Risk Taking. Management Science, 33 (11) See also Z. Shapira, 1995, Risk Taking:A Managerial Perspective, New York:Russell Sage Foundation
6. Kwon, T. H., and Zmud, R. W., 1987. “ Unifying the Fragmented Models of Information Systems Implementation ”. In Critical Issues in Information Systems Research, Edited by:Boland, R. J., and Hirschheim, R. A., New York:John Wiley & Sons. For example
7. Boehm, Barry. 1989. Software Risk Management Tutorial, Washington:IEEE Computer Society Press. Barry Boehm, 1991, “Software Risk Management:Principles and Practices,” IEEE Software, vol. 8 (1) pp. 32-41
8. Brooks, Note 1
9. For example, Boehm, 1989, 1990, note 7
10. Keil, Mark, Cule, Paul, Lyytinen, Kalle, and Schmidt, Roy. 1998. A Framework for Identifying Software Project Risks. Communications of the ACM, 41 (11):76–83.
11. Humphrey, Watts S., 1995. A Discipline for Software Engineering, Reading, MA:Addison-Wesley.
12. Reimus, note 4
13. Brooks, Fred P., Jr. 1995. The Mythical Man-Month:Essays on Software Engineering, Reading, MA:Addison-Wesley.
14. California, note 3