Information systems project failure – analysis of causal links using interpretive structural modelling

References

• Agarwal, A., and R. Shankar. 2003. “On-line Trust Building in E-enabled Supply Chain.” Supply Chain Management: An International Journal 8: 324–334.10.1108/13598540310490080
   Web of Science ®Google Scholar
• 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
   Web of Science ®Google Scholar
• Al-Ahmad, W., K. Al-Fagih, K. Khanfar, K. Alsamara, S. Abuleil, and H. Abu-Salem. 2009. “A Taxonomy of an IT Project Failure: Root Causes.” International Management Review 5 (1): 93–104.
   Google Scholar
• 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, New York, 31–46.
   Google Scholar
• Barker, T., and M. N. Frolick. 2003. “ERP Implementation Failure: A Case Study.” Information Systems Management 20 (4): 43–49.
   Web of Science ®Google Scholar
• BBC. 2016. “Home Office Criticized over £830m ‘Failed’ Borders Scheme.” Accessed on January 1, 2016. http://www.bbc.co.uk/news/uk-34988913
   Google Scholar
• Beynon-Davies, P. 1995. “Information Systems ‘Failure’: The Case of the London Ambulance Service’s Computer Aided Despatch Project.” European Journal of Information Systems 4 (3): 171–184.10.1057/ejis.1995.20
   Web of Science ®Google Scholar
• Bronte-Stewart, M. 2009. “Risk Estimation from Technology Project Failure.” In 4th European Conference on Management of Technology, Glasgow, Scotland, September, pp. 4–6.
   Google Scholar
• 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
   Web of Science ®Google Scholar
• 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
   Web of Science ®Google Scholar
• Burnes, B. 2005. “Complexity Theories and Organizational Change.” International Journal of Management Reviews 7 (2): 73–90.10.1111/ijmr.2005.7.issue-2
   Web of Science ®Google Scholar
• 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
   Web of Science ®Google Scholar
• Chander, M., S. K. Jain, and R. Shankar. 2013. “Modeling of Information Security Management Parameters in Indian Organizations Using ISM and MICMAC Approach.” Journal of Modelling in Management 8 (2): 171–189.10.1108/JM2-10-2011-0054
   Google Scholar
• Cicmil, S., T. Williams, J. Thomas, and D. Hodgson. 2006. “Rethinking Project Management: Researching the Actuality of Projects.” International Journal of Project Management 24 (8): 675–686.
   Google Scholar
• Conboy, K. 2010. “Project Failure en Mass: A Study of Loose Budgetary Control in ISD Projects.” European Journal of Information Systems 8 (40): 1–14.
   Google Scholar
• 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.
   Google Scholar
• Crawford, L., and A. H. Nahmias. 2010. “Competencies for Managing Change.” International Journal of Project Management 28 (4): 405–412.
   Web of Science ®Google Scholar
• Cullen, A. J., and M. Taylor. 2009. “Critical Success Factors for B2B E-commerce Use within the UK NHS Pharmaceutical Supply Chain.” International Journal of Operations & Production Management 29 (11): 1156–1185.
   Web of Science ®Google Scholar
• Davis, G. B., A. S. Lee, K. R. Nickles, S. Chatterjee, R. Hartung, and Y. Wu. 1992. “Diagnosis of an Information System Failure: A Framework and Interpretive Process.” Information & Management 32 (5): 293–318.
   Web of Science ®Google Scholar
• Dwivedi, Y. K., M. Janssen, E. L. Slade, N. P. Rana, V. Weerakkody, J. Millard, J. Hidders, and D. Snijders. 2016. “Driving Innovation Through Big Open Linked Data (BOLD): Exploring Antecedents using Interpretive Structural Modelling.” Information Systems Frontiers 1–16. http://link.springer.com/article/10.1007/s10796-016-9675-5.
   Web of Science ®Google Scholar
• 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 International Working Conference on Transfer and Diffusion of IT, edited by Dwivedi, Y. K., Henriksen, H. Z., Wastell, D. and De, R., 73–88. Berlin Heidelberg: Springer.10.1007/978-3-642-38862-0
   Google Scholar
• 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
   Web of Science ®Google Scholar
