Abstract

With increasing competition in the software industry, software companies need to effectively manage the risks of software projects with minimal time and cost to deliver high quality products. High frequencies of warning errors and failures in software projects are indicative of human and financial costs in the software projects and teams. One of the reasons for the failure of software projects is the lack of risk management mechanism in the software development process, which can, in case of proper implementation of risk management, increase the success rate of such projects. In most projects, risk management activities are strongly confined to the adopted software methodology. Therefore, is needed a solution or model to overcome this constraint. Scrum is one of the most popular software development methodologies which has recently considered by software teams. This methodology seems not to have paid much attention to risk management. Focusing on this weakness, this research has been trying to provide a model for risk management with the participation of 52 Agile experts from six different countries using the Prince2 project management framework in Scrum methodology. The main goals of this model are to improve the coverage and appropriate risk management mechanism on software projects, increase the project’s success rate and to provide a good estimation of the required time, improve product quality and enhance quality parameters, such as the usability, flexibility, efficiency, and reliability.

Highlights

  • American Project Management Institute (PMI) introduced risk management as one of the twelve principal levels of the general knowledge project [1]

  • Risk management refers to all processes to identify, analyze, and respond to any uncertainty that includes maximizing the results of desirable events and minimizing adverse events results [2]

  • The heavyweight methodologies, nature of software development, lead to unrealistic estimates in the design phase and inability to adapt to unforeseen changes in projects

Read more

Summary

Introduction

Risk management refers to all processes to identify, analyze, and respond to any uncertainty that includes maximizing the results of desirable events and minimizing adverse events results [2]. Traditional project management (waterfall approach) is suitable for the projects that are well defined areas and it has less complexity and uncertainty [4]. More complex projects and business environments with unique needs and capabilities are changing [5]. One of the challenges of the traditional models, it needs very time and cost to writing the documentation of the project. The heavyweight methodologies, nature of software development, lead to unrealistic estimates in the design phase and inability to adapt to unforeseen changes in projects. It is needed an approach to identify and solve these challenges and risks [7]

Methods
Results
Discussion
Conclusion
Full Text
Published version (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