Software risk management research papers
Software risk management pdf
After this introductory section, this paper is organized as follows: Section 2 presents main concepts about risk management in multiple project environments; Sections 3, 4 and 5 presents the application of the defined metodhology, introduced at Section 1. After the analysis of 63 articles, only 24 ones brought proposals of measures, metrics or indicators for risk assessment in projects. There is information about team size [19, 34, 38]. It refers to activities of software and system engineering, such as analysis and requirements specification, design and implementation, integrations of software and hardware components, and tests. According to PMBOK Guide 12 , this activity generates an artifact called Risk Management Plan, which describe policies, cost, responsibilities, schedule and all the necessary activities to execute the Risk Management. Risk analysis also organizes risks using a predefined categorization. The next subsections presents the research protocol adopted for this work. The choice of this taxonomy is due to the fact that it provides an organized way to categorize risk factors, and it is a consolidated report in software risk management. Likewise, the software development process must be aligned to the business models of these organizations in order to generate products that meet their needs, commonly inside constraints of cost, time, scope and quality. Offshoring increase the likelihood of failure. Another highlight is the presence of information related to Organizational factors, which demonstrates a strong influence of risks in the context of processes. The majority of the items used to measure these constructs are pro- posed for the first time in the literature. On the other hand, it is important to define different indicators considering also the complexity level of a project. These findings were combined with the identification of measurable risk factors, providing, thus, a set of categorized indicators for software development environments. Motivations levels is considered as an important measure for software development environments [30, 40], once the software processes specifically depends a lot from the staff.
However, despite the intention of previous studies  to examine these two dimensions of residual performance risk sepa- rately, no effort of this kind is recorded until today in the international literature. Boehm  proposed a software risk management framework that included the evaluation and control of risk and conducted a list with the top ten risks based on his personal professional experience.
Another point is that there were cases where the data in some papers was not so clear to get, so it could skew the results.
The first of these is Project Scope, which in this case is going to be studied through an indicator, Project Dura- tion [31,32].
Code: some works present source code-based metrics for software risk assessment.
Engineering product risks commonly derives from requirements that are hard to implement, inappropriate assessment of quality requirements or design specification and poor quality of code implementation.
Additionally 17 proposes a risk metric that combines the customization degree and dependence level between product components.
The selection of works from the areas of interest in step 2 involved the elimination of works that do not approach risk assessment in projects in the context of economics, management and computer science and the elimination of duplicates.
In this case, managers perceived high task uncertainty, equivocality, and coupling across sites as risk mitigation rather than risk taking. It also includes management issues. At the end of this step, for better understanding and definition of the proposal, the found information was categorized.
Software project risk management plan example
Four of them are going to be dis- cussed below, in a similar way as they were classified by Kulik and Weber . Houston  also proposed a list of 29 software development risk factors, considering them as the most important and frequently cited in the existent literature. In other words, there are several factors that, if not property managed, can contribute to project failure. And finally, in step 4 the full text of the remaining papers was read. In this context, this paper aims to define and propose indicators that are specific for environments of software projects in order to support risk assessment activities — risk identification and risk analysis. In line with Kwak and Ibbs study, Adams and Pinto  research states that risk management has not received sufficient attention and does not appear to be widely accepted within the soft- ware engineering community. And by Operational risk we just looked at ones that consider operational aspects of an enterprise, as a whole, especially continuous activities.
based on 18 review