project cont.

complete the risk plan forms, and change plan, and the second project status report
risk_management_plan_template.doc
10b_risk_response_plan_template.xls
11_change_management_plan_template.doc
projectstatusrpt_template.docx
Unformatted Attachment Preview
Put your
logo here
Put your
organization
name here
Project Risk Management Plan Template
Rev. 2.2, 4/2/2006
PROJECT RISK MANAGEMENT PLAN
Project Name:
Prepared by:
Date (MM/DD/YYYY):
Risk Management Strategy
1. Define the risk management methodology to be used. Section 1 of this table defines your risk
management process. The risk management process is scalable to ensure that the level, type, and visibility of risk
management are commensurate with both the risk and the importance of the project. Modify the text in this section to fit
your process.

Risk Identification – Identify risks through discussion with all major stakeholders. Also use the Risk
Assessment Questionnaire and Project Planning Risk Assessment Checklist, augmented to include other project
specific risks, as appropriate.

Risk Categorization – Group the risks into categories by using the Risk Assessment Questionnaire. The
project manager can create additional categories, as required.

Risk Probability and Impact Assessment – Enter all risks into the Risk Response Plan document. For
each risk identified, assess the risk event in terms of likelihood of occurrence (Risk Probability) and its effect on
project objectives if the risk event occurs (Risk Severity = Impact Score). This information will be used to
prioritize the risk using established threshold criteria.

Risk Prioritization – Risks that meet the threshold criteria will be so noted in the Risk Register. These Risks
will be prioritized.

Risk Response Planning – For each risk in the Risk Register that is above the Risk Threshold:

Determine the options and actions to reduce the likelihood or consequences of impact to the project’s
objectives

Determine the response based on a cost/benefit analysis (cost vs. expected effectiveness)

Describe the actions to be taken to mitigate the risk

Describe the Signs and Symptoms that may be indicators of Risk Event occurrence

Describe the actions to be taken when the risk event occurs (contingency plan)

Assign responsibilities for each agreed-upon response

Assign a “due date” where risk responses are time-sensitive

Determine impact on project budget and schedule and make appropriate changes or additions to the project
plan.

Incorporate this information into the Risk Register
Template source: http://www.cvr-it.com
Page 1
Put your
logo here
Put your
organization
name here
Project Risk Management Plan Template
Rev. 2.2, 4/2/2006
Risk Management Strategy

Risk Response Tracking:

Document the dates and the actions taken to mitigate the risk

Document the actions taken when the risk event occurred (contingency plan)

Document any subsequent actions taken

Incorporate this information into the Risk Register
Risk Monitoring – Establish systematic reviews and schedule them in the project schedule, ensuring the
following reviews:

Ensure that all requirements of the Risk Management Plan are being implemented

Assess currently defined risks as defined in the Risk Register

Evaluate effectiveness of actions taken

Identify status of actions to be taken

Validate previous risk assessment (likelihood and impact)

Validate previous assumptions

State new assumptions

Identify new risks

Track risk response

Establish communications
Risk Control

Validate mitigation strategies and alternatives

Take corrective action when actual events occur

Assess impact on the project of actions taken (cost, time, resources)

Identify new risks resulting from risk mitigation actions

Ensure the Project Plan (including the Risk Management Plan) is maintained

Ensure change control addresses risks associated with the proposed change

Revise the Risk Assessment Questionnaire, Project Planning Risk Assessment Checklist and other risk
management documents to capture results of mitigation actions.

Revise Risk Register

Establish communications
2. Define assumptions that have a significant impact on project risk:
3. Define the roles and responsibilities unique to the risk management function:

Risk Management Team:
Risk Response Tracking Coordinator:
Template source: http://www.cvr-it.com

Page 2
Put your
logo here
Put your
organization
name here
Project Risk Management Plan Template
Rev. 2.2, 4/2/2006
Risk Management Strategy
4. Define risk management milestones (insert rows as needed):
Milestone

Risk Management Plan approved

Risk Assessment Questionnaire tailored to project

Risk Assessment Questionnaire and Project Planning Risk Evaluation
Checklist complete

