Information systems project failure: A comparative study of two countries

Journal of Global Information Management

Volumn 10, Issue 2, 2002, Pages 28-39

  Lemon, Wayne F ^a   Liebowitz, Jay ^a   Burn, Janice ^c   Hackney, Ray ^b  

^a UNIVERSITY OF MARYLAND BALTIMORE COUNTY   (United States)

^b MANCHESTER METROPOLITAN UNIVERSITY   (United Kingdom)

^c NONE

Author keywords

[No Author keywords available]

Indexed keywords

DECISION MAKING; INFORMATION MANAGEMENT; INVESTMENTS; MANAGERS; PROJECT MANAGEMENT; RISK MANAGEMENT; SOFTWARE ENGINEERING; STRATEGIC PLANNING; TELECOMMUNICATION INDUSTRY;

AUSTRALIA; EXECUTIVE MANAGEMENT LEADERSHIP; INFORMATION SYSTEMS PROJECT FAILURE; UNITED STATES;

INFORMATION TECHNOLOGY;

EID: 0041473486     PISSN: 10627375     EISSN: None     Source Type: Journal    
DOI: 10.4018/jgim.2002040103     Document Type: Article

References (22)

1. Alter, A. (1998). Software Runaways: Lessons Learned from Massive Software Project Failures. Computer World, 32 (13), 61 March.
2. Ambler, S. (1999). Comprehensive approach cuts project failures. Computing Canada, 25, 15-16. January.
3. Ash, T. (1998). Seven reasons why internet projects fail. UNIX Review's Performance Computing, 16, 15-16. October.
4. Briere, D and Heckart, C. (1999). Success through Failure. Network World, 16 (33) 32. August.
5. Burn, J,l Davison, R, and Jordan, E. (1998). The Information Society - A Cultural Fallacy? Failure & Lessons Learned in Information Technology Management: An International Journal (J. Liebowitz, ed.), 2, 219-232.
6. Brown A. and Jones M. (1988). Doomed to failure: Narratives of inevitability and conspiracy in a failed IS project. Organization Studies, 19(1), 73-88.
7. Capron, B and Kuiper, D. (1998). Increase success by avoiding failure. Manufacturing Systems, A6-A8. April.
8. Canadian Management Accounting Society (1998), "IT failures costing billions." CMA Management, 72, 37-38.
9. Glass, R. (1998). Short-Term and Long-Term Remedies for Runaway Projects: Communications of the ACM, 41 (7) July.
10. Gallupe, B, and Tan, F. B. (1999). A Research Manifesto for Global Information Management. Journal of Global Information Management, 7(3) July-Sept.
11. Glass, R. (1999). Evolving a new Theory of Project Success: Communications of the ACM, 41 (7) November.
12. James, G. (1997) IT fiascoes and how to avoid them. Datamation, 43(11):84-88. November.
13. Kim, Chung S, Kim Han Joong, and Peterson Dana (1999). Information Systems Success: Perceptions of developers in Korea. Journal of Computer Information Systems. Winter.
14. Jiang, J and Klein, G. (1999). Risks to different aspects of system success. Information & Management, 36 (5), 263-271.
15. Kapur, G. (1997). IT project management can succeed! Managing Office Technology, 42 (7).
16. 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 (4), 63-87.
17. Liebowitz, J. (1998). Information Systems: Success or failure? Journal of Computer Information Systems, 40, 17-26.
18. Mandell, M. (1998). Knowing when to quit. World Trade 12 (4), 95, April.
19. McKague, A (1998). Time has come to deal with issue of IT failures. Computing Canada, 24 (22), 9 June.
20. Schermerhorn, J. (1989). Management for Productivity. New York.
21. Sethi, V and Lederer, A. (1997). A Cross-Culture Comparison of German and US Strategic Information Systems Planning, Failure & Lessons Learned in Information Technology Management: An International Journal, (1), 233-241.
22. Vandersluis, C (1997). Plan is key to avoiding IT project failures. Computing Canada, 23 (9), 20.