Ademar França de Sousa Neto, F. Ramos, D. Albuquerque, Emanuel Dantas, M. Perkusich, H. Almeida, A. Perkusich
{"title":"Towards a Recommender System-based Process for Managing Risks in Scrum Projects","authors":"Ademar França de Sousa Neto, F. Ramos, D. Albuquerque, Emanuel Dantas, M. Perkusich, H. Almeida, A. Perkusich","doi":"10.1145/3555776.3577748","DOIUrl":null,"url":null,"abstract":"Agile Software Development (ASD) implicitly manages risks through, for example, its short development cycles (i.e., iterations). The absence of explicit risk management activities in ASD might be problematic since this approach cannot handle all types of risks, might cause risks (e.g., technical debt), and does not promote knowledge reuse throughout an organization. Thus, there is a need to bring discipline to agile risk management. This study focuses on bringing such discipline to organizations that conduct multiple projects to develop software products using ASD, specifically, the Scrum framework, which is the most popular way of adopting ASD. For this purpose, we developed a novel solution that was articulated in partnership with an industry partner. It is a process to complement the Scrum framework to use a recommender system that recommends risks and response plans for a target project, given the risks registered for similar projects in an organization's risk memory (i.e., database). We evaluated the feasibility of the proposed recommender system solution using pre-collected datasets from 17 projects from our industry partner. Since we used the KNN algorithm, we focused on finding the best configuration of k (i.e., the number of neighbors) and the similarity measure. As a result, the configuration with the best results had k = 6 (i.e., six neighbors) and used the Manhattan similarity measure, achieving precision = 45%; recall = 90%; and F1-score = 58%. The results show that the proposed recommender system can assist Scrum Teams in identifying risks and response plans, and it is promising to aid decision-making in Scrum-based projects. Thus, we concluded that our proposed recommender system-based risk management process is promising for helping Scrum Teams address risks more efficiently.","PeriodicalId":42971,"journal":{"name":"Applied Computing Review","volume":null,"pages":null},"PeriodicalIF":0.4000,"publicationDate":"2023-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Applied Computing Review","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3555776.3577748","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q4","JCRName":"COMPUTER SCIENCE, INFORMATION SYSTEMS","Score":null,"Total":0}
引用次数: 0
Abstract
Agile Software Development (ASD) implicitly manages risks through, for example, its short development cycles (i.e., iterations). The absence of explicit risk management activities in ASD might be problematic since this approach cannot handle all types of risks, might cause risks (e.g., technical debt), and does not promote knowledge reuse throughout an organization. Thus, there is a need to bring discipline to agile risk management. This study focuses on bringing such discipline to organizations that conduct multiple projects to develop software products using ASD, specifically, the Scrum framework, which is the most popular way of adopting ASD. For this purpose, we developed a novel solution that was articulated in partnership with an industry partner. It is a process to complement the Scrum framework to use a recommender system that recommends risks and response plans for a target project, given the risks registered for similar projects in an organization's risk memory (i.e., database). We evaluated the feasibility of the proposed recommender system solution using pre-collected datasets from 17 projects from our industry partner. Since we used the KNN algorithm, we focused on finding the best configuration of k (i.e., the number of neighbors) and the similarity measure. As a result, the configuration with the best results had k = 6 (i.e., six neighbors) and used the Manhattan similarity measure, achieving precision = 45%; recall = 90%; and F1-score = 58%. The results show that the proposed recommender system can assist Scrum Teams in identifying risks and response plans, and it is promising to aid decision-making in Scrum-based projects. Thus, we concluded that our proposed recommender system-based risk management process is promising for helping Scrum Teams address risks more efficiently.