Addressing a critical success factor for software projects: A multi-round delphi study of TSP

International Journal of Physical Sciences

Volumn 6, Issue 5, 2011, Pages 1213-1232

  Nasir, Mohd Hairul Nizam Md ^a   Sahibuddin, Shamsul ^b  

^a UNIVERSITY OF MALAYA   (Malaysia)

^b UNIVERSITI TEKNOLOGI MALAYSIA   (Malaysia)

Author keywords

Critical success factors; Delphi study; Project management; Software development; Software process improvement; Team software process (TSP)

Indexed keywords

EID: 79956192952     PISSN: 19921950     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (93)

1. Adler M, Ziglio E (1996). Gazing into the Oracle: The Delphi Method and its Application to Social Policy and Public Health, Jessica Kingsley Publishers.
2. Ariane 501 Inquiry Board. (1996). Ariane 5: Flight 501 Failure. Report by the Inquiry Board. Paris: Ariane 501 Inquiry Board. Available at: http://www.di.unito.it/~damiani/ariane5rep.html.
3. Babbie ER (2010). The Practice of Social Research, 10th ed., Thomson Learning Inc.
4. Baccarini D, Salm G, Love PED (2004). Management of Risks in Information Technology Projects. Ind. Manage. Data Syst., 104(4): 286-295.
5. Battle ED (2009). Using TSP at the MSG Level. Proceedings of the TSP Symposium 2009, Louisiana, Software Engineering Institute.
6. Bayo ML, Ekene NS, Kenneth AC, Idowu SF (2007). Software development: An attainable goal for sustainable economic growth in developing nations: The Nigeria experience. Int. J. Phys. Sci., 2(12): 318-323.
7. Belassi W, Tukel OI (1996). A New Framework for Determining Critical Success/Failure Factors in Projects. Int. J. Proj. Manage,. 14(3): 141-151.
8. Beynon-Davies P (1999). Human Error and Information Systems Failure: The Case of the London Ambulance Service Computer-Aided Despatch System Project. Interact. Comp., 11(6): 669-720.
9. Boehm BW (1991). Software Risk Management: Principles and Practices. IEEE Softw,. 8(1): 32-41.
10. Brooks FP (1995). The Mythical Man-Month: Essays on Software Engineering, Anniversary ed., Addison-Wesley.
11. Callegari D, Bastos R (2007). Project Management and Software Development Processes: Integrating RUP and PMBOK. Proceedings International Conference Systems Engineering and Modeling.
12. Charette RN (2005). Why Software Fails. IEEE Spectrum, 42(9): 42-49.
13. Clegg C, Axtella C, Damodaran L, Farbey B, Hull R, Llyod-Joness R, Nicholls J, Sells R, Tomlinson C (1997). Information Technology: A Study of Performance and the Role of Organizational Factors. Ergonomics, 40(9): 851-857.
14. Cohen J (1960). A coefficient of agreement for nominal scales. Educ. Psychol. Meas., 20(1): 37-46.
15. Cooke-Davies TJ, Arzymanow A (2002). The maturity of project management in different industries: An investigation into variations between project management models. Int. J. Proj. Manage., 21(6): 471-478.
16. Cramer D (1997). Basics Statistics for Social Research, Routledge.
17. Davis N, Barbara S (2009). Experiences Using the Team Software Process at Adobe Systems. Proceedings of the TSP Symposium 2009, Louisiana, Software Engineering Institute.
18. Davis N, Mullaney J (2003). The Team Software Process in Practice: A Summary of Recent Results. Technical Report, Software Engineering Institute.
19. Delbecq AL, Van de Ven AH, Gustafson DH (1975). Group techniques for program planning: A guide to nominal group and Delphi processes, Scott, Foresman and Company.
20. Drummond H (1998). Riding a Tiger: Some Lessons of Taurus. Manage. Decis., 36(3): 141-146.
21. Dvir D, Lipovetsky S, Shenhar A, Tishler A (1998). In Search of Project Classification: A Non-Universal Approach to Project Success Factors. Res. Pol., 27(9): 915-935.
22. Ewusi-Mensah K (1997). Critical Issues in Abandoned Information Systems Development Projects. Commun. ACM. 40(9): 74-80.
23. Fairly ER (2009). Managing and Leading Software Projects, Wiley-IEEE Computer Society Press.
24. Fortune J, White D (2006). Framing of Project Critical Success Factors by a Systems Model. Int. J. Proj. Manage., 24(1): 53-65.
25. Galin D (2004). Software Quality Assurance-From Theory to Implementation, Addison-Wesley.
26. Glaser J (2004). Management's Role in IT Project Failures. Healthc. Finance Manage., 58(10): 90-92.
27. Gray CF, Larson EW (2008). Project Management: The Managerial Process, 4th ed., Irwin/McGraw-Hill.
28. Gustafson DH, Shukla RK, Delbecq A, Walster GW (1973). A comparison study of differences in subjective likelihood estimates made by individuals, interacting groups, Delphi groups and nominal groups. Organ. Behav. Hum. Perf., 9(2): 280-291.
29. Hakim C (1987). Research Design: Strategies and Choices in the Design of Social Research, Allen and Unwin.
30. Hass KB (2007). The Blending of Traditional and Agile Project Management. PM World Today, 9(5): 1-8.
31. Holsti OR (1969). Content Analysis for the Social Sciences and Humanities, Addison-Wesley.
32. Humphrey WS (1998). Three Dimensions of Process Improvement. Part III: The Team Process. CrossTalk J. Defense Softw. Eng., 11(4): 14-17.
33. Humphrey WS (2000). Introduction to Team Software Process, Addison-Wesley.
34. Humphrey WS (2002). Relating the Team Software Process SM (TSP SM) to the Capability Maturity Model for the Software (SW-CMM). Technical Report, Software Engineering Institute.
35. Humphrey WS (2005). Why Big Software Project Fail: The 12 Key Questions. CrossTalk J. Defense Software Eng., 18(3): 25-29.
36. Humphrey WS (2006). TSP: Coaching Development Teams, Addison-Wesley.
37. Ibbs CW, Kwak YH (2000). Assessing Project Management Maturity. Proj. Manage. J., 31(1): 32-43.
38. Jain M (2008). Delivering Successful Projects with TSP and Six Sigma: A Practical Guide to Implementing Team Software Process, Auerbach Publications.
39. Jenkins M (2005). Combining Multiple Models to Develop a Software Project Management Methodology. Proceedings International Conference Software Engineering and Applications, USA. ACTA Press.
40. Jiang J, Klein G (2000). Software Development Risks to Project Effectiveness. J. Syst. Softw., 52(1): 3-10.
41. Jiang J, Klein G, Discenza R (2001). Information System Success an Impacted by Risks and Development Strategies. IEEE T. Eng. Manage., 48(1): 46-55.
42. Jiang JJ, Klein G, Balloun JK, Crampton SM (1999). System Analyst' Orientation and Perceptions of Systems Failure. Inf. Softw. Tech., 41(2): 101-106.
43. Jones C (1995). Patterns of Large Software Systems: failure and Success. Computer, 28(3): 86-87.
44. Jones C (1996). Our Worst Current Development Practices. IEEE Softw., 13(2): 102-104.
45. Jones C (2006). Social and Technical Reasons for Software Project Failures. CrossTalk J. Defense Software Eng., 19(6): 4-9.
46. Kappelman LA, Mckeeman R, Zhang L (2006). Early Warning Signs of IT Project Failure - The Dominant Dozen. Inf. Syst. Manage., 23(4): 31-36.
47. Keil M, Tiwana A, Bush A (2002). Reconciling User and Project Manager Perceptions of IT Project Risk: A Delphi Study. Inf. Syst. J., 12(2): 103-119.
48. Lam SSY, Petri KL, Smith AE (2000). Prediction and optimization of a ceramic casting process using a hierarchical hybrid system of neural networks and fuzzy logic. IIE Trans., 32(1): 83-92.
49. Landis J, Koch G (1977). Measurement of observer agreement for categorical data. Biometrics, 33: 159-174.
50. Leveson NG (2004). The Role of Software in Spacecraft Accidents. J. Spacecraft Rockets, 41(4): 564-575.
51. Lloyd S, Simpson A (2005). Project Management in Multi-Disciplinary Collaborative Research. Proceedings of the International Professional Communication Conference (IPCC 2005), Ireland. IEEE, pp. 602-611.
52. Mahaney RC, Lederer AL (2003). Information System Project Management: An Agency Theory Interpretation. J. Syst. Softw., 68(1): 1-9.
53. May LJ (1998). Major Causes of Software Project Failure. CrossTalk J. Defense Softw. Eng., 11(7): 1-7.
54. Nambisan S, Agarwal R, Tanniru M (1999). Organisational mechanisms for enhancing user innovation in information technology. MIS Q., 23(8): 365-395.
55. Nasir MHNM, Sahibuddin S (2011). Critical Success Factors for Software Projects: A Comparative Study. Sci. Res. Essays, In Press.
56. Nawrocki J, Olek L, Jasinski M, Paliswiat B, Walter B, Piertrzak B, Godek P (2006). Balancing Agility and Discipline with XPrince. Lecture Notes in Comput. Sci., 3943: 266-277.
57. Nuseibeh B (1997). Ariane 5- Who Dunnit? IEEE Softw., 14(3): 15-16.
58. OGC Best Practice. (2005). Common Causes of Project Failure.
59. Oz E (1994). When Professional Standards are Lax, The CONFIRM Failure and its Lessons. Commun. ACM, 37(10): 29-36.
60. Oz E, Sosik JJ (2000). Why Information Systems Projects are Abandoned: A Leadership and Communication Theory and Exploratory Study. J. Comp. Inf. Syst., 41(1): 66-77.
61. Perkins TK (2006). Knowledge: The Core Problem of Project Failure. CrossTalk J. Defense Softw. Eng., 19(6): 13-15.
62. Pinto JK, Mantel SJ (1990). The Causes of Project Failure. IEEE T. Eng. Manage., 34(7): 305-327.
63. Pinto JK, Rouhiainen PJ (2001). Building Customer-Based Project Organizations, John Wiley and Sons.
64. Procaccino JD, Verner JM, Overmyer S, Darter ME (2002). Case Study: Factors for Early Prediction of Software Development Success. Inf. Softw. Tech., 44(1): 53-62.
65. Project Management Institute (2008). PMBOK: A Guide to the Project Management Body of Knowledge. 4th ed., Project Management Institute.
66. Project Management Institute (2009). The Growing Gap between Project Manager Supply and Demand. PMI Today Supplement, June, 2.
67. Project Management Institute (2010). PMI Fact File. PMI Today, May, 16.
68. Rainer A, Hall T (2003). A quantitative and qualitative analysis of factors affecting software processes. J. Syst. Softw., 66(1): 7-21.
69. Sauer C, Cuthbertson C (2003). The State of IT Project Management in the UK 2002-2003. Comput. Wkly., 15 April.
70. Schmidt R, Lyytinen K, Keil M, Cule P (2001). Identifying Software Project Risks: An International Delphi Study. J. Manage. Inf. Syst., 17(4): 5-36.
71. Schmitt JW, Kozar KA (1978). Management's Role in Information System Development Failures: A Case Study. MIS Q., 2(2): 7-16.
72. Seaman CB (1999). Qualitative Methods in Empirical Studies of Software Engineering. IEEE T. Softw. Eng., 25(4): 557-572.
73. Skulmoski GJ, Hartman FT, Krahn J (2007). The Delphi Method for Graduate Research. J. Inf. Technol. Educ., 6: 1-21.
74. Standing C, Gulfoyle G, Lin V, Love PED (2006). The Attribution of Success and Failure in IT Projects. Ind. Manage. Data Syst., 106(8):1148-1165.
75. Standish Group International (1995). Chaos. Technical Report.
76. Standish Group International (1999). Chaos: A Recipe for Success. Technical Report.
77. Standish Group International (2001). Extreme Chaos. Technical Report.
78. Standish Group International (2006). Chaos. Technical Report.
79. Standish Group International (2009). Chaos Summary 2009: 10 Laws of CHAOS. Technical Report.
80. Standish Group International (2010). Chaos Summary for 2010. Technical Report.
81. Taylor A (2000). IT Projects: Sink or Swim. Comput. Bull., 42(1): 24-26.
82. Taylor H (2006). Critical Risks in Outsourced IT Projects: The Intractable and the Unforeseen. Commun. ACM, 49(11): 75-59.
83. Tukel OI, Rom WO (2001). An Empirical Investigation of Project Evaluation Criteria. Int. J. Oper. Prod. Man., 21(3): 400-416.
84. von Wangenheim CG, Silva DAd, Buglione L, Scheidt R, Prikladnicki R (2010). Best Practice Fusion of CMMI-DEV v1.2 (PP, PMC, SAM) and PMBOK 2008. Inf. Softw. Tech., 52(7): 749-757.
85. Wateridge J (1995). IT projects: A Basis for Success. Int. J. Proj. Manage., 13(3): 169-172.
86. Wateridge J (1998). How Can IS/IT Projects be Measured for Success. Int. J. Proj. Manage., 16(1): 59-63.
87. Weber RP (1996). Basic Content Analysis. 2nd ed., SAGE Publications.
88. White D, Fortune J (2002). Current Practice in Project Management - An Empirical Study. Int. J. Proj. Manage., 20(1): 1-11.
89. Whittaker B (1999). What Went Wrong? Unsuccessful Information Technology Projects. Inf. Manage. Comput. Security, 7(1): 23-29.
90. Wilson D (2010). New TSP Paths: System Engineering Team uses TSP to Manage Software Test Product Development. Proceedings of the TSP Symposium 2010, Pittsburgh, PA, Software Engineering Institute.
91. Wingrove A (1986). The Problems of Managing Software Projects. Softw. Eng. J., 1(1): 3-6.
92. Yeo KT (2002). Critical Failure Factors in Information Systems Projects. Int. J. Proj. Manage., 20(3): 241-246.
93. Zwikael O, Globerson S (2006). From Critical Success Factors to Critical Success Processes. Int. J. Prod. Res., 44(17): 3433-3449.