Journal
SYSTEMS, SOFTWARE AND SERVICES PROCESS IMPROVEMENT (EUROSPI 2019)
Volume 1060, Issue -, Pages 619-630Publisher
SPRINGER INTERNATIONAL PUBLISHING AG
DOI: 10.1007/978-3-030-28005-5_48
Keywords
Continuity of SPI programs; Abandonment of SPI programs; Agile methods
Funding
- CNPQ (National Council of Scientific and Technological Development) [311176/2015-1]
Ask authors/readers for more resources
The adoption of Software Process Improvement (SPI) initiatives, based on reference models, such as CMMI-DEV, is largely described in the literature. Challenges and benefits are already known, especially when these models are combined with agile methods. However, little is known on what happens after the appraisal. Do companies continue to use maturity models-based processes? Do they sacrifice agile practices? The objective of this study is thus to identify how software processes evolve in companies that use agile methods and have been assessed against maturity-based reference models. We performed a case study in four companies. Our results show that companies that use agile methods struggle to use, maintain and evolve their processes along with maturity models after the official assessment.
Authors
I am an author on this paper
Click your name to claim this paper and add it to your profile.
Reviews
Recommended
No Data Available