You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Document and track identified risks for the project.
Description
Risk documents provide information about what issues may cause harm to the success of a project. Not only is the severity and likelihood of the risk specified. This document may have any information attached to track and evaluate risks.
Properties
The document type risk provides the following properties:
Type
Specify the type to organize risks.
Phase
Specify the phase of the project this risk may have impact.
Severity
Asses the severity of the risk's impact on the project.
Probability
Assess the probability this risk will have impact on the project.
Reporter
Specify the reporter in case further information is required.
Assignee
Specify the stakeholder responsible for tracking this risk.
Recognized on
Log the date the risk has been recognized.
Deadline
Log the date the risk has to be managed that it will not have negative impacts on the project.
Reference
Add references to information on external systems here.
Sections
Description
Document cause and description of the risk.
Summary
Provide a summary of the documents structure and key points. This is an informative abstract typically of about 100 to 200 words.
Recognition
Describe how the manifestation of the risk can be detected as early as possible.
Drivers
List the drivers that aggravate or abate an aspect of the risk. This may affect the impact, the likelihood of occurrence, the time or any other aspect. Separating the drivers for a risk from its description allows to elaborate what influences apply to the risk.
Impact
Describe the impact the risk has on the project. Name also the resources that are specifically affected.
Actions
List the actions to take to reduce the effects of the risk.
Relationships
List relationships to other risks or problems.
Subordinate Risks
Complex risks may be detailed in separate risk descriptions, which are added as children to this document.
Notes
These are internal notes that are usually not exported and only visible to team members with write access.
But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
Resources
The resources section provides references to further information to the topic of the document.
This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.
