Software process improvement: a systematic mapping study on the state of the art

Software process improvement (SPI) has been around for decades: frameworks are proposed, success factors are studied, and experiences have been reported.However, the sheermass of concepts, approaches, and standards published over the years overwhelms practitioners as well as researchers. What is out there? Are there new trends and emerging approaches?What are open issues? Still, we struggle to answer these questions about the current state of SPI and related research. In this article, we present results from an updated systematic mapping study to shed light on the field of SPI, to develop a big picture of the state of the art, and to draw conclusions for future research directions. An analysis of 769 publications draws a big picture of SPI-related research of the past quarter-century. Our study shows a high number of solution proposals, experience reports, and secondary studies, but only few theories and models on SPI in general. In particular, standard SPImodels likeCMMI and ISO/IEC 15,504 are analyzed, enhanced, and evaluated for applicability in practice, but these standards are also critically discussed, e.g., from the perspective of SPI in small-to-medium-sized companies, which leads to new specialized frameworks. New and specialized frameworks account for the majority of the contributions found (approx. 38%). Furthermore, we find a growing interest in success factors (approx. 16%) to aid companies in conducting SPI and in adapting agile principles and practices for SPI (approx. 10%). Beyond these specific topics, the study results also show an increasing interest into secondary studies with the purpose of aggregating and structuring SPI-related knowledge. Finally, the present study helps directing future research by identifying under-researched topics awaiting further investigation. Subjects Software Engineering

[1]  Carolyn B. Seaman,et al.  Why do programmers avoid metrics? , 2008, ESEM '08.

[2]  Roel Wieringa,et al.  Requirements engineering paper classification and evaluation criteria: a proposal and a discussion , 2005, Requirements Engineering.

[3]  D. Ross Jeffery,et al.  An exploratory study of why organizations do not adopt CMMI , 2007, J. Syst. Softw..

[4]  J. G. Brodman,et al.  What small businesses and small organizations say about the CMM , 1994, Proceedings of 16th International Conference on Software Engineering.

[5]  Rory O'Connor,et al.  Investigating software process in practice: A grounded theory perspective , 2008, J. Syst. Softw..

[6]  Davi Viana,et al.  The influence of human aspects on software process improvement: Qualitative research findings and comparison to previous studies , 2012, EASE.

[7]  Werner Mellis,et al.  Success factors of organizational change in software process improvement , 1998, Softw. Process. Improv. Pract..

[8]  Claude Y. Laporte,et al.  Systems and Software Engineering Standards for Very Small Entities: Implementation and Initial Results , 2014, 2014 9th International Conference on the Quality of Information and Communications Technology.

[9]  Risto Nevalainen,et al.  Agile Maturity Model: A Synopsis as a First Step to Synthesis , 2013, EuroSPI.

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

[11]  Marco Kuhrmann,et al.  Software process improvement: where is the evidence? , 2016, Software Engineering.

[12]  Hans Christian Benestad,et al.  Perceived productivity threats in large agile development projects , 2010, ESEM '10.

[13]  Sussy Bayona Oré,et al.  Critical success factors taxonomy for software process deployment , 2012, Software Quality Journal.

[14]  M. Elizabeth C. Hull,et al.  Software development processes - an assessment , 2002, Inf. Softw. Technol..

[15]  Deborah J. Armstrong,et al.  Exploring the Relationship between Organizational Adoption Motives and the Tailoring of Agile Methods , 2014, 2014 47th Hawaii International Conference on System Sciences.

[16]  Jarmo J. Ahonen,et al.  LAPPI: A light‐weight technique to practical process modeling and improvement target identification , 2013, J. Softw. Evol. Process..

[17]  Mary Shaw,et al.  Writing good software engineering research papers: minitutorial , 2003, ICSE 2003.

[18]  Mario Piattini,et al.  Software process improvement in small and medium software enterprises: a systematic review , 2008, Software Quality Journal.

[19]  Marco Kuhrmann,et al.  Is Water-Scrum-Fall Reality? On the Use of Agile and Traditional Development Practices , 2015, PROFES.

[20]  Marco Kuhrmann,et al.  A mapping study on the feasibility of method engineering , 2014, J. Softw. Evol. Process..

[21]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[22]  Charles W. Butler,et al.  Choice of Software Development Methodologies: Do Organizational, Project, and Team Characteristics Matter? , 2016, IEEE Software.

[23]  Ivan Rozman,et al.  Managing the complexity of SPI in small companies , 2000, Softw. Process. Improv. Pract..

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

[25]  Paolo Tell,et al.  How Does Software Process Improvement Address Global Software Engineering? , 2016, 2016 IEEE 11th International Conference on Global Software Engineering (ICGSE).

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

[27]  Tore Dybå,et al.  An Instrument for Measuring the Key Factors of Success in Software Process Improvement , 2000, Empirical Software Engineering.

[28]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[29]  Khaled El Emam,et al.  An empirical review of software process assessments , 2000, Adv. Comput..

[30]  Tony Gorschek,et al.  Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review , 2012, IEEE Transactions on Software Engineering.

[31]  Kirsi Korhonen Evaluating the impact of an agile transformation: a longitudinal case study in a distributed context , 2012, Software Quality Journal.

[32]  Káthia Marçal de Oliveira,et al.  Defining a catalog of indicators to support process performance analysis , 2011, J. Softw. Maintenance Res. Pract..

[33]  Ivan Rozman,et al.  Managing the complexity of SPI in small companies , 2000 .

[34]  Mario Piattini,et al.  A Process for Driving Process Improvement in VSEs , 2009, ICSP.

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

[36]  Pekka Abrahamsson,et al.  An iterative improvement process for agile software development , 2007, Softw. Process. Improv. Pract..

[37]  Mark Staples,et al.  Systematic review of organizational motivations for adopting CMM-based SPI , 2008, Inf. Softw. Technol..

[38]  Jürgen Münch,et al.  Software Process Definition and Management , 2012, The Fraunhofer IESE Series on Software and Systems Engineering.

[39]  Marjan Hericko,et al.  PROCESSUS – Integration of SEI CMM and ISO quality models , 2004, Software Quality Journal.

[40]  Martin Höst,et al.  A review of methods for evaluation of maturity models for process improvement , 2012, J. Softw. Evol. Process..

[41]  Austen Rainer,et al.  Implementing software process improvement: an empirical study , 2002, Softw. Process. Improv. Pract..

[42]  Stefan Wagner,et al.  What Do Practitioners Vary in Using Scrum? , 2015, XP.

[43]  Laurie A. Williams,et al.  Have Agile Techniques been the Silver Bullet for Software Development at Microsoft? , 2013, 2013 ACM / IEEE International Symposium on Empirical Software Engineering and Measurement.

[44]  Sune Dueholm Müller,et al.  Improvement as organizational change : A metaphorical nalysis of the literature une , 2010 .

[45]  Ian Allison Organizational Factors Shaping Software Process Improvement in Small-Medium Sized Software Teams: A Multi-Case Analysis , 2010, 2010 Seventh International Conference on the Quality of Information and Communications Technology.