Talk:Risk register

From apppm
(Difference between revisions)
Jump to: navigation, search
(→‎Review by Dutten)
Line 31: Line 31:
  
 
= Review by Dutten =
 
= Review by Dutten =
−
 
−
Dear Keyser Sözer,
 
−
 
−
I enjoyed reading your wiki article.
 
−
My comments are divided into general comments, and text specific comments, see below.
 
−
 
−
==Generel comments==
 
−
*You are missing your reference list in the bottom - you can make it by using the following code without the spaces:
 
−
=References =
 
−
<references />
 
−
*Your figure on the right ''Example of a Risk Register used by SURF'' is too small. By using this code, and changing the number 550, you can change the size.
 
−
[[Fil e:Creativityexample.png|550px|thumb|right|Figure 2. Example of how creativity is necessary through all project phases]]
 
−
 
−
==Text specific comments==
 
−
Risk Register
 
−
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 is the optimum risk management tool within project management when it is used correctly within a management project.
 
−
 
−
What is a Risk register
 
−
A risk register is the baseline document of the process of managing risk (reference Winch); it is a means of visualising a project’s risks within a table or template so that risks can be better understood and dealt with by project managers. It allows risks, their likelihood and preventive measures for each risk to be recorded [2]. The risk register should be in a centralised location for information to be stored and updated with respect to the risks that are effecting the company; it is key that the risk register is used constantly throughout a project process. As can be seen in Graham Winch’s risk process diagram (insert Winch diagram), throughout the lifecycle of how a risk is dealt with, the risk register is the tool that should be constantly updated and referred to.
 
−
Generally, risk registers are created within a company's intranet or online database where the register can be updated by any member of staff and can be seen by any relevant project stakeholders. The register would then be made using database or spreadsheet software. A risk register could also be made offline however, being drawn on a whiteboard at a company meeting for example as a quick and efficient tool for motivating the meeting. The register must always be in a visual format however; visualisation is key to the success of the risk register tool.
 
−
Whenever an important decision is made within a project, the risk register is referred to. Whenever something unfamiliar is being dealt within a project, again the risk register should be referred to. This is how the risk register should be used, as a familiar tool that any member of a project team can come back to ensure they can make the right decisions with a clear and focused mindset and without the need for a boss or authoritative figure being at hand; it therefore also reduces the time needed for project teams to carry out tasks, improving the efficiency of workers.
 
−
The risk register cannot only be used as a motivating risk management tool; it also has further uses as a documentation tool. Documenting information that is flowing into a project is incredibly important to manage risks affecting a current project but it also works as means of storing historical data. Ensuring that information is quickly available to you may be entirely necessary if a past client requires information about a past project [3]. Having a shared risk register would provide access to this information. It is also crucial in preventing future failures as risk registers become more and more effective as they are used more frequently within a company. Information about the uncertainty of a previous risk would allow a project manager to make a more educated decision about how to deal with the risk and would increase their own knowledge about these risks.
 
−
 
−
Defining Risk
 
−
To use the risk register correctly, it is essential that the risks associated with the project are identified properly using a risk management plan [4]. A risk management plan should consist of utilising the help of relevant stakeholders and project team members to gather all risks prior to the risk register being created. Consulting everybody before the risk register is created increases the efficiency of the risk register; everyone who uses it is involved in its creation and all relevant risks should be covered and correctly recorded if everybody has an input from their respective departments.
 
−
USE WINCH BOOK FOR THIS PART
 

Revision as of 21:35, 25 November 2014

Contents

Hermaeus Mora

Structure

  • The language is clear and easily understandable. A couple commas may be missing and in the first section paragraph 3 "The risk register cannot only be used as a motivating risk management tool" could be formulated as "The risk register can be used not only as a motivating risk management tool;" apart from that it's good.
  • There's just one figure, more could be added as the article grows.
  • References to links are nicely made, the article uses a book, this should be referenced in the traditional wiki way <references />.
  • A category from APPPM is added which is nice, maybe add a few more e.g. Uncertainty, Risk etc.
  • Layout seems to be ok for now, abstract, introduction to the tool and its applications and an introduction to how the tool should be used.

Content

  • The article is obviously not finished yet (778 words as of the writing of this review) So the review can only regard the initial part.
  • The article clearly falls under the 'in-depth description of a particular method' category. It relates deeply to project management and, judging by the links attached, is based on fresh data.
  • The abstract is good in length and shows a fair purpose behind the tool. It could however include a few sentences about the tool itself, short summary, instead of a rather strong opinion that it's "THE optimum [...] tool within project management".
  • As mentioned before any book references should be added along with additional categories in APPPM wiki for further reading.

Review - WinWin

Structure

  • The overall feeling of the article is very positive. The language is precise and easy to understand. However, there are a few spelling mistakes and grammar mistakes, which will surely disappear in the editing process.
  • At the moment there is only one figure in the article. Using more figures will definitely have a positive effect on the visualization as the article gets further along.
  • Good use of references.
  • The layout seems to be fine for now.


Content

  • The preliminary content seems to be very relevant to the course. The paragraphs are nicely written but could profit from a few summarizing sentences.
  • The fresh data is a nice touch.
  • The abstract has a suitable length for this kind of article. Definitely a plus.

Review by Dutten

Retrieved from "http://wiki.doing-projects.org/index.php?title=Talk:Risk_register&oldid=3415"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox