Software process improvement in Scrum teams: A review of the literature

Abstract

In the Global Software Development (GSD) context, adopting agile methodologies, especially Scrum, has significantly transformed software delivery by emphasizing short iterations, continuous feedback, and adaptability, thus improving productivity and software quality. However, implementing Software Process Improvement (SPI) within Scrum teams still presents significant challenges, such as resistance to change, aligning agile practices with the requirements of standards like ISO/IEC 29110 and CMMI, and the additional administrative burdens these entail. Our primary objective is to identify the SPI practices Scrum teams are considered. We are also interested in identifying the difficulties in implementing SPI practices that have been reported. After analyzing the selected primary studies, we identified the most common SPI practices used by Scrum teams. The critical success factors identified were team and stakeholder commitment, a culture of continuous improvement, effective communication, and the use of tools and metrics to measure progress. Despite the existing challenges, the perception of SPI initiatives among Scrum team members varies. Many appreciate the software quality and structure improvement, but some see a possible incompatibility with agile practices and increased administrative workload. Our research concludes that the benefits of SPI practices justify the effort and that success depends on adaptability, continuous training, empirical improvement, and active team involvement.