Background
Contoso, Inc. is in the process of installing a hardware and software monitoring application and has a limited availability window for production installation.
Risk Identification
Using sound risk management discipline, Contoso conducted various risk identification discussions to produce a master risks list. Two of those risks are listed in the following table.
Table: Contoso Application Installation Risk ID 0001
Project ID |
Risk ID |
Root Cause |
Business Effect |
Risk |
Situation |
Operational Consequence |
Downstream Effect |
Table: Contoso Application Installation Risk ID 0002
Project ID |
Risk ID |
Root Cause |
Business Effect |
Risk |
Situation |
Operational Consequence |
Downstream Effect |
Risk Prioritization
Once these risks were identified, the project team then focused on risk prioritization.
Table: Contoso Prioritization of Risk ID 0001
Project ID |
Risk ID |
Root Cause |
Business Effect |
Exposure Analysis |
Probability |
Impact (1-5) |
Exposure |
Table: Contoso Prioritization of Risk ID 0002
Project ID |
Risk ID |
Root Cause |
Business Effect |
Exposure Analysis |
Probability |
Impact (1-5) |
Exposure |
Risk Planning and Tracking
Risks ID 0001 and ID 0002 were identified as the top risks for the project. The project team then conducted an exercise to devise mitigations, triggers, and contingencies as part of the risk planning and tracking step. Project team members were assigned responsibilities to continually monitor the risks assigned to them for potential changes and action items.
Table: Contoso Tracking of Risk ID 0001
Project ID |
Risk ID |
Root Cause |
Business Effect |
Mitigation |
Contingencies |
Triggers |
- |
Table: Contoso Tracking of Risk ID 0002
Project ID |
Risk ID |
Root Cause |
Business Effect |
Mitigation |
Contingencies |
Triggers |
- |
These two risks became the top risks list for the Contoso IT Operations Manager project. These risks were discussed at each OMR and various project status meetings. The purpose of this discussion was to discuss the progress of mitigation steps, to determine whether triggers were being fulfilled in the environment, and to ensure that the probability and impact levels were still properly set. This discussion was vital to the project to determine if contingencies identified in the master risks list needed to be acted upon to avoid service disruptions where possible.
Risk Exposure Analysis
As the project progressed, various mitigation activities began to change the probability of these risks. The relationship established with an external vendor provided the ability to obtain hardware within three days. However, the project team lost a key member due to shifting business priorities. The project team then modified the probability, which in turn also reduced the exposure of the risks as noted in the following table.
Table: Contoso Exposure Analysis of Risk ID 0001
Project ID |
Risk ID |
Root Cause |
Business Effect |
Modified Exposure Analysis |
Modified Probability |
Impact (1-5) |
Modified Exposure |
Table: Contoso Exposure Analysis of Risk ID 0002
Project ID |
Risk ID |
Root Cause |
Business Effect |
Modified Exposure Analysis |
Modified Probability |
Impact (1-5) |
Modified Exposure |