| Artifact: Risk List |
 |
 |
|
| To capture the perceived risks to the success of the project. |
| Fulfilled Slots | ||
|---|---|---|
| Roles | Responsible: | Modified By: |
| Tasks | Input To:
|
Output From: |
| Main Description |
This list identifies, in decreasing order of priority, all the risks associated to a project. It serves as a focal point for project activities, and is the basis around which iterations are organized. See Concept: Risk for more details. |
|---|
| Templates |
|---|
|
This list should capture the critical and serious risks. If you find this list extending beyond 20 items, carefully consider whether they are really serious risks. Tracking more than 20 risks is an onerous task. |
| Impact of not having | If risks are not identified, then the required mitigation strategies will not be in place, and any adverse events that do occur on a project will have to be dealt with in an ad-hoc manner. Undocumented risks that do occur are also more likely to impact the overall schedule and quality of the solution |
|---|---|
| Reasons for not needing |
Unless there are no risks, or very minimal ones, there is no reason not to produce this artifact. |
| Representation Options |
A representation option for the risk list is to capture it as a section in the coarse-grained plan for the project. This means the coarse-grained plan has to be revisited constantly as you update risks. The fine-grained plans will contain only the tasks that you will be doing to mitigate risks in the short term. Given that this is a list of tabular data, it is advisable to use a centralized data storage mechanism to store these items. For example, one could use a relational database table (such as Oracle or SQL Server), a SharePoint List, a DotNetNuke user-defined table, or similar. That said, a spreadsheet is better than a word-processing document; but, a multi-developer project calls for a soltuion that can be edited by many at once. |
|
This program and the accompanying materials are made available under the |