Risk Management is an important part in project planning activities. It involves identifying and estimating the probability of risks with their order of impact on the project.
Risk Management Steps:
There are some steps which need to be followed in order to reduce risk. These steps are as follows:
1. Risk Identification:
Risk identification involves brainstorming activities. it also involves preparation of risk list. Brainstorming is a group discussion technique where all the stakeholders meet together. this technique produces new ideas and promote creative thinking.
Preparation of risk list involves identification of risks that is occurring continuously in previous software projects.
2. Risk Analysis and Prioritization:
It is a process which consist of following steps:
- Identifying the problems causing risk in projects
- Identifying the probability of occurrence of problem
- Identifying the impact of problem
- Assigning values to step 2 and step 3 in the range of 1 to 10
- Calculate the risk exposure factor which is product of values of step 2 and step 3
- Prepare a table consisting of all the values and order risk on the basis of risk exposure factor
|Risk No||Problem||Probability of occurrence of problem||Impact of problem||Risk exposure||Priority|
|R1||Issue of incorrect password||2||2||4||10|
|R2||Testing reveals lot of defects||1||9||9||7|
|R3||Design is not robust||2||7||14||5|
3. Risk Avoidance and Mitigation:
The purpose of this technique is to altogether eliminate the occurrence of risks. so the method to avoid risks is to reduce the scope of projects by removing non-essential requirements.
4. Risk Monitoring:
In this technique risk is monitored continuously by reevaluating the risks, the impact of risk and probability of occurrence of risk.
This ensures that:
- Risk have been reduced
- New risk are discovered
- Impact and magnitude of risk are measured
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.