This process ensures that all project risks are identified, assessed and managed. It also helps to manage project risk proactively. This is done by reducing the probability of a risk occurring, identifying contingency plans where needed and at times justifying that a risk is accepted. Countermeasures (mitigation) should be considered for every risk. The nature and extent of the countermeasure will depend on the nature of the risk and on the impact assessment carried out. Countermeasures must be noted in the Risk Log and included in the Delivery Plan and/or Timebox Plans, either as specific actions to prevent or reduce the risk or through re-balancing the MoSCoW priorities in order to deal with risk. Contingency plans should be linked to specific risks. So in a Timebox where significant risk has been identified, it is advisable to increase the proportion of Should Have and Could Have requirements providing additional contingency for the guaranteed delivery of the Must Have requirements There is a perception to that risk management is a Project Manager responsibility. However in reality, the whole team should be aware of the risks, even though the Project Manager may drive risk management. Since the focus of the project is on delivering a business solution and the risks could affect the success of the project, a decision to cancel a project, especially during the early stages, is sometimes made based on an unacceptably high level of risk.