Publication Cover
Production Planning & Control
The Management of Operations
Volume 28, 2017 - Issue 9
1,478
Views
35
CrossRef citations to date
0
Altmetric
Original Articles

Mapping IS failure factors on PRINCE2® stages: an application of Interpretive Ranking Process (IRP)

, &
Pages 776-790 | Received 29 Dec 2016, Accepted 18 Mar 2017, Published online: 10 Apr 2017

References

  • Abubakre, M., M. N. Ravishankar, and C. R. Coombs. 2015. “The Role of Formal Controls in Facilitating IS Diffusion.” Information and Management 52 (5): 599–609.10.1016/j.im.2015.04.005
  • Agarwal, A., R. Shankar, and M. K. Tiwari. 2007. “Modeling Agility of Supply Chain.” Industrial Marketing Management 36 (4): 443–457.10.1016/j.indmarman.2005.12.004
  • Atkinson, R. 1999. “Project Management: Cost, Time and Quality, Two Best Guesses and a Phenomenon, Its Time to Accept Other Success Criteria.” International Journal of Project Management 17: 337–342.10.1016/S0263-7863(98)00069-6
  • Avison, D., and D. Wilson. 2002. “IT Failure and the Collapse of One. Tel.” Proceedings of the IFIP 17th World Computer Congress – TC8 Stream on Information Systems: The e-Business Challenge: 31–46.
  • Bakker, R. M., S. Boroş, P. Kenis, and L. A. G. Oerlemans. 2013. “It’s Only Temporary: Time Frame and the Dynamics of Creative Project Teams.” British Journal of Management 24 (3): 383–397.10.1111/bjom.2013.24.issue-3
  • Barker, T., and M. Frolick. 2003. “ERP Implementation Failure: A Case Study.” Information Systems Management 20 (4): 43–49.10.1201/1078/43647.20.4.20030901/77292.7
  • Bartis, E., and N. Mitev. 2008. “A Multiple Narrative Approach to Information Systems Failure: A Successful System That Failed.” European Journal of Information Systems 17 (2): 112–124.10.1057/ejis.2008.3
  • Bevilacqua, M., F. E. Ciarapica, and G. Giacchetta. 2006. “A Fuzzy-QFD Approach to Supplier Selection.” Journal of Purchasing and Supply Management 12 (1): 14–27.10.1016/j.pursup.2006.02.001
  • Beynon-Davies, P. 1995. “Information Systems Failure: The Case of the London Ambulance Services Computer Aided Despatch Project.” European Journal of Information Systems 4 (3): 171–184.10.1057/ejis.1995.20
  • Birkinshaw, J., and H. Haas. 2016. “Increase Your Return on Failure.” Harvard Business Review 94 (5): 88–93.
  • Brown, A., and M. Jones. 1998. “Doomed to Failure: Narratives of Inevitability and Conspiracy in a Failed IS Project.” Organization Studies 19 (1): 73–88.10.1177/017084069801900104
  • Bryde, D. J. 2005. “Methods for Managing Different Perspectives of Project Success.” British Journal of Management 16 (2): 119–131.10.1111/bjom.2005.16.issue-2
  • Buchanan, D., L. Fitzgerald, D. Ketley, R. Gollop, J. L. Jones, S. S. Lamont, A. Neath, and E. Whitby. 2005. “No Going Back: A Review of the Literature on Sustaining Organizational Change.” International Journal of Management Reviews 7 (3): 189–205.10.1111/ijmr.2005.7.issue-3
  • Burnes, B. 2005. “Complexity Theories and Organizational Change.” International Journal of Management Reviews 7 (2): 73–90.10.1111/ijmr.2005.7.issue-2
  • Bussen, W., and M. Myers. 1997. “Executive Information System Failure: A New Zealand Case Study.” Journal of Information Technology 12 (2): 145–153.10.1080/026839697345152
  • Chapman, R. L., and M. Corso. 2005. “From Continuous Improvement to Collaborative Innovation: The Next Challenge in Supply Chain Management.” Production Planning & Control 16 (4): 339–344.10.1080/09537280500063269
  • Cinite, I., L. E. Duxbury, and C. Higgins. 2009. “Measurement of Perceived Organizational Readiness for Change in the Public Sector.” British Journal of Management 20 (2): 265–277.10.1111/bjom.2009.20.issue-2
  • Conboy, K. 2010. “Project Failure en Mass: A Study of Loose Budgetary Control in ISD Projects.” European Journal of Information Systems 19 (3): 273–287.10.1057/ejis.2010.7
  • Conway, C. M., and M. Limayem. 2011. “You Want It When? How Temporal Dissonance in IT Workers Contributes to Project Failures.” International Conference on Information Systems 2011, Shanghai.
  • Crawford, L., P. Morris, J. Thomas, and M. Winter. 2006. “Practitioner Development: From Trained Technicians to Reflective Practitioners.” International Journal of Project Management 24 (8): 722–733.
  • Delone, W. H., and E. R. McLean. 2003. “The DeLone and McLean Model of Information Systems Success: A Ten-year Update.” Journal of Management Information Systems 19 (4): 9–30.
  • Dwivedi Y. K., K. Ravichandran, M. D. Williams, S. Miller, B. Lal, G. V. Antony, and M. Kartik. 2013. IS/IT Project Failures: A Review of the Extant Literature for Deriving a Taxonomy of Failure Factors. In: Grand Successes and Failures in IT. Public and Private Sectors. TDIT 2013. IFIP Advances in Information and Communication Technology, edited by Y. K. Dwivedi, H. Z. Henriksen, D. Wastell, and R. De’, 73–88. Vol. 402. Berlin, Heidelberg: Springer. 10.1007/978-3-642-38862-0
  • Dwivedi, Y. K., D. Wastell, S. Laumer, H. Z. Henriksen, M. D. Myers, D. Bunker, A. Elbanna, M. N. Ravishankar, and S. C. Srivastava. 2015. “Research on Information Systems Failures and Successes: Status Update and Future Directions.” Information Systems Frontiers 17 (1): 143–157.10.1007/s10796-014-9500-y
  • El Emam, K., and A. Koru. 2008. “A Replicated Survey of IT Software Project Failures.” IEEE Software 25 (5): 84–90.10.1109/MS.2008.107
  • Ewusi-Mensah, K. 2003. Software Development Failures: Anatomy of Abandoned Projects, 45–64. Cambridge, MA: The MIT Press.
  • Ewusi-Mensah, K., and Z. Przasnyski. 1995. “Learning from Abandoned Information Systems Development Projects.” Journal of Information Technology 10 (1): 3–14.10.1057/jit.1995.2
  • Faisal, M. N. 2010. “Analysing the Barriers to Corporate Social Responsibility in Supply Chains: An Interpretive Structural Modelling Approach.” International Journal of Logistics: Research and Applications 13 (3): 179–195.10.1080/13675560903264968
  • Fenech, K., and C. De Raffaele. 2013. Overcoming ICT Project Failures – A Practical Perspective. World Congress on Computer and Information Technology, Sousse.
  • Fincham, R. 2002. “Narratives of Success and Failure in Systems Development.” British Journal of Management 13 (1): 1–14.10.1111/bjom.2002.13.issue-1
  • Fitzgerald, G., and N. R. Russo. 2005. “The Turnaround of the London Ambulance Service Computer-aided Dispatch System (LASCAD).” European Journal of Information Systems 14 (3): 244–257.10.1057/palgrave.ejis.3000541
  • Flowers, S. 1997. “Information Systems Failure: Identifying the Critical Failure Factors, Failure and Lessons Learned.” Information Technology Management 1 (1): 19–29.
  • Gauld, R. 2007. “Public Sector Information System Failures: Lessons from a New Zealand Hospital Organization.” Government Information Quarterly 24: 102–114.10.1016/j.giq.2006.02.010
  • George, J. P., and V. R. Pramod. 2014. “An Interpretive Structural Model (ISM) Analysis Approach in Steel Re Rolling Mills (SRRMS).” International Journal of Research in Engineering and Technology 2 (4): 161–174.
  • Haleem, A., Sushil, M. A. Qadri, and S. Kumar. 2012. “Analysis of Critical Success Factors of World-class Manufacturing Practices: An Application of Interpretative Structural Modelling and Interpretative Ranking Process.” Production Planning & Control 23 (10–11): 722–734.10.1080/09537287.2011.642134
  • Heeks, R. 2006. “Information Systems and Developing Countries: Failure, Success, and Local Improvisations.” The Information Society 18 (2): 101–112.
  • Hiatt, J. M., and T. M. Creasey. 2012. Change Management – The People Side of Change. Loveland, CO: Prosci Inc.
  • Hornstein, H. 2015. “The Integration of Project Management and Organizational Change Management is Now a Necessity.” International Journal of Project Management 33 (2): 291–298.10.1016/j.ijproman.2014.08.005
  • Hughes, D. L., Y. K. Dwivedi, A. C. Simintiras, and N. P. Rana. 2015. Success and Failure of IS/IT Projects – A State of the Art Analysis and Future Directions. Berlin, Heidelberg: Springer.
  • Hughes, D. L., Y. K. Dwivedi, A. C. Simintiras, and N. P. Rana. 2016. “Information Systems Project Failure – Analysis of Causal Links Using Interpretive Structural Modeling.” Production Planning & Control 27 (16): 1–21.
  • Janes, F. R. 1988. “Interpretive Structural Modelling: A Methodology for Structuring Complex Issues.” Transactions of the Institute of Measurement and Control 10 (3): 145–154.10.1177/014233128801000306
  • Jones, C. 2004. “Software Project Management Practices: Failure versus Success.” The Journal of Defense Software Engineering October 17: 5–9.
  • Jones, C. 2006. “Social and Technical Reasons for Software Project Failures.” CrossTalk 19 (6): 4–9.
  • Kappelman, L. A., R. McKeeman, and L. Zhang. 2006. “Early Warning Signs of IT Project Failure: The Dominant Dozen.” Information Systems Management 23 (4): 31–36.
  • Keil, M., P. E. Cule, K. Lyytinen, and R. C. Schmidt. 1998. “A Framework for Identifying Software Project Risks.” Communications of the ACM 41 (11): 76–83.10.1145/287831.287843
  • Kerzner, H. 2013. Project Management. A Systems Approach to Planning, Scheduling and Controlling. 5th ed. Hoboken, NJ: Wiley.
  • Kerzner, H. 2015. Project Management 2.0: Leveraging Tools, Distributed Collaboration, and Metrics for Project Success. 1st ed. Hoboken, NJ: Wiley.
  • Le Roy, F., and A. S. Fernandez. 2015. “Managing Coopetitive Tensions at the Working-group Level: The Rise of the Coopetitive Project Team.” British Journal of Management 26 (4): 671–688.10.1111/1467-8551.12095
  • Lemon, W. F., J. Liebowitz, J. Burn, and R. Hackney. 2002. “Information Systems Project Failure: A Comparative Study of Two Countries.” Journal of Global Information Management 10 (2): 28–39.10.4018/JGIM
  • Leyland, M., D. Hunter, and J. Dietrich. 2009. “Integrating Change Management into Clinical Health Information Technology Project Practice.” World Congress on Privacy, Security, Trust and the Management of e-Business 2009: 89–99.10.1109/CONGRESS.2009.28
  • Luthra, S., D. Garg, and A. Haleem. 2014. “Critical Success Factors of Green Supply Chain Management for Achieving Sustainability in Indian Automobile Industry.” Production Planning & Control 26 (5): 339–362.
  • Luthra, S., V. Kumar, S. Kumar, and A. Haleem. 2011. “Barriers to Implement Green Supply Chain Management in Automobile Industry Using Interpretive Structural Modeling Technique: An Indian Perspective.” Journal of Industrial Engineering and Management 4 (2): 231–257.
  • Lyytinen, K., and R. Hirschheim. 1987. “Information Systems Failures: A Survey and Classification of the Empirical Literature.” Oxford Surveys in Information Technology 4 (1): 257–309.
  • Lyytinen, K., and D. Robey. 1999. “Learning Failure in Information Systems Development.” Information Systems Journal 9 (2): 85–101.10.1046/j.1365-2575.1999.00051.x
  • McDermott, A. M., L. Fitzgerald, and D. A. Buchanan. 2013. “Beyond Acceptance and Resistance: Entrepreneurial Change Agency Responses in Policy Implementation.” British Journal of Management 24 (S1): S93–S115.
  • Mcgrath, K. 2002. “The Golden Circle: A Way of Arguing and Acting about Technology in the London Ambulance Service.” European Journal of Information Systems 11 (4): 251–266.10.1057/palgrave.ejis.3000436
  • Michie, S., and M. West. 2004. “Managing People and Performance: An Evidence Based Framework Applied to Health Service Organizations.” International Journal of Management Reviews 5 (2): 91–111.10.1111/ijmr.2004.5-6.issue-2
  • Mitev, N. N. 1996. “More than a Failure? The Computerized Reservation Systems at French Railways.” Information Technology & People 9 (4): 8–19.10.1108/09593849610153403
  • Monteiro de Carvalho, M. 2014. “An Investigation of the Role of Communication in IT Projects.” International Journal of Operations & Production Management 34 (1): 36–64.
  • Mutch, A. 1999. “Critical Realism, Managers and Information.” British Journal of Management 10 (4): 323–333.10.1111/bjom.1999.10.issue-4
  • Nawi, H. S. A., A. A. Rahman, and O. Ibrahim. 2011. “Government’s ICT Project Failure Factors: A Revisit.” 2011 International Conference on Research and Innovation in Information Systems Kuala Lumpur: 1–6.
  • Nelson, R. 2007. “IT Project Management: Infamous Failures, Classic Mistakes and Best Practices.” MIS Quarterly Executive 6 (2): 67–68.
  • Newell, S., T. Carole, and J. Huang. 2004. “Social Capital and Knowledge Integration in ERP Project Team: The Importance of Bridging and Bonding.” British Journal of Management 15 (S1): s43–s54.10.1111/bjom.2004.15.issue-s1
  • Newman, M., and R. Sabherwal. 1996. “Determinants of Commitment to Information Systems Development: A Longitudinal Investigation.” MIS Quarterly 20: 23–54.
  • Nixon, P., M. Harrington, and D. Parker. 2012. “Leadership Performance is Significant to Project Success or Failure: A Critical Analysis.” International Journal of Productivity and Performance Management 61 (2): 204–216.10.1108/17410401211194699
  • Nudurupati, S. S., S. Tebboune, and J. Hardman. 2015. “Contemporary Performance Measurement and Management (PMM) in Digital Economies.” Production Planning & Control 27 (3): 226–235.
  • Oakland, J., and S. Tanner. 2007. “Successful Change Management.” Total Quality Management and Business Excellence 18 (1–2): 1–19.10.1080/14783360601042890
  • Pan, G., R. Hackney, and S. L. Pan. 2008. “Information Systems Implementation Failure: Insights from Prism.” International Journal of Information Management 28 (4): 259–269.10.1016/j.ijinfomgt.2007.07.001
  • Park, C., M. Keil, and J. W. Kim. 2009. “The Effect of IT Failure Impact and Personal Morality on IT Project Reporting Behavior.” IEEE Transactions on Engineering Management 56 (1): 45–60.10.1109/TEM.2008.2009794
  • Pettigrew, A., and R. Whipp. 1993. Managing Change for Competitive Success, 269–295. Oxford: Black.
  • Philip, T., G. Schwabe, and K. Ewusi-Mensah. 2009. “Critical Issues of Offshore Software Development Project Failures.” ICIS 2009 Proceedings – Thirtieth International Conference on Information Systems, Phoenix, AZ.
  • Pinto, J. K., and S. J. Mantel. 1990. “The Causes of Project Failure.” IEEE Transactions on Engineering Management 37 (4): 269–276.10.1109/17.62322
  • Prosci. 2012. Best Practices in Change Management. Prosci Benchmarking Report. Loveland, CO: Prosci®
  • Rob, M. 2003. “Project Failures in Small Companies.” IEEE Software 20 (6): 94–95.10.1109/MS.2003.1241374
  • Sandeep, M. S., and M. N. Ravishankar. 2014. “The Continuity of Underperforming ICT Projects in the Public Sector.” Information and Management 51 (6): 700–711.10.1016/j.im.2014.06.002
  • Sauer, C. 1993. Why Information Systems Fail: A Case Study Approach. Henley-on-Thames: Alfred Waller.
  • Sauer, C., G. Southon, and C. Dampne. 1997. “Fit, Failure, and the House of Horrors: Toward a Configurational Theory of IS Project Failure.” Proceedings of the Eighteenth International Conference on Information Systems ICIS Atlanta: 349–366.
  • Scarbrough, H., M. Robertson, and J. Swan. 2015. “Diffusion in the Face of Failure: The Evolution of a Management Innovation.” British Journal of Management 26 (3): 365–387.10.1111/1467-8551.12093
  • Schmidt, R., K. Lyytinen, M. Keil, and P. Cule. 2001. “Identifying Software Project Risks: An International Delphi Study.” Journal of Management Information Systems 17 (4): 5–36.
  • Scott, J., and I. Vessey. 2000. “Implementing Enterprise Resource Planning Systems: The Role of Learning from Failure.” Information Systems Frontiers 2 (2): 213–232.10.1023/A:1026504325010
  • Shahabadkar, P., S. S. Hebbal, and S. Prashant. 2012. “Deployment of Interpretive Structural Modelling Methodology in Supply Chain Management–An Overview.” International Journal of Industrial Engineering & Production Research 23 (3): 195–205.
  • Shyur, H. J., and H. S. Shih. 2006. “A Hybrid MCDM Model for Strategic Vendor Selection.” Mathematical and Computer Modelling 44 (7): 749–761.10.1016/j.mcm.2005.04.018
  • Singh, R. K., S. K. Garg, and S. G. Deshmukh. 2007. “Interpretive Structural Modelling of Factors for Improving Competitiveness of SMEs.” International Journal of Productivity and Quality Management 2 (4): 423–440.10.1504/IJPQM.2007.013336
  • Sitkin, S. B. 1992. “Learning through Failure: The Strategy of Small Losses.” Research in Organizational Behavior 14: 231–266.
  • Söderlund, J. 2011. “Pluralism in Project Management: Navigating the Crossroads of Specialization and Fragmentation.” International Journal of Management Reviews 13 (2): 153–176.10.1111/j.1468-2370.2010.00290.x
  • Standing, C., A. Guilfoyle, C. Lin, and P. E. D. Love. 2006. “The Attribution of Success and Failure in IT Projects.” Industrial Management and Data Systems 106 (8): 1148–1165.10.1108/02635570610710809
  • Standish Group. 2013. CHAOS MANIFESTO Think Big Act Small. Boston, MA. http://www.stansdishgroup.com.
  • Stensaker, I. G., and A. Langley. 2010. “Change Management Choices and Trajectories in a Multidivisional Firm.” British Journal of Management 21 (1): 7–27.10.1111/bjom.2010.21.issue-1
  • Sushil. 2009. “Interpretive Ranking Process.” Global Journal of Flexible Systems Management 10 (4): 1–10.
  • Thakkar, J., S. G. Deshmukh, A. D. Gupta, and R. Shankar. 2007. “Development of a Balanced Scorecard: An Integrated Approach of Interpretive Structural Modeling (ISM) and Analytic Network Process (ANP).” International Journal of Productivity and Performance Management 56 (1): 25–59.
  • Verner, J. M., and L. M. Abdullah. 2012. “Exploratory Case Study Research: Outsourced Project Failure.” Information and Software Technology 54 (8): 866–886.10.1016/j.infsof.2011.11.001
  • Verner, J., J. Sampson, and N. Cerpa 2008. “What Factors Lead to Software Project Failure?” Proceedings of the 2nd International Conference on Research Challenges in Information Science, RCIS 2008: 71–79.10.1109/RCIS.2008.4632095
  • Ward, J., and R. Elvin. 1999. “A New Framework for Managing IT-enabled Business Change.” Information Systems Journal 9 (3): 197–221.10.1046/j.1365-2575.1999.00059.x
  • Warne, L., and D. Hart. 1997. “Organizational Politics and Project Failure: A Case Study of a Large Public Sector Project. Failure and Lessons Learned.” Information Technology Management 1 (1): 57–65.
  • Wiegel, W., and D. Bamford. 2015. “The Role of Guanxi in Buyer–Supplier Relationships in Chinese Small-and Medium-sized Enterprises – A Resource-based Perspective.” Production Planning & Control 26 (4): 308–327.
  • Wiers, V. C. 2002. “A Case Study on the Integration of APS and ERP in a Steel Processing Plant.” Production Planning & Control 13 (6): 552–560.10.1080/09537280210160321
  • Willcocks, L. P., and W. L. Currie. 1997. “Information Technology in Public Services: Towards the Contractual Organization?” British Journal of Management 8 (s1): 107–120.10.1111/bjom.1997.8.issue-s1
  • Williams, T. 2008. “How Do Organizations Learn Lessons from Projects – And Do They?” IEEE Transactions on Engineering Management 55 (2): 248–266.10.1109/TEM.2007.912920
  • Wilson, F., J. Desmond, and H. Roberts. 1994. “Success and Failure of MRPII Implementation.” British Journal of Management 5 (3): 221–240.10.1111/bjom.1994.5.issue-3
  • Yeo, K. T. 2002. “Critical Failure Factors in Information System Projects.” International Journal of Project Management 20 (3): 241–246.10.1016/S0263-7863(01)00075-8
  • Young, R. 2005. “An Example of Relevant IS Research for Top Managers on IT Project Failure.” ACIS 2005 Proceedings – 16th Australasian Conference on Information Systems. ACIS 2005, Sydney 14.
  • Young, R., and S. Poon. 2013. “Top Management Support – Almost Always Necessary and Sometimes Sufficient for Success: Findings from a Fuzzy Set Analysis.” International Journal of Project Management 31 (7): 943–957.10.1016/j.ijproman.2012.11.013

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.