• Emam, K. El, and A. Koru. 2008. “A Replicated Survey of IT Software Project Failures.” IEEE Software 25 (5): 84–90.
   Web of Science ®Google Scholar
• Ewusi-Mensah, K. 2003. Software Development Failures: Anatomy of Abandoned Projects, 45–64. Cambridge, MA: MIT Press.
   Google Scholar
• Ewusi-Mensah, K., and Z. Przasnyski. 1995. “Learning from Abandoned Information Systems Development Projects.” Journal of Information Technology 10: 3–14.10.1057/jit.1995.2
   Web of Science ®Google Scholar
• Fenech, K., and C. De Raffaele. 2013. “Overcoming ICT Project Failures – A Practical Perspective.” World Congress on Computer and Information Technology, Sousse. 10.1109/WCCIT.2013.6618719
   Google Scholar
• Fitzgerald, G., and N. R. Russo. 2005. “The Turnaround of the London Ambulance Service Computer-Aided Despatch System (LASCAD).” European Journal of Information Systems 14 (3): 244–257.10.1057/palgrave.ejis.3000541
   Web of Science ®Google Scholar
• Flowers, S. 1997. “Information Systems Failure: Identifying the Critical Failure Factors.” Failure and Lessons Learned in Information Technology Management 1 (1): 19–29.10.3727/108812897792459181
   Google Scholar
• Gauld, R. 2007. “Public Sector Information System Project Failures: Lessons from a New Zealand Hospital Organization.” Government Information Quarterly 24: 102–114.10.1016/j.giq.2006.02.010
   Web of Science ®Google Scholar
• Goulielmos, M. 2005. “Applying the Organizational Failure Diagnosis Model to the Study of Information Systems Failure.” Disaster Prevention and Management 14 (3): 362–377.10.1108/09653560510605027
   Google Scholar
• Heeks, R. 2002. “Information Systems and Developing Countries: Failure, Success, and Local Improvisations.” The Information Society 18 (2): 101–112.10.1080/01972240290075039
   Web of Science ®Google Scholar
• Hirschheim, R., and M. Newman. 1988. “Information Systems and User Resistance: Theory and Practice.” The Computer Journal 31 (5): 398–408.10.1093/comjnl/31.5.398
   Web of Science ®Google Scholar
• 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. New York: Springer.
   Google Scholar
• 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
   Google Scholar
• Jiang, J. J., G. Klein, and J. Balloun. 1998. “Perceptions of System Development Failures.” Information and Software Technology 39 (14–15): 933–937.10.1016/S0950-5849(97)00051-7
   Web of Science ®Google Scholar
• Jones, C. 2004. “Software Project Management Practices: Failure versus Success.” CrossTalk: The Journal of Defense Software Engineering 17 (10): 5–9.
   Google Scholar
• Jones, C. 2006. “Social and Technical Reasons for Software Project Failures.” CrossTalk 19 (6): 4–9.
   Google Scholar
• 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.10.1201/1078.10580530/46352.23.4.20060901/95110.4
   Web of Science ®Google Scholar
• Keider, S. 1974. “Why Projects Fail.” Datamation 20 (12): 53–55.
   Google Scholar
• 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
   Web of Science ®Google Scholar
• Kerzner, H. 2013. Project Management: A Systems Approach to Planning, Scheduling and Controlling. 5th ed. Hoboken, NJ: Wiley.
   Google Scholar
• Lehtinen, T. O. A., M. V. Mäntylä, J. Vanhanen, J. Itkonen, and C. Lassenius. 2014. “Perceived Causes of Software Project Failures – An Analysis of Their Relationships.” Information and Software Technology 56 (6): 623–643.10.1016/j.infsof.2014.01.015
   Web of Science ®Google Scholar
• 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
   Google Scholar
• Lin, Y. M., and X. Pan. 2011. “Study on Risk Scenarios of Project Failure Based on Monte-Carlo Simulation.” 2011 IEEE 18th International Conference on Industrial Engineering and Engineering Management, IE and EM 2011, Changchun, China, pp. 1291–1295.10.1109/ICIEEM.2011.6035392
   Google Scholar
• Linberg, K. R. 1999. “Software Developer Perceptions about Software Project Failure: A Case Study.” Journal of Systems and Software 49 (2–3): 177–192.10.1016/S0164-1212(99)00094-1
   Web of Science ®Google Scholar
