Risk management in the software life cycle: A systematic literature review

Abstract

Risk management (RM) plays a key role in project management, as it allows identification and prompt management of threats that may arise during project execution. Furthermore, project management within the software industry is evolving rapidly nowadays, a fact that implies new challenges, because the emergence and use of fresh approaches has brought a greater degree of complexity to the RM process. The objective of this paper is to carry out a systematic literature review (SLR) in the field of software risk, in an attempt to characterize and present the state of the art of this field, identifying gaps and opportunities for further research. From the analysis of the results of this SLR it could be observed that interest on the part of the scientific community has turned away from the definition of research work that addressed an integrated risk management process, to pay attention to work that concentrates on specific activities of this process. It was also possible to see that there is a clear lack of scientific rigour as regards the process of validation in the different studies, and a deficiency in the use of standards or of de facto models to define these.

Crisis and Risks in Engineering Project Management: A Review

“…For Raz et al (2002) and Pinheiro et al (2006) more numerous the project's uncertainties, the greater the risks are taken by him, so risk management becomes essential for the project management. Therefore, risk management aims to identify potential threats that may occur, thus reducing any negative impact on the project's objectives and success (Masso et al, 2020).…”

Identificación de estructuras sintácticas en corpus: un enfoque para encontrar áreas de conocimiento en disciplinas dirigidas por proyectos

“…Similarly, Masso et al [13] study risk in software projects by performing a systematic literature review about the topic by including guides like PMBOK, PRINCE2, CMMI, and ISO 31000. Even though the authors are only collecting the information related to the topic, they use a more objective way to analyze the information by using the co-occurence of words.…”

“…Raz and Hillson [12] compare some standards for managing risks, including PMBOK. Finally, Masso et al [13] perform a systematic literature review about software risk management for comparing the usage of the term among guides like PMBOK, PRINCE2, CMMI, and ISO 31000.…”

Improving Software Project Management by Applying Agile Methodologies: A Case Study

“…The software industry's growth began in the early 90s with the incursion of emerging economy countries that focused their strategies on the development of customized software, responding to the needs of a specific market niche [1]. In this context, organizations' management allied with software information systems fundamental to support the organization's strategic leadership in the market; this generates permanent demands for software engineering, especially in terms of quality [2].…”