Risk management in software. In the field of seeking to formalize knowledge aimed at minimizing or avoiding risks in software development projects, through the generation of principles and good practices of realistic application.
Summary
[ hide ]
- 1 Definition
- 2 Risk categories
- 3 Strategies against risk
- 4 Stages for dealing with risks
- 5 Importance
- 6 Sources
Definition
Risk management in the field of the software seeks to formalize knowledge – oriented minimization or avoidance of risks in projects of software development through the generation of principles and good practices application. Different risk management approaches have been proposed and used since Boehm attracted the software engineering community to risk management. In recent years it has been evidenced that few organizations still use explicit and systematic specific methods to manage risks in their software projects.
Risk categories
- The risks of the project, which threaten the plan.
- Technical risks, which threaten quality and time planning.
- Business risks, which threaten the viability of the project or product.
Another categorization to consider based on your knowledge of them:
- Known risks (those that are discovered in evaluations).
- Predictable risks (extrapolated from experience).
Unpredictable risks (they can happen, but it is very difficult to identify them in advance).
Risk strategies
- Reactive, whose method is to assess the consequences of the risk when it has already occurred (it is no longer a risk) and act accordingly. This type of strategy has negative consequences, by putting the project in jeopardy.
- Preactive, which apply the method of prior and systematic evaluation of the risks and their possible consequences, at the same time that they make up contingency plans to avoid and minimize the consequences.
Consequently, this type of strategy allows for a shorter reaction time to the appearance of unpredictable risks. It is considered that the most feasible strategy to face risks is proactive and it is considered necessary to carry out risk analyzes early, systematically, formally and in depth.
Stages for dealing with risks
Risk management is an iterative process that is applied throughout the project and is developed in four stages:
- Risk identification.
- Risk analysis.
- Risk planning.
- Risk supervision.
The results of risk management should be documented in a risk management plan.
Importance
In order to produce what the client requires, within the requested period and adjusted to the assigned budget, it is necessary to develop a process that includes, from the earliest stage, the management of the risks associated with the requirements, so as to contribute to the gradual improvement development process and management of a software project that achieves customer satisfaction.
The identification and management of the risks associated with the software requirements, individual and groups of them, from the requirements engineering phase can allow them to be minimized, evaded and controlled. The proactive confrontation of the risks that may affect the development or the quality of the requirements and the actions to avoid them, would allow to minimize problems that persist in software development. Of greater importance are the risks associated with the main quality characteristics of the requirements
