Provides doctypes for documenting and tracking risks.
Risks refer to events that may or may not have impact on a project. This impacts may be in favor for the success of the project, but often the risks with a negative impact are of more concern.
To manage risks the project management set of doctypes provides blueprints.
The following doctypes provide blueprints for risk management.
| # |
Name |
Short Description |
Documentation Type |
Categories |
| 1 |
|
Document assumptions to assess risks and opportunities for the project. |
|
|
| 2 |
|
Assumptions are grouped by their type. |
|
|
| 3 |
|
Document and track identified opportunities for the project. |
|
|
| 4 |
|
Opportunities are grouped by their type. |
|
|
| 5 |
|
Document problems as a means to communicate the details and to use the information for reviews and retrospections. |
|
|
| 6 |
|
Problems are grouped by their type. |
|
|
| 7 |
|
Document and track identified risks for the project. |
|
|
| 8 |
|
Document actions to prevent or reduce the negative impact on exceptions on a project. |
|
|
| 9 |
|
Risk actions are grouped by their type. |
|
|
| 10 |
|
Risks are grouped by the phase of their impact on the project. |
|
|
| 11 |
|
Risks are grouped by the probability of having impact on the project. |
|
|
| 12 |
|
Risks are grouped by the severity of their impact on the project. |
|
|
| 13 |
|
Document targets of risks. |
|
|
| 14 |
|
Risk tagets are grouped by their type. |
|
|
| 15 |
|
Risks are grouped by their type. |
|
|
Values as Document Instances
This model assumes that probability is a category and not a plain number. A category, such as risk probability 'high' requires a description on how to associate a risk with this probability. In this case adding a document of type Risk Probability is a natural way to provided this documentation.
In case you model expresses the value as a percentage or an absolute number, you may consider to use a macro to prevent users entering illegal values by accident.
