Skip to content
Related Articles

Related Articles

Improve Article

Short note on Risk Assessment and Risk Mitigation

  • Last Updated : 18 Aug, 2021

Software Risk is actually a problem that may or may not occurs that shows the uncertainty of risks but if occur, unwanted losses or threatening or consequences will occur. It is generally caused due to a lack of incomplete information, control, or time. Risk Assessment and Risk Mitigation is a process in which identifying, assessing, and mitigating risk takes place to scope, schedule, cost, and quality of the project. 
 

Risk Assessment : 
 

Risk assessment simply means to describe the overall process or method to identify risk and problem factors that might cause harm. It is actually a systematic examination of a task or project that you perform to simply identify significant risks, problems, hazards, and then to find out control measures that you will take to reduce risk. The best approach is to prepare a set of questions that can be answered by project managers in order to assess overall project risks. 

Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.

 

These questions are shown below: 



  • Will the project get proper support from the customer manager?
  • Are end-users committed to software that has been produced?
  • Is there a clear understanding of the requirements?
  • Is there an active involvement of customers in the requirement definition?
  • Are the expectations set for the product are realistic?
  • Is project scope stable?
  • Are there team members with the required skills?
  • Are project requirements stable?
  • Does technology used for software is known to developers?
  • Is the size of the team sufficient to develop the required product?
  • Is that all customers know the importance of the product/requirements of the system to be built?

Thus, the number of negative answers to these questions represents the severity of the impact of risk on the overall project. It is not about creating or making a large number of work papers, but rather simply identify and find out measures to control risks in your workplace. 
 

Risk Mitigation : 
 

Risk mitigation simply means to reduce adverse effects and impact of risks that are harmful to project and Business continuity. It includes introducing measures and step taken into a project plan to mitigate, reduce, eliminate, or control risk. Risk mitigation means preventing risks to occur (risk avoidance). 
Following are measures and steps to be taken for mitigating risks: 
 

  • Communicate with concerned staff to find probable risks.
  • Identify and eliminate all those causes and issues that can create risk before the beginning of project work.
  • Develop policy in an organization that will help to continue the project even though some staff leaves the organization.
  • Everybody in the project team should be acquainted i.e. should be aware of and familiar with current development activity.
  • Maintain corresponding documents in a timely manner. This documentation should be strictly followed as per standards set by the organization.
  • Conduct timely reviews in order to speed up work.
  • For conducting every critical activity during software development, provide additional staff is required.

Risk management:

  • Maintain a worldwide perspective: view software risks within the context of a system and therefore the business drawback planned to solve.
  • Take an advanced view: ink regarding the risk which can occur in the longer term and make future plans for managing the future events.
  • Encourage open communication: Encourage all the stakeholders and users for suggesting risks at any time.
  • Integrate: A thought of risk should be integrated into the software process.
  • Emphasize never-ending process: Modify the known risk than than a lot of info is understood and add new risks as higher insight is achieved.
  • Develop a shared product vision: If all the stakeholders share a similar vision of the software then it’s easier for better risk identification.
  • Encourage teamwork: whereas conducting risk management activities pool the skills and knowledge of all stakeholders.

 

My Personal Notes arrow_drop_up
Recommended Articles
Page :