Towards a stakeholder analysis of information systems development project abandonment

This study adopts a stakeholder analysis to examine stakeholders’ roles and contributions in influencing organizational decisions to abandon information systems (IS) development projects. To do so, we adapted from Freeman’s (1984) work and developed a theoretical assessment framework to organize and interpret data, and define avenues (five propositions were proposed) for further research into IS project abandonment. By providing a better understanding of the project stakeholders’ perception, expectations and their interrelationship, this study provides practitioners with useful insights on how to manage stakeholders in IS development projects. Our contribution lies in the development of a project abandonment review model that adds a stakeholder perspective.

[1]  Tom DeMarco,et al.  A defined process for project post mortem review , 1996, IEEE Software.

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

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

[4]  Wanda J. Orlikowski,et al.  Technological frames: making sense of information technology in organizations , 1994, TOIS.

[5]  Robert E. Tarjan,et al.  Culturally-induced information impactedness: a prescription for failure in software ventures , 1998, Proceedings of the Thirty-First Hawaii International Conference on System Sciences.

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

[7]  Daniel Robey,et al.  A Social Process Model of User-Analyst Relationships , 1992, MIS Q..

[8]  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..

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

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

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

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

[13]  Paul B. Cragg,et al.  Factors contributing to the success of customer oriented interorganizational systems , 1995, J. Strateg. Inf. Syst..

[14]  A. Bryman Social Research Methods , 2001 .

[15]  Daniel Robey,et al.  User Involvement in Information System Development: A Conflict Model and Empirical Test , 1982 .

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

[17]  Michael D. Myers,et al.  Executive information system failure: a New Zealand case study , 1997, PACIS.

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

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

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

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

[22]  Andrew D. Brown,et al.  Doomed to Failure: Narratives of Inevitability and Conspiracy in a Failed IS Project , 1998 .

[23]  Michael Newman,et al.  Information system design, stress and organisational change in the ambulance services: A tale of two cities , 1996 .

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

[25]  Z. H. Przasnyski,et al.  Learning from Abandoned Information Systems Development Projects , 1995 .

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

[27]  M. Patton,et al.  Qualitative evaluation and research methods , 1992 .

[28]  Chris Sauer,et al.  Is there a place for department stores on the Internet? Lessons from an abandoned pilot , 1999, J. Inf. Technol..

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

[30]  DeMarcoTom,et al.  A Defined Process For Project Postmortem Review , 1996 .

[31]  Albert L. Lederer,et al.  The Impact of the Environment on the Management of Information Systems , 1990, Inf. Syst. Res..

[32]  Patricia J. Guinan,et al.  Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach , 1998, Inf. Syst. Res..

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

[34]  Wanda J. Orlikowski,et al.  Studying Information Technology in Organizations: Research Approaches and Assumptions , 1991, Inf. Syst. Res..

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

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

[37]  Kuldeep Kumar,et al.  Post implementation evaluation of computer-based information systems: current practices , 1990, Commun. ACM.

[38]  Jan Weglarz,et al.  Interpreting Information Systems in Organizations , 1993 .

[39]  Grant T. Savage,et al.  Stakeholder analysis for multi‐sector innovations , 2002 .

[40]  Geoff Walsham,et al.  Interpreting Information Systems in Organizations , 1993 .

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