Risk Management in Software Development Using Scrum. A Systematic Literature Review

An increasing number of organizations are adopting Scrum for software development owing to its flexibility, collaborative structure, transparency, and communication, adapting to continuous changes in requirements. However, Scrum teams do not use well-defined, good practices, or systematic methods for risk management. This makes it difficult to scale and extend the knowledge and actions of different Scrum teams to mitigate risks by reducing operational efficiency. This study characterizes the risk management methods and practices used by software development teams working within a Scrum framework. In this study, a systematic literature review (SLR) was performed using five relevant databases based on eight research questions. A total of 231 records were extracted from the databases consulted, which after the process, remained in 16 primary studies according to the criteria of inclusion, exclusion, and quality. The most commonly used risk-management practices were identified, evaluated, and implemented. In addition, the analyzed models present characteristics aligned with agile values, such as collaboration and adaptability, while maintaining the iterative nature of agility. The analysis shows a wide variety of approaches that combine traditional tools with Scrum. They highlight independent and hybrid strategies as well as benefits, such as the identification of risks and the increase in team productivity and efficiency. Although Scrum contributes indirectly to risk management, a more structured approach through hybrid models is needed, complemented by risk management training for the entire Scrum team, to strengthen resilience and improve project decision making.