Project Risk Management Overview
Project Risk Management Overview
PMP
Plan Risk Management
Monitor Risks
11. PROJECT
RISK MANAGEMENT
Presented by:
2 24 10 12 1
334
• Project team needs to know what level of risk exposure is acceptable in pursuitof
the project objectives. ( Risk thresholds).
TAILORING CONSIDERATIONS
• Project size.
• Project complexity.
• Project importance.
• Development approach.
336
Risk is considered when selecting the content of each iteration, and riskswill
also be identified, analyzed, and managed during each iteration.
01 PROJECT CHARTER
03
PROJECT DOCUMENTS
• Stakeholder register
01
EXPERT JUDGMENT
02 DATA ANALYSIS
• Stakeholder analysis
03 Meetings 33
%
95
%
95
%
340
Methodology.
Funding.
Timing.
Risk categories.
341
Risk Breakdown
Structure (RBS)
342
Definitions of risk probability and impacts. used to evaluate both threats and opportunities
by interpreting the impact definitions as negative for threats (delay, additional cost, and
performance shortfall) and positive for opportunities (reduced time or cost, and performance
enhancement).
343
Reporting formats. Reporting formats define how the outcomes of the Project Risk
Management process will be documented, analyzed, and communicated.
Tracking. Tracking documents how risk activities will be recorded and how risk
management processes will
be audited.
345
02
PROJECT DOCUMENTS
• Assumption log • Lessons learned register
• Cost estimates • Requirements documentation
• Duration estimates • Resource requirements
• Issue log • Stakeholder register
03
AGREEMENTS
04 PROCUREMENT DOCUMENTATION
01 EXPERT JUDGMENT
02 DATA GATHERING
• Brainstorming. to obtain a comprehensive list of individual project risks and sources of
overall project risk.
• Checklists. developed based on historical information and knowledge that has been
accumulated from similar projects and from other sources ofinformation.
• Interviews. interviewing experienced participants, stakeholders, and subject matter
experts to identify risks
03 DATA ANALYSIS
• Root cause analysis. to discover the underlying causes that lead to a problem, and
develop preventive action.
• Assumption and constraint analysis. To explores the validity of assumptions and
constraints to determine which pose a risk to the project
33
• SWOT analysis. examines the project from each of the strengths, weaknesses,
%
opportunities, and threats (SWOT) perspectives.
• Document analysis.
95
%
348
05 PROMPT LISTS
A prompt list is a predetermined list of risk categories that might give rise to individual
project risks and that could also act as sources of overall projectrisk.
common strategic frameworks for identifying sources of overall project risk
• PESTLE (political, economic, social, technological, legal, environmental),
• TECOP (technical, environmental, commercial, operational, political), or
• VUCA (volatility, uncertainty, complexity, ambiguity).
06 MEETINGS
(often called a risk workshop).
33
%
95
%
350
02 RISK REPORT
02
PROJECT DOCUMENTS
• Assumption log
• Risk register
• Stakeholder register
02
DATA GATHERING
03 DATA ANALYSIS
Risk data quality assessment. evaluates the degree to which the data about individual
project risks is accurate and reliable as a basis for qualitative risk analysis.
Risk probability and impact assessment. considers the likelihood that a specificrisk
will occur. Considers the potential effect project objectives ( schedule, cost, quality, or
performance). Impacts will be negative for threats and positive for opportunities.
33
%
95
%
354
06 DATA REPRESENTATION
Probability and impact matrix.
Hierarchical Charts
Where risks have been categorized using more than two parameters.
Ex: Bubble chart which displays three dimensions of data, where each risk is plotted
(bubble), and the three parameters are represented by the x-axis value, the y-axis value,
and the bubble size.
07 MEETINGS
33
%
95
%
356
95
%
357
33
%
95
%
358
02
PROJECT DOCUMENTS
• Assumption log • Milestone list
• Basis of estimates • Resource requirements
• Cost estimates • Risk register
• Cost forecasts • Risk report
• Duration estimates • Schedule forecasts
04
ORGANIZATIONAL PROCESS ASSETS
361
05 DATA ANALYSIS
Influence diagrams. represents a project or situation within the project as a setof entities,
outcomes, and influences, together with the relationships and effects betweenthem.
Simulation. Simulates the combined effects of individual project risks and other sources of
uncertainty to evaluate their potential impact on achieving project objectives performed using a
Monte Carlo analysis.
362
Influence Diagrams
363
33
%
95
%
365
Prototype
A company is trying to
determine if prototyping Pass: No Impact
is worthwhile on the
Expected Monetary
project
Value : P * I
02 PROJECT DOCUMENTS
• Lessons learned register • Risk register
• Project schedule • Risk report
• Project team assignments • Stakeholder register
• Resource calendars
04
ORGANIZATIONAL PROCESS ASSETS
369
02
DATA GATHERING
2. Avoid. when the project team acts to eliminate the threat or protect the project from its impact.
appropriate for high-priority threats with a high probability of occurrence and a largenegative impact.
4. Mitigate. action is taken to reduce the probability of occurrence and/or impact of a threat.
5. Accept. acknowledges the existence of a threat, but no proactive action is taken, appropriate for
low-priority threats.
370
1. Escalate.
2. Exploit. The exploit strategy may be selected for high-priority opportunities where the organization
wants to ensure that the opportunity is realized. by ensuring that it definitely happens, increasing the
probability of occurrence to 100%
3. Share. Sharing involves transferring ownership of an opportunity to a third party so that it shares
some of the benefit if the opportunity occurs.
5. Accept. Accepting an opportunity acknowledges its existence but no proactive action is [Link]
strategy may be appropriate for low-priority opportunities.
06
CONTINGENT RESPONSE STRATEGIES
It is appropriate for the project team to make a response plan that will only be executed undercertain
predefined conditions.
371
07
STRATEGIES FOR OVERALL PROJECT RISK
1. Avoid
2. Exploit.
3. Transfer/share.
4. Mitigate/enhance.
5. Accept
08 DATA ANALYSIS
• Alternatives analysis
• Cost-benefit analysis.
09
DECISION MAKING
372
02
PROJECT MANAGEMENT PLAN UPDATES
• Schedule management plan • Procurement management plan
• Cost management plan • Scope baseline
• Quality management plan • Schedule baseline
• Resource management plan • Cost baseline
02
PROJECT DOCUMENTS
• Lessons learned register
• Risk register
• Risk report
01
EXPERT JUDGMENT
33
%
95
%
95
%
376
11.6 Implement Risk Responses Output
01 CHANGE REQUESTS
02
PROJECT DOCUMENTS
• Issue log
• Lessons learned register
• Risk register
• Risk report
01
DATA ANALYSIS
04
ORGANIZATIONAL PROCESS ASSETS UPDATES
Project Management Professional
(Thanks)
Presented by: