Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 41 ยท Risk, Quality and Communication

Risk Management Process

Learn the project risk management process: identify risks, score probability and impact, plan responses, keep a risk register and monitor with simple Python examples.

A risk is an uncertain event that, if it happens, changes what your project achieves: its schedule, cost, scope or quality. A flood in the server room is a risk. A key developer already on holiday is not a risk but a fact, and a fact is handled in the plan. This difference matters, because the risk process is how you decide where to spend limited attention before the surprise arrives.

Risk management is not pessimism. It is the habit of asking "what could change our plan?" early, while changes are still cheap. Opportunities (positive risks) belong in the same process: a supplier discount or a reusable component can pull a project ahead.

The risk management process

Most standards (PMI, PRINCE2, ISO 31000) agree on the same loop.

The risk loop

Identify List what could go wrong or right.
Analyze Score probability and impact.
Respond Choose a strategy and an owner.
Monitor Review, update and close risks.

It repeats every week or sprint, not once.

1 / 2

Identify

Run a short workshop. Ask each person for risks in their own area: technology, people, suppliers, regulation, schedule assumptions, requirements. Write each as a sentence with a cause, an event and an effect: "Because the payment vendor has no sandbox (cause), integration testing may start late (event), delaying go-live by two weeks (effect)." That form stops vague entries like "integration problems".

Analyze

Qualitative analysis scores each risk on two scales, usually 1 to 5:

  • Probability: how likely is it?
  • Impact: how bad (or good) if it happens?

The product is the risk score. A 3 by 5 risk (score 15) deserves more attention than a 5 by 1 risk (score 5). Teams color-code scores into low, medium and high bands. When you need numbers in money or days instead, use quantitative methods such as expected monetary value or simulation (see Monte Carlo schedule risk).

Respond

For threats there are four classic strategies:

Strategy Idea Example
Avoid Remove the cause Drop the unproven library
Mitigate Reduce probability or impact Add a prototype spike in week 2
Transfer Shift the impact to someone else Fixed-price contract, insurance
Accept Do nothing now (active: reserve; passive: just document) Minor UI delay

For opportunities the mirror strategies are exploit, enhance, share and accept. Each response gets an owner (a named person) and, if it costs money or time, it is added to the plan. Remaining risk after the response is the residual risk; new risks created by the response are secondary risks.

Monitor

Risks change. Review the register at every status meeting, retire risks whose dates have passed, add new ones, and watch triggers: early warning signs ("vendor has not replied for 5 days").

The risk register

The register is the single document of record. A useful row has an ID, description, probability, impact, score, response, owner, trigger and status.

Python A risk register in Python

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Sorting by score gives the agenda for the next risk review. Note that R3 has a high impact but a low probability; a score alone hides that, so look at the extreme cells of the matrix, not only the sorted list.

Probability and impact matrix

A matrix turns the two scales into a picture people can discuss.

Python Print a probability-impact matrix

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Expected monetary value

When impact is in money, multiply by probability to get the expected monetary value (EMV). A 20 percent chance of a 50,000 loss has an EMV of -10,000. The total EMV of your risks is a starting point for a contingency reserve: money held for known risks. A management reserve is held for unknown unknowns and is controlled by the sponsor, not the project manager.

Python EMV and contingency

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common mistakes

  • One workshop and done. A stale register is worse than none because it gives false comfort.
  • No owners. "The team" owns nothing. Name one person per risk.
  • Mixing issues and risks. An issue has already happened and goes to the issue log with an action.
  • Vague wording. Without cause, event and effect, nobody can choose a response.
  • Ignoring opportunities. Positive risks are free value.

Ask "what would surprise us?" in every status meeting. Two minutes of this question finds more risks than a quarterly workshop.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which statement describes a risk rather than an issue?

    A risk is uncertain and in the future. The other items have already happened, so they are issues.
  2. 2. You sign a fixed-price contract so the supplier bears cost overruns. Which response is this?

    Transfer shifts the impact (and ownership of the response) to a third party, often by contract or insurance.
  3. 3. A 20 percent chance of a 40,000 loss has an expected monetary value of:

    EMV is probability times impact: 0.20 x 40,000 = 8,000 (a loss, so -8,000).
  4. 4. Who normally controls the management reserve?

    Management reserve covers unknown unknowns and sits outside the project's own baseline, under management control.

Summary

  • A risk is an uncertain future event; an issue has already happened.
  • The loop is identify, analyze, respond, monitor, and it repeats.
  • Write risks as cause, event and effect; score probability times impact.
  • Threat responses: avoid, mitigate, transfer, accept; opportunities: exploit, enhance, share, accept.
  • Every risk needs an owner, a trigger and a review date.
  • EMV turns risks into money to size the contingency reserve.

Next: Monte Carlo Schedule Risk