|
Have all potential risks to the project been identified
| 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 Concept: Risk for more information. |
Are risks described without ambiguity
| 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 - that a risks are
effectively identified and managed. |
What is the probability of happening and impact of each risk
| Determine 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 Concept: Risk for more information. |
Have the risks been properly prioritized and sorted
| The risk list is a prioritized list with the highest risk at the top and the rest in descending order. They should be
sorted according to their magnitude of risk. |
Are there interdependencies between risks
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 all interdependent risks at the same time, or revisit the risk list to update the magnitude of
dependent risks.
|
Is there a mitigation strategy for each risk
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 of happening or impact that the risk brings to the project). See
Concept: Risk Management for more information.
|
|
