Survey research is used to determine what kind of post-mortem appraisals companies undertake concerning their abandoned IS development projects. The data suggest that most organizations do not keep records of their failed projects and do not make any formal effort to understand what went wrong or attempt to learn from their failed projects. A learning paradigm is suggested which companies could use as a guide to undertake post-mortem analysis of their abandoned IS development projects.
Get full access to this article
View all access options for this article.
References
1.
Abdel-HamidT.K., and MadnickS.E. (1990). The elusive silver lining: how we fail to learn from software development failures. Sloan Management Review, 32(1), 39–48.
2.
BlumB.I. (1987). Improving software maintenance by learning from the past: a CASE study. Proceedings of the IEEE, 77(4), 596–606.
3.
BoddieJ. (1987). The project post-mortem. Computerworld, 7, December, 77–82.
4.
BrooksF.P.Jr. (1975). The Mythical Man-month (Addison-Wesley, Reading, MA).
5.
Comptroller General (1979). Report to Congress. FGMSD-80-4, November.
6.
Ewusi-MensahK., and PrzasnyskiZ.H. (1991). On information systems project abandonment: an exploratory study of organizational practices. MIS Quaterly, 15(1), 67–85.
7.
Ewusi-MensahK., and PrzasnyskiZ.H. (1994). Factors contributing to the abandonment of information systems development projects. Journal of Information Technology, 9(3), 185–201.
8.
GladdenG.R. (1982). Stop the life-cycle, I want to get off. Software Engineering Notes, 7(2), 35–39.
9.
GlaserG. (1984). Managing projects in the computer industry. Computer, 17, 45–53.
10.
HedbergB. (1981). How organizations learn and unlearn, in Handbook of Organizational Design, NystromP.C., and StarbuckW. H. (eds.), (Oxford University Press, Oxford), pp. 3–27.
11.
LehmanM.M. (1980). Programs, life cycles, and laws of software evolution. Proceedings of the IEEE, 68(9), 1060–1076.
12.
LyytinenK. (1987). Different perspectives on information systems: problems and solutions. ACM Computing Surveys, 19(1), 5–50.
13.
LyytinenK., and HirschheimR. (1987). Information systems failures – a survey and classification of the the empirical literature. Oxford Surveys in Information Technology, 4, 257–309.
14.
McFarlanF.W., (1981). Portfolio Approach to Information Systems. Harvard Business Review, 65, March-April, 68–74.
15.
MarchJ.G., and OlsenJ.P. (1976). Ambiguity and Choice in Organizations, (Universitetsforlaget, Bergen).
16.
SwansonE.B. (1976). The dimensions of maintenance, in Proceedings of the Second International Conference on Software Engineering, San Francisco, October, pp. 492–497.
