blob: 2f3b8642f49c79115d494c93a71baebeb214c95b [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="" xmlns:org.eclipse.epf.uma="" epf:version="1.0.0" xmi:id="-4VJ_0upihz-bR7VRlm63Vw" name="risk_list,_Ckay8Cc_EduIsqH1Q6ZuqA" guid="-4VJ_0upihz-bR7VRlm63Vw" changeDate="2006-10-30T16:42:53.506-0800">
<mainDescription>This list identifies, in decreasing order of priority, the events that could lead to a significant negative outcome. It
serves as a focal point for project activities and is the basis around which iterations are organized. &lt;!--EndFragment--&gt;</mainDescription>
This list should capture the critical and serious risks. If you find this list extending beyond 20, carefully consider
whether they are really serious risks. Tracking more than 20 risks is an onerous task.
<purpose>To&amp;nbsp;capture the perceived risks to the success of the project.</purpose>
Option: list of risks captured in the project plan
In this approach you put the overall risk list in the project plan. The iteration plan will contain only the tasks you
will be doing during the iteration to mitigate the risks. This will ensure that the iteration plan contains only
iteration information. The project plan has to be revisited constantly as you update risks.
Option: list of risks captured in&amp;nbsp;the iteration plan
In this approach you enter the overall risk list in the current iteration plan. This approach ensures that you look at
the risk list at each iteration, as it is part of your iteration plan. The only drawback is that your iteration plan
will contain information that is not relevant to the current iteration. All the risks you have not&amp;nbsp;mitigated
during the iteration&amp;nbsp;have to be&amp;nbsp;transferred to the next iteration plan.