blob: c8e147355d079f9b07de769d9fad1a0bfc42d943 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="-gqNN4DnROmJpgKtrdguhpg" name="new_checklist,_7BZa0DIdEduDTv4Y1akVTA" guid="-gqNN4DnROmJpgKtrdguhpg" changeDate="2006-08-22T13:38:14.915-0700">
<sections xmi:id="_qO41ADIfEduDTv4Y1akVTA" name="Have all potential risks to the project been identified" guid="_qO41ADIfEduDTv4Y1akVTA">
<sectionDescription>Have you identified anything that can be on the path to the project success? List all potential risks, giving a description
and type (direct or indirect). See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup_basic/guidances/concepts/risk,_0bsLgMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0bsLgMlgEdmt3adZL5Dmdw&quot;&gt;Concept: Risk&lt;/a&gt;&amp;nbsp;for more information.</sectionDescription>
</sections>
<sections xmi:id="_5RiSkDe2EduD7J48kKN20g" name="Are risks described without ambiguity" guid="_5RiSkDe2EduD7J48kKN20g">
<sectionDescription>Make sure you capture and describe risks in a clear, concise and unambiguous way. Also follow these rules when describing
mitigation strategies for risks. This will avoid unnecessary work and - more importantly -&amp;nbsp;that a risks are
effectively identified and managed.</sectionDescription>
</sections>
<sections xmi:id="_2rpQoDIfEduDTv4Y1akVTA" name="What is the probability of happening and impact of each risk" guid="_2rpQoDIfEduDTv4Y1akVTA">
<sectionDescription>Determine&amp;nbsp;the probability of the risk happening and its impact on the project. This gives you the order of magnitude
of risks (probability x impact), allowing you to address the high magnitude risks early in the project. See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup_basic/guidances/concepts/risk,_0bsLgMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0bsLgMlgEdmt3adZL5Dmdw&quot;&gt;Concept: Risk&lt;/a&gt;&amp;nbsp;for more information.</sectionDescription>
</sections>
<sections xmi:id="_x-gbwDe0EduD7J48kKN20g" name="Have the risks been properly prioritized and sorted" guid="_x-gbwDe0EduD7J48kKN20g">
<sectionDescription>The risk list is a prioritized list with the highest risk at the top and the rest in descending order.&amp;nbsp; They should be
sorted according to their magnitude of risk.</sectionDescription>
</sections>
<sections xmi:id="_hSFaYDe3EduD7J48kKN20g" name="Are there interdependencies between risks" guid="_hSFaYDe3EduD7J48kKN20g">
<sectionDescription>&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;
&lt;span style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: Arial&quot;&gt;Make sure you establish interdependencies between risks as
appropriate. For example, the consequence of a risk happening may raise the probability of another risk happening, or
raise the impact that other risk brings to the project. If risks depend on each other, you may need to
mitigate&amp;nbsp;all interdependent risks&amp;nbsp;at the same time, or revisit the risk list to update the magnitude of
dependent risks.&lt;/span&gt;
&lt;/p&gt;</sectionDescription>
</sections>
<sections xmi:id="_LATHgDIeEduDTv4Y1akVTA" name="Is there a mitigation strategy for each risk" guid="_LATHgDIeEduDTv4Y1akVTA">
<sectionDescription>&lt;p&gt;
Propose a mitigation strategy for each identified risk. You can either transfer the risk, avoid it, accept it or
mitigate it (by minimizing the probability&amp;nbsp;of happening or impact&amp;nbsp;that the risk brings to the project). See
&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup_basic/guidances/concepts/risk_management,_VNxL4ACsEdu8m4dIntu6jA.html&quot; guid=&quot;_VNxL4ACsEdu8m4dIntu6jA&quot;&gt;Concept: Risk Management&lt;/a&gt; for more information.
&lt;/p&gt;</sectionDescription>
</sections>
</org.eclipse.epf.uma:ContentDescription>