<Project Name>
Risk List
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
Date |
Version |
Description |
Author |
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3áááá Definitions, Acronyms and Abbreviations
2.1áááá <Risk Identifier û a descriptive name or number>ááááá
2.1.1áááááááááááRisk Magnitude or Ranking
2.2áááá <next Risk Identifier û a descriptive name or number>
Risk List
[The introduction of the Risk List should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Risk List.]
[Specify the purpose of this Risk List.]
[A brief description of the scope of this Risk List; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Risk List. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Risk List.á Each document should be identified by title, report number (if applicable), date, and publishing organization.á Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Risk List contains and explain how the document is organized.]
[An indicator of the magnitude of the risk may be assigned to help rank the risks from the most to the least damaging to the project.]
[A brief description of the risk.]
[List the impacts on the project or product.]
[Describe how to monitor and detect that the risk has occurred or is about to occur. Include such things as metrics and thresholds, test results, specific events, etc.]
[Describe what is currently done on the project to reduce the impact of the risk.]
[Describe what the course of action will be if the risk does materialize: alternate solution, reduction in functionality, etc.]