Project Risk Register
The Project Risk Register is a summary risk document. The risk register should contain a listing of all sources of risk, risk impact, risk probability, contingency plans, risk owner and the status of the risk. The risk identification, impact assessment and risk ranking, contingency planning and project execution tasks are all inputs to this document.
The risk register should be actively maintained throughout the project. The below example project risk register is based on a generic website development project.
|
Risk ID
|
Description
|
Risk Impact
|
Impact Description
|
Risk Probability
|
Risk Severity
|
Risk Contingency
|
Risk Owner
|
Status
|
Date
|
| 1 | Content will not be available when required |
4
|
Missed deadline will result in funding cut. |
3
|
12
|
Hire additional copy editors | Marketing | Currently recruiting for additional staff |
10/10/08
|
| 2 | Project resources may be reallocated for other (higher) priority project |
3
|
Resources are currently 100% committed to this project. Losing a resource would severely delay project. |
2
|
6
|
Work with Portfolio Manager to ensure resource availability | PM | Portfolio Manager will not reallocate staff. |
10/11/08
|
| 3 | End users may be resistant to new site workflow |
4
|
Customer feedback was instrumental in site design, but not all customers will like the site changes. May result in bad publicity or customer satisfaction issues. |
3
|
12
|
Implement online help facility. Provide additional customer support staff for transition. |
Support Manager | Additional staff will be brought online 1 month prior to release. Online help facility added as change request. |
9/9/08
|
| 4 | Data loss |
5
|
Data migration may result in loss of customer data. Customer data is key for day to day business operations. |
2
|
10
|
Revisit backup procedures. Execute manual backup prior to migration. |
Developers |