Slides - Week 8 PDF
Slides - Week 8 PDF
Slides - Week 8 PDF
• Please:
2–1
Review from Last Classes/Exam
2–2
Where We Are Now
7–3
What is a Risk?
7–4
Risks
7–5
Risk Management Process
• Risk Management
– A proactive attempt to recognize and manage internal
events and external threats that affect the likelihood
of a project’s success
• What can go wrong? (risk event)
7–6
The Risk Event Graph
FIGURE 7.1
7–7
Risk Management’s Benefits
7–8
The Risk
Management
Process
FIGURE 7.2
7–9
Managing Risk
• Step 1: Risk Identification
– Generate a list of possible risks through
brainstorming, problem identification, and risk
profiling
• Macro risks first, then specific events
FIGURE 7.3
7–11
Partial Risk Profile for Product Development Project
FIGURE 7.4
7–12
Defined Conditions for Impact Scales of a Risk on Major
Project Objectives (Examples for negative impacts only)
FIGURE 7.5
7–13
Risk Assessment Form
7–14
Risk Severity Matrix
Failure Mode and Effects Analysis (FMEA)
Impact × Probability × Detection = Risk Value
User Interface
4 Backlash problems
Likelihood
System
2
freezing
Hardware
1 malfunc-
tioning
1 2 3 4 5 FIGURE 7.7
Impact
7–15
Managing Risk (cont’d)
• Step 3: Risk Response Development
– Mitigating Risk
• Reducing the likelihood an adverse event will occur
• Reducing impact of adverse event
– Avoiding Risk
• Changing the project plan to eliminate the risk or condition
– Transferring Risk
• Paying a premium to pass the risk to another party
• Requiring Build-Own-Operate-Transfer (BOOT) provisions
– Accept Risk
• Making a conscious decision to retain the risk
7–16
Contingency Planning
• Contingency Plan
– An alternative plan that will be used if a possible
foreseen risk event actually occurs
– A plan of actions that will reduce or mitigate the
negative impact (consequences) of a risk event
7–17
Risk Response Matrix
FIGURE 7.8
7–18
Risk and Contingency Planning
• Technical Risks
– Backup strategies if chosen technology fails
– Assessing whether technical uncertainties
can be resolved
• Schedule Risks
– Use of slack increases the risk of a late project finish
– Imposed duration dates (absolute project finish date)
– Compression of project schedules due to a shortened
project duration date
7–19
Risk and Contingency Planning (cont’d)
• Costs Risks
– Time/cost dependency links: costs increase when
problems take longer to solve than expected
– Price protection risks (a rise in input costs) increase if
the duration of a project is increased
• Funding Risks
– Changes in the supply of funds for the project can
dramatically affect the likelihood of implementation or
successful completion of a project
7–20
Risk Management Exercise
7–21
Opportunity Management Tactics
• Exploit
– Seeking to eliminate the uncertainty associated with an
opportunity to ensure that it definitely happens
• Enhance
– Taking action to increase the probability and/or the positive
impact of an opportunity
• Share
– Allocating some or all of the ownership of an opportunity to
another party who is best able to capture the opportunity for the
benefit of the project
• Accept
– Being willing to take advantage of an opportunity if it occurs, but
not taking action to pursue it
7–22
Contingency Funding
• Contingency Funds
– Funds to cover project risks—identified and unknown
• Size of funds reflects overall risk of a project
– Budget reserves
• Are linked to the identified risks of specific work packages
– Management reserves
• Are large funds to be used to cover major unforeseen risks
(e.g., change in project scope) of the total project
7–23
Contingency Fund Estimate ($000s)
TABLE 7.1
7–24
Managing Risk (cont’d)
• Step 4: Risk Response Control
– Risk control
• Execution of the risk response strategy
• Monitoring of triggering events
• Initiating contingency plans
• Watching for new risks
7–25
Change Management Control
• Sources of Change
– Project scope changes
– Implementation of contingency plans
– Improvement changes
7–26
Change Control System Process
7–27
The Change
Control Process
FIGURE 7.9
7–28
Benefits of a Change Control System
1. Inconsequential changes are discouraged
by the formal process
2. Costs of changes are maintained in a log
3. Integrity of the WBS and performance measures
is maintained
4. Allocation and use of budget and management
reserve funds are tracked
5. Responsibility for implementation is clarified
6. Effect of changes is visible to all parties involved
7. Implementation of change is monitored
8. Scope changes will be quickly reflected in baseline
and performance measures
7–29
Key Terms
7–30
For Next Class
5–31