Re-assessing the importance of necessary or sufficient conditions of critical success factors in it project success: A fuzzy set-theoretic approach

19th European Conference on Information Systems, ECIS 2011

Volumn , Issue , 2011, Pages

  Poon, Simon K ^a   Young, Raymond ^b   Irandoost, Sepehr ^a   Land, Lesley ^c  

^a UNIVERSITY OF SYDNEY   (Australia)

^b UNIVERSITY OF CANBERRA   (Australia)

^c UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

Critical success factor; Fuzzy set analysis; Project failure; Top management support

Indexed keywords

CONVENTIONAL APPROACH; COUNTERFACTUALS; CRITICAL SUCCESS FACTOR; EMPIRICAL EVIDENCE; IT PROJECT; MULTIPLE-CASE STUDY; PROJECT EXPERIENCES; PROJECT FAILURES; PROJECT SUCCESS; SET-THEORETIC APPROACH; SUFFICIENT CONDITIONS; TOP MANAGEMENT SUPPORT;

COMPUTER SUPPORTED COOPERATIVE WORK; ENTERPRISE RESOURCE PLANNING; FUZZY SETS; INFORMATION SYSTEMS; MANAGEMENT SCIENCE; PROJECT MANAGEMENT;

RESEARCH;

EID: 84870648561     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (43)

1. HB280 (Standards Australia 2006). HB 280 how boards and senior management have governed ICT projects to succeed (or fail). Young R editor, Sydney: standards Australia.
2. Baccarini, D. (1999). "The logical framework for defining project success." Project Management Journal 30(4): 25-32.
3. Bassellier, G. and A. Pinsonneault (1998). Assessing top management support for information technologies: an new conceptualisation and measure. European conference on information systems.
4. Brandon, D. H. (1970). Management Planning for Data Processing. Princeton, New Jersey, Brandon Systems Press.
5. Checkland, P. (1981). Systems Thinking, Systems Practice. Chichester, John Wiley & Sons.
6. Clegg, C., C. Axtell, et al. (1997). "Information technology: a study of performance and the role of human and organizational factors." Ergonomics 40(9): 851-871.
7. Collins, T. and D. Bicknell (1997). Crash: ten easy ways to avoid a computer disaster. London, Simon and Schuster
8. Cooke-Davies, T. (2002). "The "real" success factors on projects." International Journal of Project Management 20: 185-190.
9. Crawford, L. (2005). "Senior management perceptions of project management competence." International Journal of Project Management 23(1): 7-16.
10. de Wit (1985). "Measurement of project success." International Journal of Project Management 6(3): 164-170.
11. Dinter, H. (1971). "Criteria for the Organizational Effectiveness of Data Processing." Data Management 9(8): 33-34.
12. Doll, W. J. (1985). "Avenues for Top Management Involvement in Successful MIS Development." MIS Quarterly 9(1): 17-35.
13. Emery, J. C. (1990). "Editors Comments - The Management Difference: a Tale of Two IS Projects." MIS Quarterly 14(1): xi-xii.
14. Falconer, D. J. and R. A. Hodgett (1999). The relationship between participation in information systems planning and development and the achievement of performance criteria in Australian commercial organisations that plan strategically for information systems. 10th Australasian Conference on Information Systems, Wellington, New Zealand.
15. Geortz, G. and B. F. Braumoeller (2000). "The methodology of necessary conditions." American Journal of political science 44: 14.
16. Izzo, J. (1987). A View of Tomorrow's System Architecture. Embattled Fortress. San Francisco, Jossey-Bass: chapter 6.
17. Jarvenpaa, S. L. and B. Ives (1991). "Executive Involvement and Participation in the Management of Information Technology." MIS Quarterly 15(2): 205-227.
18. Keil, M. (1995). "Pulling the plug: Software project management and the problem of project escalation." MIS Quarterly 19(4): 421.
19. Kraemer, K. L. and J. L. King (1986). "Computing and Public Organizations." Public Administration Review 46(6): 488-496.
20. Lederer, A. L. and A. L. Mendelow (1988). "Information systems planning: top management takes control." Business Horizons May-June: 73-78.
21. Lovallo, D. and D. Kahneman (2003). "Delusions of success: how optimism undermines executive's decisions." Harvard Business Review 81(7).
22. Lucas, H. C. (1975). Why Information Systems Fail. New York, Columbia University Press.
23. Lyytinen, K. and R. Hirschheim (1987). "Information systems failures - a survey and classification of the empirical literature." Oxford Surveys in Information Technology 4: 257-309.
24. Mähring, M. (2002). IT Project Governance. The Economic Research Institute. Stockholm, Stockholm School of Economics.
25. Markus, M. L., S. Axline, et al. (2000). "Learning from adopters' experience with ERP: problems encountered and success achieved." Journal of Information Technology 15: 245-265.
26. McGolpin, P. and J. Ward (1997). Factors Influencing the Success of Strategic Information Systems. Information Systems: an emerging discipline? J. Mingers and F. Stowell. London, McGraw-Hill: 287-327.
27. Reich, B. and Sauer, C. (2008). The Influence of Knowledge Management on Business Value in IT Projects: A Theoretical Model. International Conference on Information Systems. December 14-17, Paris.
28. Rocheleau, B. (2000). "Prescriptions for Public-Sector Information Management: a Review, Analysis and Critique." American Review of Public Administration 30(4): 414-435.
29. Sargeant, R. (2010). Creating Value in Project Management Using PRINCE2. Brisbane, Queenland Univerisity of Technology.
30. Sauer, C. (1999). Deciding the Future for IS Failures Not the Choice You Might Think. Rethinking Management Information Systems. B. Galliers and W. Currie. New York, Oxford University Press.
31. Schmidt, R., K. Lyytinen, et al. (2001). "Identifying Software Project Risks: An International Delphi Study." Journal of Management Information Systems 17(4): 5-36.
32. Schmitt, J. W. and K. A. Kozar (1978). "Management's role in information system development failures: a case study." MIS Quarterly June: 7-16.
33. Standish (1996). Unfinished voyages: a follow-up to the CHAOS report [Available at: http://www.standishgroup.com/sample-research/unfinished-voyages- 1.php] Last view 11/08/2010.
34. Standish (2003). Latest Standish group CHAOS Report [Available at: http://www.standishgroup.com/press/article.php?id=2] Last view 27/10/2010.
35. Standish (2009). The CHAOS Report, Standish Group International.
36. Strassmann, P. A. (1995). The Politics of Information Management. New Canaan, CT., Information Economics Press.
37. Thomas, J. and M. Mullaly (2008). Researching the Value of Project Management [Available at: http://www.pmi.org/Marketplace/Pages/ProductDetail. aspx?GMProduct=00101065301] Last view 27/10/2010.
38. Tichy, L. and Bascom, T. (2008). The Business End of IT Project, Mortgage Banking, 68(6): 28-35.
39. Willcocks, L., Ed. (1994). Information Management: the evaluation of information systems investments. London, Chapman & Hall.
40. Yin, R. K. (2003). Case Study Research: design and methods. Newbury Park, Sage.
41. Young, R. (2006). What is the ROI for IT Project Governance? Establishing a benchmark. 2006 IT Governance International Conference. Auckland, New Zealand.
42. Young, R. and E. Jordan (2008). "Top management support: Mantra or necessity?" International Journal of Project Management 26(7): 713 - 725.
43. Zadeh, L. A. (1965). "Fuzzy sets." Information and Control (3): 338-353.