A framework for assisting the design of effective software process improvement implementation strategies

A number of advances have been made in the development of software process improvement (SPI) standards and models, e.g. Capability Maturity Model (CMM), more recently CMMI, and ISO's SPICE. However, these advances have not been matched by equal advances in the adoption of these standards and models in software development which hasresulted in limited success for many SPI efforts. The current problem with SPI is not a lack of standards or models, but rather a lack of an effective strategy to successfully implement these standards or models. In this paper we have focused on SPI implementation issues and designed three individual components in order to assist SPI practitioners in the design of effective SPI implementation initiatives. We have pulled together individual components under one SPI implementation framework (SPI-IF) using a bottom-up approach already familiar to many practitioners and researchers. The framework is based on the results drawn from SPI literature and an empirical study we have carried out. In the design of SPI-IF, the concept of critical success factors (CSFs) was used and extended. Thirty-four CSF interviews were conducted with Australian practitioners. In addition, 50 research articles (published experience reports and case studies) were also selected and analysed in order to identify factors that play positive or negative roles in SPI implementation. The SPI-IF provides a very practical structure with which to assess and implement SPI implementation initiatives. In order to evaluate SPI-IF, a practical evaluation scheme was undertaken. The evaluation results show that SPI-IF has potential to assist SPI practitioners in the design of effective SPI implementation initiatives. Thus, we recommend organizations to use SPI-IF in order to effectively design SPI implementation initiatives.

[1]  Hugh Coolican Research Methods and Statistics in Psychology , 1993 .

[2]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .

[3]  Watts S. Humphrey,et al.  A discipline for software engineering , 2012, Series in software engineering.

[4]  Peter Axel Nielsen,et al.  Implementing software process improvement: two cases of technology transfer , 2000, Proceedings of the 33rd Annual Hawaii International Conference on System Sciences.

[5]  Al Florence Lessons Learned in Attempting to Acheive Software CMM Level 4 , 2001 .

[6]  J. Rockart Chief executives define their own data needs. , 1979, Harvard business review.

[7]  Ian Sommerville,et al.  Improving the Requirements Process , 1998, REFSQ.

[8]  Mark C. Paulk,et al.  Capability Maturity Model for Software , 2001 .

[9]  Sami Zahran Software process improvement - practical guidelines for business success , 1998 .

[10]  Austen Rainer,et al.  Key success factors for implementing software process improvement: a maturity-based analysis , 2002, J. Syst. Softw..

[11]  Didar Zowghi,et al.  A Framework for Guiding the Design of Effective Implementation Strategies for Software Process Improvement , 2003, SEKE.

[12]  Toni M. Somers,et al.  The impact of critical success factors across the stages of enterprise resource planning implementations , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[13]  Atte Kinnula,et al.  Deploying the defined SW process , 2000 .

[14]  Didar Zowghi,et al.  Critical Success Factors and Critical Barriers for Software Process Improvement: An Analysis of Literature , 2003 .

[15]  T. D. Wilson,et al.  Determining organizational information needs: the Critical Success Factors approach , 2001, Inf. Res..

[16]  D. Wilson,et al.  Views of software quality: a field report , 1997, IEE Proc. Softw. Eng..

[17]  P. Burnard A method of analysing interview transcripts in qualitative research. , 1991, Nurse education today.

[18]  Didar Zowghi,et al.  Critical barriers for software process improvement implementation: An empirical study , 2004, IASTED Conf. on Software Engineering.

[19]  Susan Rosenbaum,et al.  Schlumberger's Software Improvement Program , 1994, IEEE Trans. Software Eng..

[20]  Aileen B. Sedman,et al.  A longitudinal study , 1987 .

[21]  Brian Fitzgerald,et al.  A Longitudinal Study of Software Process Improvement , 1999, IEEE Softw..

[22]  Ian Sommerville,et al.  Requirements process improvement through the phased introduction of good practice , 1997 .

[23]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[24]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[25]  James D. Herbsleb,et al.  After the Appraisal: A Systematic Survey of Process Improvement, its Benefits, and Factors that Influence Success. , 1995 .

[26]  R. R. Willis,et al.  Hughes Aircraft's Widespread Deployment of a Continuously Improving Software Process , 1998 .

[27]  Robert K. Yin,et al.  Applications of case study research , 1993 .

[28]  Didar Zowghi,et al.  A Model for the Implementation of Software Process Improvement: An Empirical Study , 2003, PROFES.

[29]  G. Lynn Tinsley,et al.  The Carnegie Mellon University Library Information System (LIS): Applications within the Software Engineering Institute (SEI) Online Environment. , 1993 .

[30]  Michael Diaz,et al.  How Software Process Improvement Helped Motorola , 1997, IEEE Softw..

[31]  Mark C. Paulk,et al.  Capability Maturity Model for Software, Version 1.1 , 1993 .

[32]  Tracy Hall,et al.  Perceptions of software quality: a pilot study , 1998, Software Quality Journal.

[33]  Nathan Baddoo,et al.  Motivators and de-motivators in software process improvement : an empirical study , 2001 .

[34]  Michael Daskalantonakis,et al.  Achieving higher SEI levels , 1994, IEEE Software.

[35]  T. D. Wilson,et al.  The management information requirements of heads of university departments: a critical success factors approach , 1993, J. Inf. Sci..

[36]  Tracy Hall,et al.  De-motivators for software process improvement: an analysis of practitioners' views , 2003, J. Syst. Softw..

[37]  Bill Pitterman Telcordia Technologies: The Journey to High Maturity , 2000, IEEE Softw..

[38]  Craig K. Tyran,et al.  The implementation of expert systems: a survey of successful implementations , 1993, DATB.

[39]  Mark C. Paulk,et al.  Practices of High Maturity Organizations , 1999 .

[40]  Paul D Jeanne Ellis Ormrod Leedy,et al.  Practical Research: Planning and Design , 1974 .

[41]  Priscilla Fowler,et al.  Lessons Learned Collaborating on a Process for SPI at Xerox , 1999 .

[42]  Vijay K. Khandelwal,et al.  Critical success factors (CSFs) and the growth of IT in selected geographic regions , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[43]  Didar Zowghi,et al.  A Maturity Model for the Implementation of Software Process Improvement: an Empirical Study , 2022 .

[44]  Werner Mellis,et al.  Success factors of organizational change in software process improvement , 1998 .

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

[46]  Donald R. Cooper,et al.  Business Research Methods , 1980 .

[47]  Deependra Moitra,et al.  Managing change for software process improvement initiatives: a practical experience‐based approach , 1998 .

[48]  Anita D. Carleton,et al.  Case studies of software-process-improvement measurement , 1994, Computer.

[49]  Albert Johnson Software process improvement experience in the DP/MIS function: experience report , 1994, ICSE 1994.

[50]  Richard Messnarz,et al.  Better Software Practice for Business Benefit: Principles and Experiences , 1999 .