Risk management should raise the likelihood of meeting project objectives, and identified risks with the options for addressing each should be part of the project plan. Every team member shares responsibility for finding risks, which means identifying potential sources and characteristics that could help or harm objectives, and risk management should identify, assess, treat, control and respond to risks across the life cycle. Risks are to be identified across the whole project life cycle, recognising that earlier risks can change or return. Each identified risk should be recorded when it is found and assigned to an owner, whatever its origin inside or outside the project. Every risk should be evaluated for likelihood, impact and how soon it may materialise, then ranked so effort goes to the most significant. The links and dependencies between separate risks should also be examined. Response options should be developed that raise the chance of gains and lower exposure to losses, selecting from acceptance, avoidance, mitigation, transfer, contingency, exploitation and enhancement. The chosen action must suit the size of the threat or opportunity, be affordable, timely and workable in context, be understood by those affected, and carry a responsible owner. Residual risk should be recognised, and any resulting deviation from plan or baseline change handled through change control. Risk control should confirm that agreed responses were actually carried out and had the intended effect, aiming to limit disruption from threats and maximise gain from opportunities. It relies on reviewing management information such as risk priority, progress data, plans, change requests and corrective actions, and on tracking how each risk develops and how well the treatment works.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.