• Luthra, S., V. Kumar, and A. Haleem. 2011. “Barriers to Implement Green Supply Chain Management in Automobile Industry Using Interpretive Structural Modelling Technique – An India Perspective.” Journal of Industrial Engineering and Management 4 (2): 231–257.
   Google Scholar
• Lyytinen, K., and R. Hirschheim. 1987. “Information Systems Failures: A Survey and Classification of the Empirical Literature.” Oxford Surveys in Information 257–309.
   Google Scholar
• 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
   Web of Science ®Google Scholar
• Mandal, A., and S. G. Deshmukh. 1994. “Vendor Selection Using Interpretive Structural Modelling (ISM).” International Journal of Operations & Production Management 14 (6): 52–59.
   Google Scholar
• 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
   Web of Science ®Google Scholar
• Meade, L. M., and J. Sarkis. 1999. “Analyzing Organizational Project Alternatives for Agile Manufacturing Processes: An Analytical Network Approach.” International Journal of Production Research 37 (2): 241–261.10.1080/002075499191751
   Web of Science ®Google Scholar
• 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–6 (2): 91–111.10.1111/ijmr.2004.5-6.issue-2
   Web of Science ®Google Scholar
• Mitev, N. N. 1996. “‘More than a Failure?’ The Computerized Reservation Systems at French Railways.” Information Technology & People 9 (4): 8–19.
   Google Scholar
• 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.
   Web of Science ®Google Scholar
• 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.
   Google Scholar
• Nelson, R. 2007. “IT Project Management: Infamous Failures, Classic Mistakes and Best Practices.” MIS Quarterly Executive 6 (2): 67–68.
   Google Scholar
• Newman, M., and R. Sabherwal. 1996. “Determinants of Commitment to Information Systems Development: A Longitudinal Investigation.” MIS Quarterly 20 (1): 23–54.10.2307/249541
   Web of Science ®Google Scholar
• 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
   Google Scholar
• 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.
   Web of Science ®Google Scholar
• 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
   Web of Science ®Google Scholar
• Perkins, T. K. 2006. “Knowledge: The Core Problem of Project Failure.” CrossTalk 19 (6): 13–15.
   Google Scholar
• Pettigrew, A., and R. Whipp. 1993. Managing Change for Competitive Success, 269–295. Oxford: Black.
   Google Scholar
• Philip, T., G. Schwabe, and K. Ewusi-Mensah. 2009. “Critical Issues of Offshore Software Development Project Failures.” In ICIS 2009 Proceedings – Thirtieth International Conference on Information Systems, Phoenix, AZ.
   Google Scholar
• 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
   Web of Science ®Google Scholar
• Poulymenakou, A., and A. Holmes. 1996. “A Contingency Framework for the Investigation of Information Systems Failure.” European Journal of Information Systems 5 (1): 34–46.10.1057/ejis.1996.10
   Web of Science ®Google Scholar
• Prosci. 2012. Best Practices in Change Management. Prosci Benchmarking Report. Loveland, CO: Prosci®.
   Google Scholar
• Purohit, J. K., M. L. Mittal, S. Mittal, and M. K. Sharma. 2016. “Interpretive Structural Modeling-based Framework for Mass Customisation Enablers: An Indian Footwear Case.” Production Planning and Control 27 (9): 1–13.
   Web of Science ®Google Scholar
• Ravi, V., and R. Shankar. 2005. “Analysis of Interactions among the Barriers of Reverse Logistics.” Technological Forecasting and Social Change 72 (8): 1011–1029.10.1016/j.techfore.2004.07.002
   Web of Science ®Google Scholar
• Rob, M. 2003. “Project Failures in Small Companies.” IEEE Software 20 (6): 94–95.10.1109/MS.2003.1241374
   Web of Science ®Google Scholar
• Rockart, J. F. 1982. “The Changing Role of the Information Systems Executive: A Critical Success Factors Perspective.” Sloan Management Review 23 (1): 3–13.
   Google Scholar
• Sage, A. P. 1977. Methodology for Large-Scale Systems. New York: McGraw-Hill College.
   Google Scholar
• Salimifard, K., M. A. Abbaszadeh, and A. Ghorbanpur. 2010. “Interpretive Structural Modeling of Critical Success Factors in Banking Process Re-engineering.” International Review of Business Research Papers 6 (2): 95–103.
   Google Scholar
