Open In App

Essential Activities of Risk Management

Last Updated : 24 Mar, 2022
Like Article

Risk management is the area which tries to ensure that the impact of risks on cost, quality and schedule is minimized. The main purpose of risk management is to identify and manage the risks associated with a software project and solve the problem. Estimating the risks that can affect the project schedule or the quality of the software being developed and taking action to avoid the risk is the important task of a project manager. Identifying and preparing plans to reduce their impact on the project is called risk management. The basic motivation of risk management is to avoid disaster or heavy losses. The risk can be categorised as follows.

  1. Project Risks : These are the risks which affect the project schedule or resources.
  2. Product Risks : These are the risks which affect the quality or performance of the being developed.
  3. Business Risks : These are the risks which affect the organization developing or procuring the software.

This classification is not a special classification. If an experienced programmer leaves a project then it is a project risk because the delivery of the system may be delayed, the product may be a risk because the replacement may not be a seasoned one and therefore may be mistakes and business. Risk management is very important for software projects due to the inherent uncertainties that most projects face. The process of risk management is shown in fig. The process of risk management involves several stages are as follows-

  1. Risk Identification : In this stage, the possible project, product and business risks are identified.
  2. Risk Analysis : In this stage or process, the likelihood and consequences of these risks assessed.
  3. Risk Planning : In this stage, risk avoidance in either planned to affect the plan or mitigate its effects on the project.
  4. Risk Monitoring : In this stage, risk assessment is done continuously and the risk reduction plan is revised as more information about risk is available.

Like all other project planning, the risk management process is an iterative process that continues throughout the project. Risk management process results should be documented in a risk management plan. This should include a discussion of the risks that the project faces, analyzing these risks and requiring plans to manage these risks.It may also include some results of the risk management. The risk management has to deal with identifying the undesirable events that may occur, the likelihood of them occurring and the losses that occur when undesirable events occur. knowing this, strategies can be devised to reduce the possibility of reducing the risk or impact of the content. Therefore, risk management revolves around risk assessment and risk control. These are top 10 item techniques for managing them:

S.No> Risk Item Risk Management Techniques
(1) Personnel shortfalls Staffing with top talent; Job matching; Team building; Key-personnel agreement; Training; Prescheduling key people.
(2) Unrealistic schedules and budgets Detailed multisource cost and schedule estimation; Design to cost; Incremental development; Software reuse; Requirements scrubbing.
(3) Developing the wrong software functions Organization analysis; Mission analysis; OPS concept formulation; User surveys; Prototyping; Early users’ manuals.
(4) Developing the wrong user interface Prototyping; Scenarios; Task analysis; User characterization (functionality, style, workload).
(5) Gold plating Requirements scrubbing; Prototyping; Cost benefit analysis; Design to cost.
(6) Continuing stream of requirements changes High change threshold; Information hiding; Incremental development (defer changes to later increments).
(7) Shortfalls in externally furnished components Benchmarking; Inspection; Reference checking; Compatibility analysis.
(8) Shortfalls in externally performed tasks Reference checking; preaward audits; Awardfee contracts; Competitive design or prototyping teambuilding.
(9) Real time performance shortfalls Simulation; Benchmarking; Modeling; Prototyping; Instrumentation; Tuning.
(10) Straining computer science capabilities Technical analysis; Cost-benefit analysis; Prototyping; Reference checking.

Previous Article
Next Article

Similar Reads

Short note on Risk Assessment and Risk Mitigation
Software Risk is a problem that may or may not occur that shows the uncertainty of risks but if occurs, unwanted losses threats, or consequences will occur. It is generally caused due to a lack of incomplete information, control, or time. Table of Content What is Risk Assessment? What is Risk Mitigation?Risk managementRisk Assessment and Risk Mitig
3 min read
Project Management Process Activities
Principles of Project Management Process Activities : Project management is the use of methods, tools and processes to effectively plan and execute projects. Successful project management uses teams and resources to complete project tasks within time, cost and scope. The purpose of a project is defined by the client or stakeholders, and the project
4 min read
Integrating Risk Management in SDLC | Set 1
The Software Development Life Cycle (SDLC) is a conceptual model for defining the tasks performed at each step of the software development process. This model gives you a brief about the life cycle of Software in the development phase. In this particular article, we are going to discuss risk management in each and every step of the SDLC Model. Step
8 min read
Integrating Risk Management in SDLC | Set 2
Prerequisite: Integrating Risk Management in SDLC | Set 1 We have seen the Risk Management Techniques in SDLC which we have discussed Preliminary Analysis, System Analysis, and Requirement Definition part. In this article, we will be discussing the System Design and Development phase of the Software Development Life Cycle (SDLC). We will discuss ho
9 min read
Integrating Risk Management in SDLC | Set 3
Prerequisite - Integrating Risk Management in SDLC | Set 1, and Set 2. We have already discussed the first four steps of the Software Development Life Cycle. In this article, we will be discussing the remaining four steps: Integration and System Testing, Installation, Operation and Acceptance Testing, Maintenance, and Disposal. We will discuss Risk
9 min read
Risk Mitigation, Monitoring, and Management (RMMM) plan
RMMM Plan : A risk management technique is usually seen in the software Project plan. This can be divided into Risk Mitigation, Monitoring, and Management Plan (RMMM). In this plan, all works are done as part of risk analysis. As part of the overall project plan project manager generally uses this RMMM plan. In some software teams, risk is document
4 min read
Steps of Risk Management Process
Risk Management is an important part of project planning activities. It involves identifying and estimating the probability of risks with their order of impact on the project. Risk Management Steps: Some steps need to be followed to reduce risk. These steps are as follows: 1. Risk Identification: Risk identification involves brainstorming activitie
2 min read
What is Risk Management?
A risk is a probable problem; it might happen, or it might not. There are main two characteristics of risk. Uncertainty: the risk may or may not happen which means there are no 100% risks.Loss: If the risk occurs in reality, undesirable results or losses will occur.In this Article we will understand Risk Management in detail. Table of Content What
7 min read
Principles of Risk Management and Paradigm
Risk Management is an approach that helps in managing and making the best use of the available resources. A computer code project may be laid low with an outsized sort of risk so as to be ready to consistently establish the necessary risks that could have an effect on a computer code project. Table of Content What are the Principles of Risk Managem
4 min read
Various Activities of SDLC
Software Development Life Cycle (SDLC), as name suggests, is a blueprint or a process for entire project that is used by the software industry to design, develop, and test high-quality software. This blueprint or process includes some common stages like requirement gathering and analysis, software design, coding and implementation, testing, develop
2 min read