Information systems project abandonment: a stakeholder analysis

This case study reports on the experience of an organization in Singapore in implementing and eventually abandoning an electronic procurement project. By means of a stakeholder analysis, it examines stakeholders' roles in the organization's decision to abandon the software project. This study uses Freeman's stakeholder analytical framework (Freeman, R. (1984). Strategic management: a stakeholder approach. Massachusetts: Pitman) to interpret data and develop four major findings. By providing a better understanding of project stakeholders' perceptions, expectations and interrelationships during project development, this study presents researchers with a project abandonment evaluation framework that is enhanced with a stakeholder perspective. The lessons learned from the case analysis can also offer practitioners useful insights on how to manage stakeholders in information systems development projects.

[1]  Marie-Claude Boudreau,et al.  Accounting for the Contradictory Organizational Consequences of Information Technology: Theoretical Directions and Methodological Implications , 1999, Inf. Syst. Res..

[2]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

[3]  Helga Drummond,et al.  The politics of risk: trials and tribulations of the Taurus project , 1996, J. Inf. Technol..

[4]  Zbigniew H. Przasnyski,et al.  On Information Systems Project Abandonment: An Exploratory Study of Organizational Practices , 1991, MIS Q..

[5]  Effy Oz,et al.  When professional standards are lax: the CONFIRM failure and its lessons , 1994, CACM.

[6]  Kalle Lyytinen,et al.  Expectation failure concept and systems analysts' view of information system failures: Results of an exploratory study , 1988, Inf. Manag..

[7]  Zbigniew H. Przasnyski,et al.  Factors contributing to the abandonment of information systems development projects , 1994, J. Inf. Technol..

[8]  Paul Beynon-Davies,et al.  Information Systems Failure , 1998 .

[9]  Michael D. Myers,et al.  A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems , 1999, MIS Q..

[10]  Ramiro and,et al.  De-escalating Information Technology Projects: Lessons from the Denver International Airport , 2000 .

[11]  Chris Sauer,et al.  Fit, failure, and the house of horrors: toward a configurational theory of IS project failure , 1997, ICIS '97.

[12]  KeilMark,et al.  De-escalating information technology projects , 2000 .

[13]  P. Beynon-Davies,et al.  Information systems ‘failure’: the case of the London Ambulance Service's Computer Aided Despatch project , 1995 .

[14]  R. Freeman.  Strategic Management: A Stakeholder Approach , 2010 .

[15]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[16]  A. Pouloudi,et al.  Stakeholder identification in inter-organizational systems: gaining insights for drug use management systems , 1997 .

[17]  KeilMark,et al.  Identifying Software Project Risks , 2001 .

[18]  Suzanne Rivard,et al.  Toward an Assessment of Software Development Risk , 1993, J. Manag. Inf. Syst..

[19]  John J. Sosik,et al.  Why Information Systems Projects are Abandoned: A Leadership and Communication Theory and Exploratory Study , 2000, J. Comput. Inf. Syst..

[20]  R. Block.  The politics of projects , 1983 .

[21]  Michael J. Gallivan,et al.  Meaning to change: how diverse stakeholders interpret organizational communication about change initiatives , 2001 .

[22]  Zbigniew H. Przasnyski,et al.  Learning from abandoned information systems development projects , 1995, J. Inf. Technol..

[23]  Angeliki Poulymenakou,et al.  A contingency framework for the investigation of information systems failure , 1996 .

[24]  Tim Rowley.  Moving Beyond Dyadic Ties: A Network Theory of Stakeholder Influences , 1997 .

[25]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[26]  M. Lynne Markus,et al.  Power, politics, and MIS implementation , 1987, CACM.

[27]  Kalle Lyytinen,et al.  Learning failure in information systems development , 1999, Inf. Syst. J..

[28]  Nathalie N. Mitev,et al.  The business failure of knowledge-based systems: linking knowledge-based systems and information systems methodologies for strategic planning , 1994, J. Inf. Technol..

[29]  Ewusi-MensahKweku,et al.  On information systems project abandonment , 1991 .

[30]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[31]  Jeff Frooman.  Stakeholder Influence Strategies , 1999 .

[32]  Chris Sauer,et al.  Partial Abandonment as a Strategy for Avoiding Failure , 1993, Human, Organizational, and Social Dimensions of Information Systems Development.

[33]  Daniel Robey,et al.  Theories that Explain Contradiction: Accounting for the Contradictory Organizational Consequences of Information Technology , 1995, ICIS.