A grounded theory of software process improvement model adoption

This study, using a grounded theory methodology, analyzed data collected from software developers and IT professionals on software process improvement (SPI) adoption. The study is presented within a backdrop of organizational change steps described by John P. Kotter in his 1996 book, Leading Change. Software quality problems and failures have caused many financial losses, injuries, and even deaths. In the mid 1980s, as a means of mitigating these problems, the Department of Defense (DoD) and Carnegie Mellon University (CMU) began work on the Capability Maturity Model (CMM®) In 2001, the model was superseded by a more robust model, the Capability Maturity Model Integration (CMMI®) These models were designed to provide descriptive, key process improvement areas for organizations to achieve greater maturity in their software and systems development. Organizations could then be appraised at specific maturity levels. According to CMU, SPI improves quality and reliability of software products. The DoD and several organizations now require companies to be appraised at a certain maturity level prior to being awarded a contract. From the onset, there have been difficulties in the adoption of these SPI models. Some of these difficulties can be attributed to organizational change issues. Through grounded theory analysis, a substantive theory was developed, The Theory of Software Process Improvement Model Adoption. This theory contributes to the body of knowledge by providing data and analysis from numerous IT professionals and software developers. This study also provides suggested key organizational change concerns for better SPI adoption practices.

[1]  H. Harrington.  Business process improvement : the breakthrough strategy for total quality, productivity, and competitiveness , 1991 .

[2]  Jane Barnsteiner,et al.  Using Grounded Theory in Nursing , 2002 .

[3]  R. H. Franke,et al.  The Hawthorne experiments: First statistical interpretation. , 1978 .

[4]  Robert Chia,et al.  On Organizational Becoming: Rethinking Organizational Change , 2002, Organ. Sci..

[5]  J. Kotter.  Leading change: why transformation efforts fail , 2009, IEEE Engineering Management Review.

[6]  Mayuram S. Krishnan,et al.  Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development , 2000 .

[7]  Peter Axel Nielsen,et al.  Understanding the implementation of software process improvement innovations in software organizations , 2004, Inf. Syst. J..

[8]  P. Senge.  THE FIFTH DISCIPLINE , 1997 .

[9]  S. Piderit.  Rethinking Resistance and Recognizing Ambivalence: A Multidimensional View of Attitudes Toward an Organizational Change , 2000 .

[10]  Colin Sharp.  Qualitative Research and Evaluation Methods (3rd ed.) , 2003 .

[11]  Steven R. Rakitin,et al.  Software verification and validation for practitioners and managers , 2001 .

[12]  Thiagarajan Ravichandran,et al.  Quality Management in Systems Development: An Organizational System Perspective , 2000, MIS Q..

[13]  R. Mortensen,et al.  [Qualitative research in nursing]. , 1992, Vard i Norden.

[14]  Gary S. Lynn,et al.  New Product Team Learning: Developing and Profiting from Your Knowledge Capital , 1998 .

[15]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .

[16]  B Clover.  An ideal model. , 1990, The Health service journal.

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

[18]  C. Urquhart.  An encounter with grounded theory: tackling the practical and philosophical issues , 2001 .

[19]  F. Herzberg.  One More Time: How Do You Motivate Employees? , 2008 .

[20]  Kent Johnson,et al.  Interpreting the CMMI : A Process Improvement Approach , 2003 .

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

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

[23]  Richard Luecke,et al.  Managing Change and Transition , 2002 .

[24]  Peter Axel Nielsen,et al.  Competing values in software process improvement: an assumption analysis of CMM from an organizational culture perspective , 2003, IEEE Trans. Engineering Management.

[25]  Michael West,et al.  Real Process Improvement Using the CMMI , 2004 .

[26]  Nancy G. Leveson,et al.  An investigation of the Therac-25 accidents , 1993, Computer.

[27]  Mark C. Paulk,et al.  The Impact of Evolving the Capability Maturity Model to Version 1.1 , 2007 .

[28]  P. Kidwell,et al.  The mythical man-month: Essays on software engineering , 1996, IEEE Annals of the History of Computing.

[29]  J. Kotter,et al.  The Heart of Change: Real-Life Stories of How People Change Their Organizations , 2002 .

[30]  H. Raiffa,et al.  The hidden traps in decision making. , 1998, Harvard business review.

[31]  Diane L. Gibson,et al.  Demonstrating the Impact and Benefits of CMMI ® : An Update and Preliminary Results , 2003 .

[32]  R. Schaffer,et al.  Successful change programs begin with results. , 1992, Harvard business review.

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

[34]  Austen Rainer,et al.  An analysis of some core studies of software process improvement , 2001, Softw. Process. Improv. Pract..

[35]  Wanda J. Orlikowski,et al.  Improvising Organizational Transformation Over Time: A Situated Change Perspective , 1996, Inf. Syst. Res..

[36]  Zane Robinson Wolf,et al.  From Practice to Grounded Theory: Qualitative Research in Nursing , 1987 .

[37]  A. Strauss,et al.  The Discovery of Grounded Theory , 1967 .

[38]  Schaffer Rh,et al.  Successful change programs begin with results. , 1992 .

[39]  Watts S. Humphrey,et al.  A comparison of US and Japanese software process maturity , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[40]  G.E. Moore,et al.  Cramming More Components Onto Integrated Circuits , 1998, Proceedings of the IEEE.

[41]  Keith M. Sturges,et al.  Mapping the Process: An Exemplar of Process and Challenge in Grounded Theory Analysis , 2005 .

[42]  Mark T True,et al.  Software Requirements , 2005 .

[43]  유창조.  Naturalistic Inquiry , 2000, The SAGE Encyclopedia of Research Design.

[44]  Susan Gasson.  Rigor in Grounded Theory Research: An Interpretive Perspective on Generating Theory from Qualitative Field Studies , 2004 .

[45]  Peter C. Reid,et al.  Well Made in America: Lessons from Harley-Davidson on Being the Best , 1989 .

[46]  M. Beer,et al.  Why change programs don't produce change. , 1990, Harvard business review.

[47]  Amy B. Woszczynski,et al.  The Handbook of Information Systems Research , 2003 .

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

[49]  Alvita K. Nathaniel,et al.  A grounded theory of moral reckoning in nursing , 2004 .

[50]  RaiArun,et al.  Quality management in systems development , 2000 .

[51]  Robert Fantina.  Practical Software Process Improvement , 2005 .

[52]  M. Patton.  Qualitative research and evaluation methods , 1980 .

[53]  D. Larcker,et al.  The Performance Effects of Process Management Techniques , 1997 .

[54]  Pankaj Jalote,et al.  CMM in Practice: Processes for Executing Software Projects at Infosys , 1999 .

[55]  E. Rogers.  Diffusion of Innovations , 1962 .