Risk register

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
'''Summary'''
 
 
I plan on writing a Wikiarticle on using the Risk Register (or Risk Log) tool within project management. The article will begin by defining a risk register and will follow up with a short section on why risk management is important and how to define risk- segregation of risks within the register will also be included.The article will then outline what the tool should look like according to the definition of these risks- which categories and headings should be included in the register, which format the register should take ie table, document etc. This section will also include a short part on the different types of risk registers that are used in project management. Following this, the register’s uses following its creation ie how to properly update and maintain the register will be outlined. The use of further risk logs in the future and how to properly implement these risk logs will be outlined. A final section on the possible flaws of risk registers will be included. Throughout the course of the text, the benefits of the risk register will be analysed and its use within a project management plan will be evaluated. The article will also include risk register diagrams when necessary. The article will finish with a section of notes and citations used.
 
  
 
'''Contents'''
 
'''Contents'''
  
ix Importance of Risk Management
+
'''ix Importance of Risk Documentation'''
  
 +
The uncertainty surrounding any decision or action that may negatively affect a project’s success can be defined as a risk and knowing how to classify and document these risks is essential to the success of any project. This is because risk uncertainty can be difficult to control and predict; being able to communicate risk likelihood and categorisation to a project team in an efficient way allows the team to evaluate risks together and identify to what extent they can prevent these risks from happening. Documenting risks from an early stage streamlines a team’s goals and their perception of the project, working as a communication tool and a risk management tool simultaneously. The Risk Register can be used as the optimal risk documentation tool.
 
----
 
----
  

Revision as of 17:49, 20 November 2014

Contents

ix Importance of Risk Documentation

The uncertainty surrounding any decision or action that may negatively affect a project’s success can be defined as a risk and knowing how to classify and document these risks is essential to the success of any project. This is because risk uncertainty can be difficult to control and predict; being able to communicate risk likelihood and categorisation to a project team in an efficient way allows the team to evaluate risks together and identify to what extent they can prevent these risks from happening. Documenting risks from an early stage streamlines a team’s goals and their perception of the project, working as a communication tool and a risk management tool simultaneously. The Risk Register can be used as the optimal risk documentation tool.


1. Definition of a Risk Register


2. Defining Relevant Risks


3. Layout


3.1 Templates


3.2 Types


4. Utilisation


4.1 Current Utilisation


4.2 Future Utilisation


5. Faults


6. Notes and Citations.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox