Risk management within PRINCE2 7th Edition
Risk is inevitable whenever we undertake a project since projects enable change, and whenever you have a change, it introduces uncertainty and risk. We, therefore, need to understand how to apply risk management.
A risk is an uncertain event that, should it occur, will affect the project meeting its objectives. These uncertain events can be positive, in which case they would be called an opportunity; when negative, they are called Threats. Both need to be controlled in risk management.
When carrying out risk management, the purpose is to reduce the probability and impact of threats and to increase the likelihood of opportunities and their positive impact. It is helpful to consider that risk is an event that may not occur in the future, but if it does happen, it will impact the project objectives.
Effective risk management entails identifying each risk, estimating it in terms of its probability and impact and controlling it by taking appropriate action and ensuring such action has the desired effect.
In the Starting Up a Project process, which takes place before the project starts, any known risks are captured in the Daily Log. This is the start of risk management. The Project Mandate may contain known risks via Corporate or Programme Management. When creating and assembling the Project Brief, any known risks are captured, particularly those within the outline Business Case.
The Risk Management Approach
Before getting into the details of risk management, it is essential to establish how risks will be managed with a project. This is captured in the Initiation Stage and forms part of the Project Initiation Documentation in the form of the Risk Management Approach, which describes how risk management will be used and implemented within the project.
The risk management approach should include, among other things, tools and techniques to be used, the responsibilities for risk management actions, the scales for calibrating and estimating probability and impact, the risk categories to be defined, their proximity, and risk trigger indicators.
For contingency or fallback actions, a risk budget should also be agreed. This budget is used to pay for any such risk actions as part of risk management, should they be needed.
When using management by exception, the risk tolerance or risk appetite should be agreed between the project manager and the project board and included within the Risk Management Approach document.
The Risk Register should be created early in the project, as it is a vital tool that contributes to risk management and is used to capture all details and the status of each risk identified. The project manager is responsible for ensuring that risk management is implemented correctly. Still, there will be the need for risk owners for all risks, and these owners may be other people involved in the project.
The Risk Management Steps.

The first step in the risk management procedure is identifying the risks, generally done within a risk workshop. Another valuable source of possible risks is reviewing lessons from previous projects. Yet more sources include organisational risk checklists or industry-wide checklists or tables.
Many people make risk management mistakes by naming risks such as “there is a risk that the project may come in late”, — but this is in error because that statement is not the risk itself but its impact.
It is helpful to consider that the source of the risk is called the risk cause (the potential trigger points for each risk), the risk event describing the area of uncertainty, and the risk effect, which he describes the risk in fact on the project objectives.
The next step is to estimate and evaluate each risk, and various estimation techniques may be used within risk management:
Cause and Effect Diagram (Ishikawa Diagram)
This is also known as a fishbone diagram. It is used to “reverse engineer” the risk impact back to its possible causes:
Probability trees. Links up a diagrammatic representation of possible events shown as linked rectangles, each with a probability and impact. When connected, the aggregated value of project risk can be determined. These help the decision-makers determine possible outcomes and recommend suitable actions for risk management.
Expected value. This technique multiplies the cost of the risk impact with the probability of the risk occurring. For example, if the cost of a risk was £8,000, and the likelihood was equal to 40%, then the expected value would be £ 3,200. Summing all of these expected values together will give the project’s aggregated risk expected monetary value for use in risk management.
Pareto Analysis. This is often called the 80/20 rule, from the observation that 20% of the risks will have the most impact on a project, and allows management to focus their risk management attention on managing and controlling those risks.
The probability impact grid. This is a table with the vertical axis scaled in probability and the horizontal axis mounted in impact. Suitable scales are determined, typically 10% probability, from very low to very high, between 70 to 90% of ability. The impact scale usually covers from very low to very high. The grid is used to assess the severity of a risk, enabling risks to be ranked so that risk management efforts can be prioritized.
The summary risk profile. This, again, is a table of probability against impact. Still, instead of measuring the severity of each risk (probability x impact), it plots each risk as a number, much like a scatter diagram, so that the spread and severity of risks can be directly seen and used for risk management. For example, risks with a very high act and probability would be seen as severe threats, enabling appropriate actions or countermeasures to be determined.
Plan appropriate responses to threats and opportunities.
There are many ways to describe such actions, but the following most of them are used:
Threats.
Avoid. An action is planned such that the threat can no longer impact the project and/or its probability is zero.
Reduce. An action is planned to either reduce the probability of the risk occurring and/or reduce the event’s impact should it happen.
Fallback (often called Contingency). An action is planned but only implemented should the linked risk occur.
Transfer. An action is planned that reduces the financial impact of the threat. Usually, the action is via some form of insurance or an appropriate clause in a contract.
Accept. This is the take-no-action option. The threat should be continuously monitored to ensure that it remains tolerable. This risk management action is often chosen because the risk has a low probability and/or a low impact, or the costs and effort of any actions outweigh the severity of the threat.
Threat or Opportunity
Share. This risk management action is often carried out within contracts using third parties, where a pain/gain formula is agreed upon should the threat or opportunity occur.
Opportunities.
Exploit. We are taking action to ensure that the opportunity will happen and the positive impact will be realized.
Enhance. We are taking proactive actions that enhance the probability of the event’s impact.
Reject—a decision taken not to exploit or enhance the opportunity.
All of the above actions are captured and entered within the risk register, and plans are updated to include the above activities and resources as part of risk management.
It is helpful to include the proximity of each risk. This is the time frame of the risk event occurring from the present day. This helps focus resources on actions for risks shortly. However, it is also helpful in determining when each risk event will occur, as this will affect the severity of the impact.
New risks can be identified throughout a project, and existing risks can change their status — for this reason, risk management should be seen as an ongoing activity throughout the project. It should also be remembered that as issues arise, these can impact existing risks or cause new risks.
At the end of each stage of a project, the total risk situation needs to be calculated and used as part of the data for management to make an informed decision as to whether to proceed with the project or not.
At the end of a project, as part of the closure, any outstanding risks which would, therefore, impact the end product’s operational life should be found by a new owner so that such risks can continue to be successfully managed and controlled.
The effectiveness of risk management actions will be included in the Lessons Report.
Risk management procedure in PRINCE2 7
PRINCE2 recommends a five-step procedure for risk management: identify, assess, plan, implement, and communicate. The first four steps are sequential, but the communication step is done continuously, in parallel with the first four.
Risk management sequence versus procedure steps.
At the high level, risk management consists of just two ‘stages’ if you will…
This could broadly be risk analysis; the second is risk management. Let me explain.
Risk Analysis.
- This is where the risks are first identified
- Then, they are evaluated in terms of their probability, impact, proximity, etc.
- Then, suitable responses for each risk are identified and considered
- Then, the best response is selected
Risk Management.
This is where:
- The selected response is included in the relevant plan as an activity (or more), along with the resources needed to carry out that activity.
- The plan is then approved (the Stage Plan), the response activity is implemented, and its effectiveness is monitored. If it is not having the desired effect, then some form of corrective action is carried out
- At the same time, reporting of the risk status occurs within the stage – this will generally include references within the Checkpoint Report and Highlight Report.
Risk Management Steps.
Dealing with each step in turn:
Identify. This has two steps: first, to identify context, and second, to identify risks. Identifying the Context means determining the project objectives at risk and formulating the Risk management Strategy document, which describes how risks will be managed throughout the project.
Identifying risks is to capture all threats and opportunities that may affect the project objectives, and an effective way of doing this is within a risk management or planning workshop.
The next step in risk management is assessment, which has two steps: Estimate and Evaluate.
Estimating each risk is determining its probability and impact, and for this, a sensible set of scales will need to be chosen. There are also several risk management estimation techniques.
Another aspect of risk management which needs to be determined is their proximity. Proximity is the time duration measured from today for when a specific risk may occur. This helps prioritize risks and evaluate their impact by understanding when they appear.
A helpful way to represent the total risk situation is to plot each risk on a Summary Risk Profile. This is a simple matrix plotting probability on the vertical axis against impact on the horizontal axis. Each risk will be represented by its reference number, and the resulting picture will look like a scatter diagram.
The evaluation step in risk management aims to assess the aggregated effect of all identified threats and opportunities. From here, an assessment can be made of the overall severity of the project risks.
The risk severity must be checked to be within the risk tolerance band set by the project board. Risk severity is often expressed as a monetary value determined by multiplying its probability by the financial impact. If this is done for each risk and then summed, it is called the Expected Monetary Value.
The Plan step determines the possible risk management responses for each threat and opportunity to remove or reduce the threats and maximize the opportunities. An important factor in selecting each response is ensuring a balance between the cost of the response and the probability and impact of the risk occurring.
Examples of responses to a threat include avoiding, taking some different action, Reduce by reducing the probability/impact, Fallback, having a contingency plan to minimize the impact should the risk occur, Transfer, using some form of insurance or a third party, Share in terms of a pain/gain formula, or Accept by choosing to do nothing but to continue monitoring the situation.
For opportunities, the responses are Exploit, taking some action to ensure the opportunity will happen; share, the same as for threats; enhance, which enhances the probability/impact by taking action now; and Reject, which is a deliberate decision not to exploit or enhance the opportunity.
The parallel Communication step
Within risk management relates to using various reports throughout the project. These are the Checkpoint Reports, Highlight Reports, End Stage Reports, End Project Reports, and Lessons Reports
PRINCE2® 7 Foundation and Practitioner


Learn PRINCE2® 7 Foundation and Practitioner Online
** Enhance your PRINCE2 career now **
PRINCE2® Masterclass gives you the skills necessary to manage projects effectively and achieve your objectives.
Get 7 days a week 12 months one to one coaching with ex PRINCE2 examiner Dave Litten.
PRINCE2® is a globally recognized project management framework. By completing both the Foundation and Practitioner courses through our self-paced e-learning, you will develop an understanding of the methodology and learn how to effectively adapt it to any project.
The PRINCE2® 7 Foundation and Practitioner Masterclass is PeopleCert Accredited and guarantees to take you from PRINCE2 Novice to PRINCE2 Practitioner with our famous video learning, study guides and practice exams.
What Does the Masterclass Cover?
The PRINCE2 Foundation examination assesses your knowledge and comprehension of the PRINCE2 project management methodology as detailed in the syllabus. The PRINCE2 Practitioner examination, on the other hand, gauges your ability to apply and tailor the PRINCE2 method. Candidates who pass the Practitioner exam should be able to start implementing the method on an actual project with some guidance. However, their effectiveness may differ based on their experience in project management, the complexity of the project, and the level of support they receive in their work environment.

