11.6 Implement Risk Responses
Carry out the risk responses that were planned, not just leave them on paper.
Executing / Risk · ← PMBOK reference · See it on the map
Why it matters
A response plan that sits unused when the risk actually occurs protects nobody; this is where the planning finally pays off.
What done looks like
Planned responses are being carried out and their effect on the risk is tracked.
First time tip
Check in with each response owner before the risk actually triggers, not after. Confirming readiness early avoids a scramble in the moment.
What you need (Inputs)
- Risk Management Plan
- Risk Register
- Risk Report
- Lessons Learned Register
How Scrum/Kanban projects satisfy this — counted from: sprint retrospective evidence (driftless/models/delivery.py:Sprint) — a sprint closed with retrospective notes is a lesson captured, the way a predictive project files one as prose - Organizational Process Assets
How you do it (Tools & Techniques)
What you get (Outputs)
Worked example
Two weeks out, the site manager confirms the marquee is booked and paid for, and the bookings volunteer has the standby act's written agreement in hand. The chair checks both off at the meeting instead of assuming they happened, and the register records the date each response actually went into place.
Common pitfalls
- Assuming a response that was planned is a response that happened.
- Carrying out the response but never recording it, so the register still shows the risk untreated.
- Leaving the booking until the risk looks likely, by which time the marquee is already hired out.
How driftless helps
- Risk Register can be created in the wizard.