Abstract
The distributed Agile development approach has been accepted by software companies due to its promised benefits. However, due to the controversial nature of distributed and Agile development, significant challenges arise from spatial, temporal, social, and cultural differences between distributed teams. Scrum, as the most popular Agile methodology, assumes that team members work together in the same room. But this principle does not apply in a realistic scenario where Scrum teams are distributed in different locations. Hence, proposing a risk management framework is necessary in order to succeed such teams. The purpose of this research was to propose a risk management framework in Scrum using the PRINCE2 methodology, which includes the perceived risks in distributed Scrum projects and their causes and roots for managing these risks. By embedding distributed Scrum in delivery layer of PRINCE2 and considering perceived risk factors, along with a hybrid model, a risk management framework was suggested. This framework has been used in a case study, and the results showed its proper functionality in detecting and eliminating potential risks in the case under study. Also, using this framework led to higher team efficiency in terms of increasing the number of completed user stories in each sprint.
Highlights
Risk management in software development as one of the pillars of software project management has always been a serious concern of researchers
Global experiences have shown that the success of these projects depends largely on proper planning and preparedness to reduce potential risks
Due to some inconsistencies, this approach is subject to significant challenges and risks, which will bring some kind of risk in software development [2]
Summary
Risk management in software development as one of the pillars of software project management has always been a serious concern of researchers. Global experiences have shown that the success of these projects depends largely on proper planning and preparedness to reduce potential risks. This is mostly because software risk management involves approaches, processes, and tools that can reduce potential challenges in the management of risks [1]. Organizations use the hybrid approach including Agile software development (ASD) and distributed software development (DSD), which is called distributed Agile development (DAD), to develop better software products with better quality, time, and cost use. This approach helps to get the benefits of Agile and distributed development simultaneously. The distribution of project stakeholders in the global software development (GSD) projects with the time period, geography, and culture often results in some of the challenges or risks
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