Risk Management Reviews scheduled
Date
(MM/DD/YYYY)
5. Define risk rating/scoring techniques (The project will rate each identified risk (e.g., Impact Score = High,
Medium, Low) based on the likelihood that the risk event will occur and the effect on the project’s objectives if the risk
event occurs. This will be a subjective evaluation based on the experience of those assigned to the project’s risk
management team.) :
Default rating/scoring system is as follows:
Impact Score can be rated as 1, 3, 5, 7, or 9 (1 = Very Low, 9 = Very High).
Probability can be rated as 0.1, 0.3, 0.5, 0.7 or 0.9 (0.1 = Very Low, 0.9 = Very High).
6. Establish risk thresholds (Modify the text below to show how the project team will plan for risk events, e.g.
“The project will establish risk responses for risk events that have been determined to have a rating of ‘High’.”)
Risk priority is determined by calculating a Risk Score (= Impact * Probability) and then comparing that Risk Score
to Priority thresholds.
Based on the scoring system in section 5., the lowest possible Risk Score is 1 * 0.1 = .01 and the highest possible
Risk Score is 9 * 0.9 = 8.1
The following Priority Thresholds will be used to establish Risk Priority:
Green (Low Risk) <= 2.5 Yellow (Medium Risk) between 2.5 and 6.5 Red (High Risk) >= 6.5
❑
The Project Team develops a full response plan for each item rated as High risk. These risks are watched
closely.
❑
The Project Team should create a response plan for any Medium risk item where they deem it necessary.
However, in general no response plan is required for Medium risk items. Medium risks are monitored on a
regular basis.
❑
No action is required for Low risk items except to keep a watch on them as the project progresses.
All Risk items with a response plan are to be entered into the Risk Register document.
7. Define risk communications:
Template source: http://www.cvr-it.com
Page 3
Put your
organization
name here
Put your
logo here
Project Risk Management Plan Template
Rev. 2.2, 4/2/2006
Risk Management Strategy
8. Define risk-tracking process:
Project Risk Management Plan Approval / Signatures
Project Name:
Project Manager:
I have reviewed the information contained in this Project Risk Management Plan and agree:
Name
Title
Signature
Date
The signatures above indicate an understanding of the purpose and content of this document by those
signing it. By signing this document, they agree to this as the formal Project Risk Management Plan
document.
Template source: http://www.cvr-it.com
Page 4
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Project Name:
Instructions:
Threat Priority Thresholds
High
Medium
1. Enter Impact and Probability Scores (or use default provided)
4.5
2. Enter Priority Cutoff scores for Threats
2
3. Enter Priority Cutoff scores for Opportunities
4. Enter risk impact and probability scores on the main worksheets. Color coding
indicates priority of Risks and Opportunities
Opportunity Priority Thresholds
Threats
Opportunities
= High Priority
= High Priority
High
4
Medium
2
= Medium Priority
= Medium Priority
= Low Priority
= Low Priority
Impact
Threats
Opportunities
9
0.9
2.7
4.5
6.3
8.1
8.1
6.3
4.5
2.7
0.9
7
0.7
2.1
3.5
4.9
6.3
6.3
4.9
3.5
2.1
0.7
5
0.5
1.5
2.5
3.5
4.5
4.5
3.5
2.5
1.5
0.5
3
0.3
0.9
1.5
2.1
2.7
2.7
2.1
1.5
0.9
0.3
1
0.1
0.3
0.5
0.7
0.9
0.9
0.7
0.5
0.3
0.1
0.1
0.3
0.5
0.7
0.9
0.9
0.7
0.5
0.3
0.1
Probability
Note: Be certain to fill out the Risk Management Plan before using this workbook. Available at www.cvr-it.com.
Risk Register [Rev. 1.5 1/15/2009]
Page 1 of 66
Printed on: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register [Rev. 1.5 1/15/2009]
Risk Register
Page 2 of 66
Your Organization
Name Here
Printed on: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register [Rev. 1.5 1/15/2009]
Risk Register
Page 3 of 66
Your Organization
Name Here
Printed on: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register
Your Organization
Name Here
Copyright 2009 CVR/IT Consulting LLCAll Rights Reserved
Risk Register [Rev. 1.5 1/15/2009]
Page 4 of 66
Printed on: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Threat Register
Project Name: 0
Impact
Score
Probability
Risk
Score
Detectability
Critical
Very High
8.1
Low
Very High
6.3
High
071123b
Very
Serious
Serious
Very High
4.5
Low
071210a
Moderate
Very High
2.7
High
071211a
Minor
Very High
0.9
Low
071222a
Moderate
High
2.1
High
080105a
Moderate
Low
0.9
Low
080109a
High
4.9
High
Low
2.1
Low
080111a
Very
Serious
Very
Serious
Serious
Med
2.5
0
0
0
0
0
0
0
0
0
0
0
0
0
Med
Risk Register [Rev. 1.5 1/15/2009]
Page 5 of 66
Risk ID
Example:
071111a
071123a
Risk Description
New technology presents IT with a steep
learning curve, could cause delay in
implementation
Sample data on this tab are displayed on
the ThreatChart tab
080109b
Impact
Area
Risk Cause
Schedule Staff do not have experinece in
this technology
Status
Assigned to
Active Joe Smith
Trigger Event
Staff does not obtain training;
early “prove feasibility” tasks
are not completed
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Threat Register
Project Name: 0
Risk ID
Risk Description
Impact
Area
Risk Cause
Impact
Score
Probability
Risk
Score
Detectability
Status
Assigned to
Trigger Event
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 6 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Threat Register
Project Name: 0
Risk ID
Risk Description
Impact
Area
Risk Cause
Impact
Score
Probability
Risk
Score
Detectability
Status
Assigned to
Trigger Event
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 7 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Threat Register
Project Name: 0
Risk ID
Risk Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Risk Cause
Impact
Score
Probability
Page 8 of 66
Risk
Score
Detectability
Status
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Threat Register
Project Name: 0
Risk ID
Risk Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Risk Cause
Impact
Score
Probability
Page 9 of 66
Risk
Score
Detectability
Status
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Threat Register
Project Name: 0
Risk ID
Risk Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Risk Cause
Impact
Score
Probability
Page 10 of 66
Risk
Score
Detectability
Status
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Results of formal analysis
Example:
071111a
Your Organization
Name Here
Risk Register
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Advanced training planned for 3 staff to
occur on 12/2/03
Date of Plan
Approval
04-Mar-06
Comments; Fallback plans
Example text
071123a
071123b
071210a
071211a
071222a
080105a
080109a
080109b
080111a
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 11 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Results of formal analysis
Your Organization
Name Here
Risk Register
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Date of Plan
Approval
Comments; Fallback plans
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 12 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Results of formal analysis
Your Organization
Name Here
Risk Register
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Date of Plan
Approval
Comments; Fallback plans
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 13 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Results of formal analysis
Risk Register [Rev. 1.5 1/15/2009]
Your Organization
Name Here
Risk Register
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Page 14 of 66
Date of Plan
Approval
Comments; Fallback plans
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Results of formal analysis
Risk Register [Rev. 1.5 1/15/2009]
Your Organization
Name Here
Risk Register
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Page 15 of 66
Date of Plan
Approval
Comments; Fallback plans
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Results of formal analysis
Your Organization
Name Here
Risk Register
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Date of Plan
Approval
Comments; Fallback plans
Copyright 2009 CVR/IT Consulting LLCAll Rights R
Risk Register [Rev. 1.5 1/15/2009]
Page 16 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register
Your Organization
Name Here
Do not remove or change these cells!
Threat Priority Thresholds
High
Medium
Opportunity Priority Thresholds
High
Medium
Risk Register [Rev. 1.5 1/15/2009]
4.5
2
4
2
Page 17 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register [Rev. 1.5 1/15/2009]
Risk Register
Page 18 of 66
Your Organization
Name Here
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register [Rev. 1.5 1/15/2009]
Risk Register
Page 19 of 66
Your Organization
Name Here
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register [Rev. 1.5 1/15/2009]
Risk Register
Page 20 of 66
Your Organization
Name Here
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register [Rev. 1.5 1/15/2009]
Risk Register
Page 21 of 66
Your Organization
Name Here
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk Register
Your Organization
Name Here
Copyright 2009 CVR/IT Consulting LLCAll Rights Reserved
Risk Register [Rev. 1.5 1/15/2009]
Page 22 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Example:
021111a
Opportunity Description
New technology presents IT with a real
opportunity, could shave weeks off of
implementation
Impact
Area
Schedule
Opportunity Cause
Impact
Score
Probability
Opportunity DetectaStatus
Score
bility
Very
High
Med
4.5
High
Very
High
Very
High
High
Very Low
0.9
Med
Low
2.7
Low
Very High
6.3
High
High
4.9
High
Med
3.5
High
Low
2.1
High
Very Low
0.7
Assigned to
Trigger Event
Active Joe Smith
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 23 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Impact
Area
Opportunity Cause
Impact
Score
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 24 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Impact
Area
Opportunity Cause
Impact
Score
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 25 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Opportunity Cause
Impact
Score
Page 26 of 66
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Opportunity Cause
Impact
Score
Page 27 of 66
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Opportunity Cause
Impact
Score
Page 28 of 66
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Opportunity Cause
Impact
Score
Page 29 of 66
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Your Organization
Name Here
Risk Register
Opportunity Register
Project Name: 0
Opportunity
ID
Opportunity Description
Risk Register [Rev. 1.5 1/15/2009]
Impact
Area
Opportunity Cause
Impact
Score
Page 30 of 66
Probability
Opportunity DetectaStatus
Score
bility
Assigned to
Trigger Event
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Example:
021111a
Signs and Symptoms
Vendor announces
availability of the new
product
Your Organization
Name Here
Risk Register
Results of formal
analysis
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Response Strategy
Expedite purchase of a sample of the new
technology
Date of Plan
Approval
04-Mar-06
Comments; Fallback plans
Example text
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 31 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Signs and Symptoms
Your Organization
Name Here
Risk Register
Results of formal
analysis
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Date of Plan
Approval
Comments; Fallback plans
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 32 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulting LLC
Risk ID
Signs and Symptoms
Your Organization
Name Here
Risk Register
Results of formal
analysis
Response Strategy
Contingency Reserve; Cost and
Schedule adjustments to Project
Plan
Date of Plan
Approval
Comments; Fallback plans
0
0
0
0
0
Risk Register [Rev. 1.5 1/15/2009]
Page 33 of 66
Print Date: 10/20/2019
Copyright 2006 CVR/IT Consulti …
Purchase answer to see full
attachment