Abstract
Small and medium enterprises are a very important cog in the gears of the world economy. The software industry in most countries is composed of an industrial scheme that is made up mainly of small and medium software enterprises—SMEs. To strengthen these types of organizations, efficient Software Engineering practices are needed—practices which have been adapted to their size and type of business. Over the last two decades, the Software Engineering community has expressed special interest in software process improvement (SPI) in an effort to increase software product quality, as well as the productivity of software development. However, there is a widespread tendency to make a point of stressing that the success of SPI is only possible for large companies. In this article, a systematic review of published case studies on the SPI efforts carried out in SMEs is presented. Its objective is to analyse the existing approaches towards SPI which focus on SMEs and which report a case study carried out in industry. A further objective is that of discussing the significant issues related to this area of knowledge, and to provide an up-to-date state of the art, from which innovative research activities can be thought of and planned.
Similar content being viewed by others
Explore related subjects
Discover the latest articles, news and stories from top researchers in related subjects.References
Biolchini, J., Gomes, P., Cruz, A., & Travassos, G. (2005). Systematic review in software engineering. Rio de Janeiro, Brazil: Systems Engineering and Computer Science Department, UFRJ. http://www.cronos.cos.ufrj.br/publicacoes/reltec/es67905.pdf.
Biolchini, J., Gomes, P., Cruz, A., Uchôa, T., & Travassos, G. (2007). Scientific research ontology to support systematic review in software engineering. Advanced Engineering Informatics, 21(2), 133–151.
Brodman, J. G., & Johnson, D. L. (1994). What small business and small organizations say about the CMM: Experience report. In Proceedings of the 16th International Conference On Software Engineering, Sorrento, Italy (pp. 331–340).
Calvo-Manzano, J. A., Cuevas, G., San Feliu, T., De Amescua, A., & Pérez, M. (2002). Experiences in the application of software process improvement in SMES. Software Quality Journal, 10(3), 261–273.
Casey, V., & Richardson, I. (2004). A practical application of the IDEAL model. Software Process: Improvement and Practice, 9(3), 123–132.
Derniame, J.-C., Kaba, A. B., & Warboys, B. (Eds.). (1999). The software process: Modelling and technology. In Software process: Principles, methodology, and technology (pp. 1–12). Germany: Springer.
Dyba, T. (2005). An empirical investigation of the key factors for success in software process improvement. IEEE Transactions on Software Engineering, 31(5), 410–424.
El Emam, K., & Birk, A. (2000). Validating the ISO/IEC 15504 measures of software development process capability. Journal of Systems and Software, 51(2), 119–149.
EU. (2005). The new SME definition. User guide and model declaration (pp. 1–52). European Commission. http://www.ec.europa.eu/enterprise/enterprise_policy/sme_definition/sme_user_guide.pdf.
Fayad, M. E., Laitinen, M., & Ward, R. P. (2000). Software engineering in the small. Communications of the ACM, 43(3), 115–118.
Florac, W. A., Park, R. E., & Carleton, A. D. (1997). Practical software measurement: Measuring for process management and improvement (pp. 1–12). Pittsburgh: Software Engineering Institute, Carnegie Mellon University.
Hall, T., Rainer, A., & Baddoo, N. (2002). Implementing software process improvement: An empirical study. Software Process: Improvement and Practice, 7(1), 3–15.
Hannay, J. E., Sjøberg, D. I. K., & Dybå, T. (2007). A systematic review of theory use in software engineering experiments. IEEE Transaction on Software Engineering, 33(2), 87–107.
Hareton, L., & Terence, Y. (2001). A process framework for small projects. Software Process: Improvement and Practice, 6(2), 67–83.
ISO. (2004). ISO/IEC 12207:2002/FDAM 2. Information technology – Software life cycle processes. Geneva: International Organization for Standardization. www.iso.org.
ISO. (2006). ISO/IEC JTC1/SC7 Working Group 24. Available on: http://www.iso-iec-sc7wg24.gelog.etsmtl.ca/Webpage/iso-iec-sc7wg24_english.html. Accessed: January, 2007.
Johnson, D. L., & Brodman, J. G. (1999). Tailoring the CMM for small businesses, small organizations, and small projects. In K. El Eman & N. Madhavji (Eds.), Elements of software process assessment and improvement (pp. 239–259). Los Alamitos: IEEE CS Press.
Jørgensen, M., & Shepperd, M. J. (2007). A systematic review of software development cost estimation studies. IEEE Transaction on Software Engineering, 33(1), 33–53.
Kitchenham, B. (2004). Procedures for performing systematic reviews (pp. 1–28). Keele University and ICT Australia Ltd. http://www.idi.ntnu.no/emner/empse/papers/kitchenham_2004.pdf.
Oktaba, H., Garcia, F., Piattini, M., Pino, F., Alquicira, C., & Ruiz, F. (2007). Software process improvement: The COMPETISOFT project. IEEE Computer, 40(10), 21–28.
Paulk, M. C. (1998). Using the software CMM in small organizations. In Proc. Joint 16th Pacific Northwest Software Quality Conf. and 8th Int’l Conf. Software Quality (pp. 350–360).
Pino, F., Garcia, F., Piattini, M., & Oktaba, H. (2006). Revisión sistemática de mejora de procesos software en micro, pequeñas y medianas empresas. COMPETISOFT_IT_1. Ciudad Real, España: CYTED. http://www.alarcos.inf-cr.uclm.es/competisoft/privado/deriverables/COMPETISOFT_IT%201.pdf.
Richardson, I. (2001). Software process matrix: A small company SPI model. Software Process: Improvement and Practice, 6(3), 157–165.
Rout, T., Tuffley, A., Cahill, B., & Hodgen, B. (2000). The RAPID assessment of software process capability. In First International Conference on Software Process Improvement and Capability Determination (pp. 47–56).
Saiedian, H., & Carr, N. (1997). Characterizing a software process maturity model for small organizations. ACM SIGICE Bulletin, 23(1), 2–11.
Scott, L., Jeffery, R., Carvalho, L., D’Ambra, J., & Rutherford, P. (2001). Practical software process improvement – The IMPACT project. In Proceedings of the Australian Software Engineering Conference (pp. 182–189).
SEI. (2006). Improving processes in small settings (IPSS project). Available on: http://www.sei.cmu.edu/iprc/ipssbackground.html. Accessed: October, 2006.
Staples, M., & Niazi, M. (2007). Systematic review of organizational motivations for adopting CMM-based SPI. Information and Software Technology, doi:10.1016/j.infsof.2007.07.003.
Staples, M., Niazi, M., Jeffery, R., Abrahams, A., Byatt, P., & Murphy, R. (2007). An exploratory study of why organizations do not adopt CMMI. Journal of Systems and Software, 80(6), 883–895.
Wangenheim, C. G. v., Anacleto, A., & Salviano, C. F. (2006). Helping small companies assess software processes. IEEE Software, 23(1), 91–98.
Yoo, C., Yoon, J., Lee, B., Lee, C., Lee, J., Hyun, S., & Wu, C. (2006). A unified model for the implementation of both ISO 9001:2000 and CMMI by ISO-certified organizations. Journal of Systems and Software, 79(7), 954–961.
Acknowledgments
We would like to thank anonymous reviewers for their useful comments in order to improve this paper, and we acknowledge the assistance of the following projects: COMPETISOFT (506AC287) financed by CYTED, MECENAS (PBI06-0024) granted by the “Junta de Comunidades de Castilla-La Mancha” of Spain and ESFINGE (TIN2006-15175-C05-05) financed by Dirección General de Investigación of the Ministerio de Educación y Ciencia of Spain.
Author information
Authors and Affiliations
Corresponding author
Appendices
Appendix A
The protocol summary for this systematic review is presented below. To carry out the systematic review of SPI in SMEs the protocol template presented in Biolchini et al. (2005) and Kitchenham’s guidelines for systematic reviews presented in Kitchenham (2004) were followed, along with some advice from other published systematic reviews.
1.1 Review planning
1.1.1 Question formulation
Question focus The goal of this systematic review is to identify experience reports and initiatives carried out in Software Engineering related to software process improvement in SMEs.
Question quality and amplitude
-
Problem: The improvement models established by the SEI or ISO were structured in such a way as to be applicable to large companies. These models cannot easily be applied in small and medium organizations, given the fact that an improvement project involves a large investment in terms of time, money and resources. The great complexity of the recommendations must also be taken into account, along with the fact that the return on the investment undertaken has to be seen from a long term perspective (Hareton and Terence 2001; Johnson and Brodman 1999; Saiedian and Carr 1997).
-
Question: What approaches concerning SPI exist, which focus both on SMEs and report on a case study?
-
Keywords and synonyms: software, process, improvement, SPI, small, enterprises, organizations, companies, team, firms, SME, settings, CMM, CMMI, 15504, SPICE, 12207 and 9001.
-
Intervention: To analyse/study the different proposals about software process improvement which have been applied on SMEs.
-
Control: There are no initial data for this systematic review.
-
Effect: Identification of the processes improved, key factors for improvements, improvement strategies conducted and the models for process improvement which are most usually applied in SMEs.
-
Outcome: To present an up-to-date state of the art regarding SPI proposals applied in SMEs from which to think of and plan innovative research activities as well as to discuss the significant issues related to this area of knowledge.
-
Population: Research proposals in the software processes improvement area which have been applied within SMEs and which have been published in the list of sources.
-
Application: People related to SPI and SMEs, such as instructors, researchers, company managers and improvement project managers, among others.
-
Experimental design: A non-statistical method will be applied.
1.1.2 Sources selection
Definition of source selection criteria The sources have been identified based on the judgment of experts in the area of work which is the scope of the systematic review.
Study language English
Source identification
-
Source search method: The search execution of the primary results will be performed by means of the search web engines of each of the selected sources.
-
Search string: There are two strings.
-
First “software process improvement” AND (small AND(enterprises OR organizations OR companies OR team OR firms OR settings)).
-
Second (small AND (enterprises OR organizations OR companies OR team OR firms OR settings)) AND (CMM OR 15504 OR SPICE OR 9001 OR 12207).
-
-
Source list: The planned list of sources is:
-
Science@Direct on the subject of Computer Science,
-
Wiley InterScience on the subject of Computer Science,
-
IEEE Digital Library,
-
ACM Digital Library, and
-
As grey literature the special report “Proceedings of the First International Research Workshop for Process Improvement in Small Settings” from SEI was reviewed.
-
-
Source selection after evaluation: Expert opinion concluded that, a priori, all the selected sources satisfy the quality criteria, as the sources include significant and highly important journals in the area of knowledge tackled by the systematic review.
-
Reference checking: The sources were approved.
1.1.3 Study selection
Study definition
-
Study inclusion and exclusion criteria definition: Since search strings are not intended to search empirical studies in the software industry, we defined the inclusion and exclusion criteria in such a way as to include publications that report case studies.
From the analysis conducted in the first iteration of the relevant studies, we ascertained that they treated the SPI and SMEs at different levels:
-
A first level, where the study consists of the application of a process improvement effort that focuses on small and medium-size organizations (there is a case study applied to SMEs).
-
A second level, where the study deals with SPI initiatives for SMEs which nevertheless have never been applied in such companies (there is no case study applied to SMEs).
-
A third level, in which the study reports on SPI initiatives where some SMEs are involved, but improvement in these companies was not the main objective of those initiatives.
To determine which articles, in the context of the systematic review, were important enough to be considered as primary studies, the exclusion criterion was to exclude any of those which dealt with SPI and SMEs at levels two and three.
-
Study type definition: Publications about SPI initiatives applied in SMEs, which have been reported as papers in the selected sources.
-
Procedures for study selection: see Fig. 1.
1.2 Planning evaluation
The protocol evaluation of this systematic review was performed through:
-
Protocol execution testing on one source in the first iteration of the review. During this iteration the protocol that was initially planned was evaluated and improved in order to achieve the review objectives, giving the final protocol presented in this work as a result. Some pre-searches were carried out to select the most suitable set of keywords and search strings. For example, in the planning evaluation stage and with regard to keywords, we initially considered the words “Small” and “Medium”, as small and medium are part of the acronym SME. However, when the search of this first iteration was performed by using the words “small” and “medium”, it was observed that the set of publications was a subset of the publications returned by using only the word “small”. Because of this, only the word “small” was included in the definitive search strings. The same strategy was followed when choosing the search strings in singular and/or plural forms. Finally, the plural form was considered to be most suitable to perform the searches as with singular search strings only a subset of publications extracted with strings in plural were obtained.
-
Periodical meetings took place with two experts in the field of research, in order to validate the protocol and to track the review execution, to ensure that it was being carried out in a suitable manner.
1.3 Review execution
1.3.1 Selection execution
-
Initial study selection: The complete selection execution and list of studies can be found in Pino et al. (2006).
-
Study quality evaluation: See Sect. 2.4. Moreover, all selected studies have an assumption of quality, as they have been published in the selected sources. This means that the publications accepted have gone through a strict reviewing period which guarantees their quality.
-
Selection review: The study selection was approved in control meetings with the experts in the area.
1.3.2 Information extraction
Information inclusion and exclusion criteria definition The data inclusion criteria from the primary studies consisted of collecting information about the improvement strategy applied, the processes improved, the improvement success key factors and the models used for process improvement. Moreover, the most important ideas from the studies were registered.
Data extraction forms See Sect. 2.4.
Extraction execution See Table 3. The complete data extraction execution can be found in Pino et al. (2006).
Resolution of divergence among reviewers There was no divergence; only one person carried out the execution of the review and two experts validated the information.
Appendix B: List of selected studies
In this section the selected primary studies in the systematic review are presented.
Rights and permissions
About this article
Cite this article
Pino, F.J., García, F. & Piattini, M. Software process improvement in small and medium software enterprises: a systematic review. Software Qual J 16, 237–261 (2008). https://doi.org/10.1007/s11219-007-9038-z
Published:
Issue Date:
DOI: https://doi.org/10.1007/s11219-007-9038-z