The study identified several factors as contributing to the abandonment of IS development projects. Organizational-related issues which ranged from senior management involvement to end-user participation in the project development process were the most widespread and dominant of the factors. Organizational issues were also found to influence factors dealing primarily with economic and technological matters in project development.
Get full access to this article
View all access options for this article.
References
1.
Applied Computer Research Inc. (1987). Directory of Top Computer Executives, East and West Autumn Editions.
2.
BalanchadraR., and RaelinJ.A. (1980). How to decide when to abandon a project. Research Management, 23, 24–9.
3.
BrooksF.P.Jr. (1975). The Mythical Man-month (Addison-Wesley, Reading, MA).
4.
Comptroller General (1979). Report to Congress, FGMSD-80-4.
5.
DavisG. B. (1982). Strategies for the information requirements determination. IBM Systems Journal, 4, 4–30.
6.
DeMarcoT., and ListerT. (1987). Peopleware: Productive Projects and Teams (Dorset House, New York).
7.
Ewusi-MensahK., and PrzasnyskiZ.H. (1991). On information systems project abandonment: an exploratory study of organizational practices. MIS Quaterly, 15, 67–85.
8.
Fortune 500 Companies (1988). Fortune Magazine.
9.
GladdenG.R. (1982). Stop the life-cycle, I want to get off. Software Engineering Notes, 7, 35–9.
10.
GlaserG. (1984). Managing projects in the computer industry. Computer, 17, 45–53.
11.
IvesB., and OlsonM. (1984). User involvement and MIS success: a review of research, Management Science, 30, 586–603.
12.
IvesB., HamiltonS., and DaviesG. (1980). A framework for research in computer based management information systems. Management Science, 26, 910–34.
13.
KeiderS.P. (1984). Why systems development projects fail. Journal of Information Systems Management1, 33–8.
14.
LucasH.C.Jr. (1975). Why Information Systems Fail (Columbia University Press, Irvington, NY).
15.
LyytinenK. (1987). Different perspectives on information systems: problems and solutions. ACM Computing Surveys, 19, 5–50.
16.
LyytinenK., and HirschheimR. (1987). Information systems failures – a survey and classification of the empirical literature. Oxford Surveys in Information Technology, 4, 257–309.
17.
McFarlanF.W. (1981). Portfolio approach to information systems. Harvard Business Review, 65, 68–74.
18.
MightR.J., and FischerW.A. (1985). The role of structural factors in determining project management success. IEEE Transactions Engineering Management, EM-32, 71–7.
19.
ModhaJ., GwinnettA., and BruceM. (1990). A review of information systems development methodology (ISDM) selection techniques. Omega, 18, 473–90.
20.
MorganH., and SodenJ. (1973). Understanding MIS failures. Data Base, 5, 157–71.
21.
OlleT.W., HagelsteinJ., MacdonaldL.G., RollandC., SolH.G., Van AsscheF.J.M., and Verrijn-StuartA.A. (1988). Information Systems Methodologies – A Framework for Understanding (Addison-Wesley, Reading, MA).
22.
PintoJ.K., and SlevinD.P. (1987). Critical factors in successful project implementation. IEEE Transactions Engineering Management, EM-34, 22–7.
23.
RobeyD., and FarrowD. (1982). User involvement in information systems development: a conflict model and empirical test. Management Science, 28, 73–85.
24.
SlevinJ.W., and PintoJ.K. (1986). The project implementation profile: new tool for project managers. Project Management Journal, 17, 57–70.
25.
StawB.M., and RossJ. (1987). Knowing when to pull the plug. Harvard Business Review, 65, 68–74.
26.
TurnerJ.A. (1982). Observations on the use of behavioral models in information systems research and practice. Information and Management, 5, 207–213.
27.
WhiteK.B. (1984). A diverse, balanced team approach generates vital management strategy. Data Management, 22, 31–41.
