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

A five-round Delphi study was conducted to determine the degree to which the Team Software Process (TSP) can address the identified critical success factors for software projects. Three high-reputation and high-calibre experts participated in this study. Our results found agreement among the experts that the TSP provided the 'Best Practises' for addressing 14 critical success factors. The experts also agreed that the TSP provided a 'Very Good' framework for addressing 4 critical success factors. Our findings further suggested that 6 critical success factors were addressed by the TSP at a 'Good' level; only 1 critical success factor was addressed to a limited degree and none of the critical success factors were addressed at the 'Fair' level. The only critical success factor not addressed by the TSP was the 'good performance by vendors/contractors/consultants' factor. From an expert's perspective, the TSP provides an operational framework that addresses 21 critical success factors software projects. We believe that each framework or method on its own cannot address all the identified critical success factors. However, by combining a software process improvement and project management framework or other excellent software development process models, all of the critical success factors can be better addressed.

[1]  M. Adler,et al.  Gazing into the oracle : the Delphi method and its application to social policy and public health , 1996 .

[2]  Paul Beynon-Davies,et al.  Human error and information systems failure: the case of the London ambulance service computer-aided despatch system project , 1999, Interact. Comput..

[3]  Daniel Galin,et al.  Software Quality Assurance: From Theory to Implementation , 2003 .

[4]  Ritu Agarwal,et al.  Organizational Mechanisms for Enhancing User Innovation in Information Technology , 1999, MIS Q..

[5]  Gregory J. Skulmoski,et al.  Journal of Information Technology Education the Delphi Method for Graduate Research , 2022 .

[6]  Capers Jones,et al.  Patterns of Large Software Systems: Failure and Success , 1995, Computer.

[7]  Watts S. Humphrey,et al.  Introduction to the Team Software Process , 1999 .

[8]  Austen Rainer,et al.  A quantitative and qualitative analysis of factors affecting software processes , 2003, J. Syst. Softw..

[9]  Daniel Antonio Callegari,et al.  Project Management and Software Development Processes: Integrating RUP and PMBOK , 2007, 2007 International Conference on Systems Engineering and Modeling.

[10]  Hazel Taylor,et al.  Critical risks in outsourced IT projects: the intractable and the unforeseen , 2006, CACM.

[11]  E. Larson,et al.  Project Management: The Managerial Process , 2002 .

[12]  Andrew Taylor,et al.  IT projects: sink or swim , 2000 .

[13]  Gary Klein,et al.  Software development risks to project effectiveness , 2000, J. Syst. Softw..

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

[15]  R. Weber.  Basic Content Analysis , 1986 .

[16]  Jeffrey K. Pinto,et al.  Building Customer-Based Project Organizations , 2001 .

[17]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

[18]  John Wateridge,et al.  IT projects: a basis for success , 1995 .

[19]  Joyce Fortune,et al.  Framing of project critical success factors by a systems model , 2006 .

[20]  Capers Jones,et al.  Why software fails , 1996 .

[21]  Chad Lin,et al.  The attribution of success and failure in IT projects , 2006, Ind. Manag. Data Syst..

[22]  Ofer Zwikael,et al.  From Critical Success Factors to Critical Success Processes , 2006 .

[23]  H. Drummond.  Riding a tiger: some lessons of Taurus , 1998 .

[24]  Leon A. Kappelman,et al.  Early Warning Signs of it Project Failure: The Dominant Dozen , 2007 .

[25]  John Wateridge,et al.  How can IS/IT projects be measured for success? , 1998 .

[26]  Brenda Whittaker,et al.  What went wrong? Unsuccessful information technology projects , 1999, Inf. Manag. Comput. Secur..

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

[28]  Ashley A. Bush,et al.  Reconciling user and project manager perceptions of IT project risk: a Delphi study 1 , 2002, Inf. Syst. J..

[29]  Terence J. Cooke-Davies,et al.  The maturity of project management in different industries: An investigation into variations between project management models , 2003 .

[30]  Peter E. D. Love,et al.  Management of risks in information technology projects , 2004, Ind. Manag. Data Syst..