• Samantra, C., S. Datta, S. Mahapatra, and B. Ranjan. 2016. “Interpretive Structural Modelling of Critical Risk Factors in Software Engineering Project.” Benchmarking: An International Journal 23 (1): 2–24.10.1108/BIJ-07-2013-0071
   Web of Science ®Google Scholar
• Sauer, C. 1993. Why Information Systems Fail: A Case Study Approach. Oxford: Alfred Waller.
   Google Scholar
• Sauer, C., G. Southon, and C. Dampney. 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, GA, USA, pp. 349–366.
   Google Scholar
• Saxena, J. P., and P. Vrat. 1992. “Scenario Building: A Critical Study of Energy Conservation in the Indian Cement Industry.” Technological Forecasting and Social Change 41 (2): 121–146.10.1016/0040-1625(92)90059-3
   Web of Science ®Google Scholar
• 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.
   Web of Science ®Google Scholar
• 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
   Google Scholar
• Sharma, H. D., and A. D. Gupta. 1995. “The Objectives of Waste Management in India: A Futures Inquiry.” Technological Forecasting and Social Change 48 (3): 285–309.10.1016/0040-1625(94)00066-6
   Web of Science ®Google Scholar
• Singh, R. K. 2011. “Developing the Framework for Coordination in Supply Chain of SMEs.” Business Process Management Journal 17 (4): 619–638.10.1108/14637151111149456
   Google Scholar
• Singh, M. D., R. Shankar, R. Narain, and A. Agarwal. 2003. “An Interpretive Structural Modeling of Knowledge Management in Engineering Industries.” Journal of Advances in Management Research 1 (1): 28–40.10.1108/97279810380000356
   Google Scholar
• Söderlund, J. 2010. “Knowledge Entrainment and Project Management: The Case of Large-scale Transformation Projects.” International Journal of Project Management 28 (2): 130–141.
   Web of Science ®Google Scholar
• 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
   Web of Science ®Google Scholar
• Standish Group. 2013. CHAOS MANIFESTO Think Big Act Small. Boston, MA. http://www.stansdishgroup.com
   Google Scholar
• Talib, F., Z. Rahman, and M. Qureshi. 2011. “Analysis of Interaction among the Barriers to Total Quality Management Implementation Using Interpretive Structural Modeling Approach.” Benchmarking: An International Journal 18 (4): 563–587.10.1108/14635771111147641
   Google Scholar
• Thakkar, J., A. Kanda, and S. G. Deshmukh. 2007. “Evaluation of Buyer–Supplier Relationships Using an Integrated Mathematical Approach of Interpretive Structural Modeling (ISM) and Graph Theoretic Matrix: The Case Study of Indian Automotive SMEs.” Journal of Manufacturing Technology Management 19 (1): 92–124.10.1108/17410380810843471
   Google Scholar
• Tukel, O. I., and W. O. Rom. 1998. “Analysis of the Characteristics of Projects in Diverse Industries.” Journal of Operations Management 16 (1): 43–61.10.1016/S0272-6963(97)00016-8
   Google Scholar
• 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
   Web of Science ®Google Scholar
• 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, Marrakech, Morocco, pp. 71–80.10.1109/RCIS.2008.4632095
   Google Scholar
• Wallace, L., M. Keil, and A. Rai. 2004. “Understanding Software Project Risk: A Cluster Analysis.” Information & Management 42 (1): 115–125.
   Web of Science ®Google Scholar
• 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
   Web of Science ®Google Scholar
• Warfield, J. N. 1974. “Developing Subsystem Matrices in Structural Modeling.” IEEE Transactions on Systems, Man, and Cybernetics 1: 74–80.10.1109/TSMC.1974.5408523
   Google Scholar
• 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.
   Google Scholar
• 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.
   Web of Science ®Google Scholar
• 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.
   Web of Science ®Google Scholar
• Winklhofer, H. 2001. “Organizational Change as a Contributing Factor to IS Failure.” Proceedings of the Hawaii International Conference on System Sciences, Maui, HI, USA.
   Google Scholar
• 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
   Google Scholar
• 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, Sydney, Australia.
   Google Scholar