# Software Project Risk Identification Based on Scrum Artifacts
## 2 Related Work  
Risk management in Agile software development has gained significant attention due to its implications for project success. But while risk management strategies are followed to some extent in Agile projects, they are often implemented in a non-systematic way [13]. Researchers generally agree that incorporating risk management practices into Agile projects can mitigate risks but should be carried out without compromising Agile principles [14; 15]. Research on risk management frequently emphasizes the identification and classification of risks into specific categories, such as requirements (requirements elicitation, analysis, specification, change, and other similar risks) [16; 17; 18; 19; 20], project management [16; 17; 18; 19; 20] (management methods and processes, project initiation, project organization, project planning and control, organizational risks), communication [17; 18; 19; 20] (coordination and collaboration, customer collaboration, external stakeholders, group awareness, etc. ), technology [16; 18; 19; 21] (environmental risks, infrastructure and resources, security risks, tools selection, technology setup, etc. ), design and implementation [19; 20; 21], coding and integration [17; 18; 19], testing [16; 17; 18; 19; 20], humans [16; 18; 19; 20] (team managing, acquisition and development, trust, performance, work environment, resources, etc. ), Agile ceremonies [17; 18; 19]. Beyond the principles of risk classification, the risk management process in Agile projects has been analyzed in various studies. These investigations often focus on specific stages of the process, such as risk identification [17; 22], risk assessment [15; 23], estimation [20], or on the management process in its entirety [3; 18; 19; 21; 24; 25; 26]. Several proposals have been made to integrate formal project management techniques into the Scrum process for risk management [18; 25; 26]. The proposal for incorporating the risk management techniques from the Project Management Body of Knowledge Guide [2] into the Scrum process [25] seeks to improve the risk management mechanism in Scrum and increase the success rate of Scrum projects. Another significant contribution is the RIMPRO framework [26], which modifies PMBoK risk management processes to address risks specific to the Product Owner role. RIMPRO covers risk identification and analysis and introduces a classification system tailored to risks associated with the Product Owner. Building on this framework, the authors developed RIMPRO-AST, an automated tool designed to facilitate the management of Product Owner-related risks [27]. In [22], the AGP model is introduced, emphasizing a systematic approach to risk identification. Drawing on 1868 survey responses from professionals, the authors identify four key factors influencing project risks: organizational culture, timeframe and budget stress, project team, and project organizational environment. These factors explain up to 76% of the variability in potential risks. The study highlights the importance of integrating human-centric elements into risk management, emphasizing the collaborative and adaptive nature of Agile methodologies. In [28], a framework is proposed that integrates machine learning into risk management, introducing a risk prioritization scheme. However, this study primarily focuses on prioritization, with the overall effectiveness of the framework remaining insufficiently validated. Other emerging machine learning solutions for risk management [17; 21; 23; 29] leverage AI-based approaches but are heavily reliant on project datasets. This reliance poses a challenge in Agile environments, where the complexity of collecting high-quality data can hinder the applicability and performance of such methods. A novel process integrating a recommender system into the Scrum framework to improve risk management in Agile projects is presented in [30]. The system recommends risks and response strategies for projects based on a database of risks from similar past projects.