[31]  Lorin J. May.  Major Causes of Software Project Failures , 2007 .

[32]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[33]  Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

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

[35]  J. R. Landis,et al.  The measurement of observer agreement for categorical data. , 1977, Biometrics.

[36]  Capers Jones,et al.  Our Worst Current Development Practices , 1996, IEEE Softw..

[37]  Walter O. Rom,et al.  An empirical investigation of project evaluation criteria , 2001 .

[38]  Noopur Davis,et al.  The Team Software ProcessSM (TSPSM) in Practice: A Summary of Recent Results , 2003 .

[39]  Albert L. Lederer,et al.  Information systems project management: an agency theory interpretation , 2003, J. Syst. Softw..

[40]  James McHale,et al.  Relating the Team Software Process(SM) (TSPSM) to the Capability Maturity Model for Software (SW-CMM) , 2002 .

[41]  W SchmittJohn,et al.  Management's role in information system development failures , 1978 .

[42]  Dov Dvir,et al.  In search of project classification: a non-universal approach to project success factors , 1998 .

[43]  Shamsul Sahibuddin,et al.  Critical success factors for software projects: A comparative study , 2011 .

[44]  Y. Kwak,et al.  Assessing Project Management Maturity , 2000 .

[45]  Bashar Nuseibeh.  Ariane 5: Who Dunnit? , 1997, IEEE Software.

[46]  Richard E. Fairley,et al.  Managing and Leading Software Projects , 2009 .

[47]  Effy Oz,et al.  When professional standards are lax: the CONFIRM failure and its lessons , 1994, CACM.

[48]  David H. Gustafson,et al.  Group Techniques for Program Planning: A Guide to Nominal Group and Delphi Processes , 1976 .

[49]  Alice E. Smith,et al.  Prediction and optimization of a ceramic casting process using a hierarchical hybrid system of neural networks and fuzzy logic , 2000 .

[50]  Watts S. Humphrey.  TSP(SM)-Coaching Development Teams , 2006 .

[51]  S. Lloyd,et al.  Project management in multi-disciplinary collaborative research , 2005, IPCC 2005. Proceedings. International Professional Communication Conference, 2005..

[52]  Gary Klein,et al.  Information system success as impacted by risks and development strategies , 2001, IEEE Trans. Engineering Management.

[53]  Nancy G. Leveson,et al.  Role of Software in Spacecraft Accidents , 2004 .

[54]  Alan Wingrove.  The problems of managing software projects , 1986, Softw. Eng. J..

[55]  June M. Verner,et al.  Case study: factors for early prediction of software development success , 2002, Inf. Softw. Technol..

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

[58]  G. William Walster,et al.  A comparative study of differences in subjective likelihood estimates made by individuals, interacting groups, Delphi groups, and nominal groups☆ , 1973 .

[59]  Jerzy R. Nawrocki,et al.  Balancing Agility and Discipline with XPrince , 2005, RISE.

[60]  Watts S. Humphrey.  Why Big Software Projects Fail: The 12 Key Questions , 2005 .

[61]  Earl R. Babbie,et al.  The practice of social research , 1969 .

[62]  Joyce Fortune,et al.  Current practice in project management — an empirical study , 2002 .

[63]  John Glaser,et al.  Management's role in IT project failures. , 2004, Healthcare financial management : journal of the Healthcare Financial Management Association.

[64]  Kenneth A. Kozar,et al.  Management's Role in Information System Development Failures: A Case Study , 1978, MIS Q..

[65]  Jeffrey K. Pinto,et al.  The causes of project failure , 1990 .

[66]  Walid Belassi,et al.  A new framework for determining critical success/failure factors in projects , 1996 .

[67]  Jacob Cohen.  A Coefficient of Agreement for Nominal Scales , 1960 .

[68]  K. T. Yeo,et al.  Critical failure factors in information system projects , 2002 .

[69]  O. Holsti.  Content Analysis for the Social Sciences and Humanities , 1969 .

[70]  Capers Jones.  Social and Technical Reasons for Software Project Failures , 2006 .