- Risk register
A risk register is a tool commonly used in
project planning and organisational risk assessments. It is often referred to as a Risk Log (for eg inPRINCE2 ).This tool is widely used within
Risk Management for identifying, analysing and managing risks. In this context a project risk is essentially an uncertain event that, should it occur, will have an impact on the project (this could be positive or negative).It contains the information on the identified and collected project risks that the project team identifies when estimating and adjusting the activity durations for risks.
The project team considers the extent to which the effects of risks are included in the baseline duration estimate for each schedule activity, particularly the risks with high impact.
Example contents
A wide range of contents for a risk register exist and recommendations are made by the
Project Management Institute Body of Knowledge (PMBOK ) and PRINCE2 among others. In addition many companies provide software tools that act as risk registers. Typically a risk register contains:
* A description of the risk
* The impact should this event actually occur
* Theprobability of its occurrence
* A summary of the planned response should the event occur
* A summary of themitigation (the actions taken in advance to reduce the probability and/or impact of the event)
* The risks are often given a ranking with the highest priority risks clearly identified to all involved.Example Risk Register in table format
Risk Register for project "birthday party"
Useful terminology
In a "qualitative" risk register descriptive terms are used: for example a risk might have a "High" impact and a "Medium" probability.
In a "quantitative" risk register the descriptions are enumerated: for example a risk might have a "£1m" impact and a "50%" probability.
Contingent response - the actions to be taken should the risk event actually occur.
Contingency - the budget allocated to the contingent response
Trigger - an event that itself results in the risk event occurring (for example the risk event might be "flooding" and "heavy rainfall" the trigger)
ee also
*
Risk
*Event chain methodology
*Risk Breakdown Structure Literature
*cite book
author = Tom Kendrick
year = 2003
title = Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project
publisher = AMACOM/American Management Association
id = ISBN 978-0814407615
*cite book
author = Lev Virine & Michael Trumper
year = 2007
title = [http://www.projectdecisions.org Project Decisions: The Art and Science]
publisher = Management Concepts
id = ISBN 978-1567262179
*cite book
author = David Hillson
year = 2007
title = Practical Project Risk Management: The Atom Methodology
publisher = Management Concepts
id = ISBN 978-1567262025
*cite book
author = Kim Heldman
year = 2005
title = Project Manager's Spotlight on Risk Management
publisher = Jossey-Bass
id = ISBN 978-0782144116External links
* [http://www.pmi.org PMI.org]
* [http://www.ogc.gov.uk/methods_prince_2.asp PRINCE2]
Wikimedia Foundation. 2010.