Successfully reported this slideshow.
Upcoming SlideShare
×

# Risk management program oregon sql

This may be a temporary upload. Provided to lend an example for a proposal to give a talk on risk management for OregonSQL.

See all

### Related Audiobooks

#### Free with a 30 day trial from Scribd

See all
• Full Name
Comment goes here.

Are you sure you want to Yes No
• Be the first to comment

• Be the first to like this

### Risk management program oregon sql

1. 1. Risk Management 2 Verticals up to Program-Level...and Back Danny Rehr November 7, 2018 Manager Data Analyst Database Admin Program-Level Project-Level
2. 2. Risk Management A methodology for identifying, rating, analyzing, and mitigating risks. Risk Problem Any identiﬁed situation that could negatively impact a project, process, procedure or task from being completed successfully. An unmitigated risk. Deﬁnitions Risk Identiﬁcation Brainstorming any occurrence, factor, limitation, inﬂuence or error--man-made or naturally-occurring--that could serve as a negative impact to a stated goal. Mitigation Strategy An action(s) or activity(ies) that, if coordinated and/or implemented, would either resolve or severely limit the impact of a risk. Recommendation: review and update 1-2 times per week, more for major risks.
3. 3. How to Score Risks Probability What is the likelihood that this risk could become a problem? 1. Very Unlikely 2. Unlikely 3. Probable 4. Likely 5. Very Likely Magnitude If this risk were to become a problem, how badly would be its eﬀect(s)? 1. Negligible 2. Moderate 3. Signiﬁcant 4. Severe 5. Catastrophic Ex. Probability = 1 Probability = 4 Magnitude = 3 Magnitude = 3 Score = 3 Score = 12 5 5 10 15 20 25 4 4 8 12 16 20 3 3 6 9 12 15 2 2 4 6 8 10 1 1 2 3 4 5 1 2 3 4 5 Probability Magnitude Risk Score = Probability Magnitude
4. 4. Risk Suggestion: color this field the risk color: green, yellow, red. If/Then If [this happened], then [this would be the impact]. Score Probability Magnitude Trigger What would trigger the “If” (from above)? Date of Impact When “Then” (from above) happen? Mitigation Strategy Risk Form (Details) (Escalating the risk to a manager may be the only mitigation strategy!)
5. 5. Project vs. Program A Risk To What? What Does the Organization Value?
6. 6. Manager Database Admin Data Analyst Program-Level Project-Level A Risk To What? What Does the Organization Value?
7. 7. Communicating Risk Packaging information for awareness, prioritization and tracking
8. 8. 20 Migration to new platform 20 Security 16 Cloud vs. On-Prem integration, redundancy 15 Subunit replacement project (post-migration electrical outages) 6 Vacation coverage 25 5G bandwidth; increase in data collected 16 Demand for real-time data from new system. 12 Department downsizing (new project surge) 8 Data accuracy from legacy system migration 4 Collaborative work with new-hire (consistency) Manager Database Admin Data Analyst Program-Level Project-Level
9. 9. SCORE RISK DB ADMIN’s risk ANALYST’s risk RISK TO BOTH 25 5G bandwidth; increase in data collected X 16 Demand for real-time data from new system. X 16 Cloud vs. On-Prem integration, redundancy X 15 Subunit replacement project (post-migration electrical outages) X 12 Department downsizing (new project surge) X 6 Vacation coverage X Escalated Risks Any risks that are RED and/or that are out of the control* of the Project-Level leader must be escalated - if for no other reason than simple awareness; otherwise, it is expected that the Program-Level leader will mitigate the risk, or escalate it him or herself. *Note the green risk. Even a low probability, low magnitude risk may be escalated as it is out of the purview of the Project-Level leader. ManagerProgram-Level
10. 10. Risk Mitigation In all likelihood, risk mitigation at the Program-Level will require 1 of 4 resolutions. 1. The Program-Level leader will mitigate him or her self. 2. The Program-Level leader will escalate to his or her manager. 3. The Program-Level leader will work directly with the Project-Level leader to mitigate. 4. The Program-Level leader will pull resources unavailable to the Project-Level leader to coordinate mitigation, e.g. collaborate with a diﬀerent department, mandate resources from other departments to get involved. ManagerProgram-Level
11. 11. Summary 1. If risks are not mitigated, then they become problems. 2. Risks must be identiﬁed. a. One of the most important aspects of risk management is awareness. 3. Score and prioritize risks. 4. Mitigate risks through active measures. a. Some risks cannot be mitigated at the Project-Level. i. Escalation may be the only mitigation strategy. 5. A RISK TO WHAT?? a. What does the organization and/or leadership value such that one scenario is risky and another is not? i. Ramiﬁcations are diﬀerent at the Program and Project levels!