Organizational badge collecting
Communications of the ACM
Technical controlling and software process improvement
Journal of Systems and Software
European experiences with software process improvement
Proceedings of the 22nd international conference on Software engineering
Knowledge capability and maturity in software management
ACM SIGMIS Database - Special issue on infomration systems: current issues and future changes
A basis for process improvement inapplication management
Software Quality Control
Initial Effects of Software Process Improvement on an Experienced Software Development Team
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 1: Software Technology and Architecture
Structural Change and Change Advocacy: A Study in becoming a Software Engineering Organization
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 8 - Volume 8
De-motivators for software process improvement: an analysis of practitioners' views
Journal of Systems and Software
An exploratory study of why organizations do not adopt CMMI
Journal of Systems and Software
Experiences using systematic review guidelines
Journal of Systems and Software
Software process improvement in small and medium software enterprises: a systematic review
Software Quality Control
Overcoming the First Hurdle: Why Organizations Do Not Adopt CMMI
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
The use of empirical methods in Open Source Software research: Facts, trends and future directions
FLOSS '09 Proceedings of the 2009 ICSE Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Systematic literature reviews in software engineering - A tertiary study
Information and Software Technology
Information and Management
Software Process Improvement barriers: A cross-cultural comparison
Information and Software Technology
Refining the systematic literature review process--two participant-observer case studies
Empirical Software Engineering
Two case studies on small enterprise motivation and readiness for CMMI
Proceedings of the 11th International Conference on Product Focused Software
Do software process improvements lead to ISO 9126 architectural quality factor improvement
Proceedings of the 8th international workshop on Software quality
Dependency analysis between CMMI process areas
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Experiences conducting systematic reviews from novices' perspective
EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment in Software Engineering
The impacts of software process improvement on developers: a systematic review
Proceedings of the 34th International Conference on Software Engineering
The maturity of maturity model research: A systematic mapping study
Information and Software Technology
Hi-index | 0.00 |
Background: Software Process Improvement (SPI) is intended to improve software engineering, but can only be effective if used. To improve SPI's uptake, we should understand why organizations adopt SPI. CMM-based SPI approaches are widely known and studied. Objective: We investigated why organizations adopt CMM-based SPI approaches, and how these motivations relate to organizations' size. Method: We performed a systematic review, examining reasons reported in more than forty primary studies. Results: Reasons usually related to product quality and project performance, and less commonly, to process. Organizations reported customer reasons infrequently and employee reasons very rarely. We could not show that reasons related to size. Conclusion: Despite its origins in helping to address customer-related issues for the USAF, CMM-based SPI has mostly been adopted to help organizations improve project performance and product quality issues. This reinforces a view that the goal of SPI is not to improve process per se, but instead to provide business benefits.