1. What This Register Is For
3. Likelihood x Impact (what to act o...
Likely / small impact
Likely / large impact
Unlikely / small impact
Unlikely / large impact
4. Four Ways to Respond (and what to ...
5. Keeping the Register Alive
Project Risk Regi...
How to use: 1. Li...
Direction & t...
How to write &...
Warning signs &am...
Scoring notes &am...
Goal Fewer scrambles after the fact. Decide up fron t who does what, and when, if the risk lands.
How to write a line Use: because of , happens, and follows. e.g. Approvals drag on and work starts two wee ks late.
What not to log Something already happening is an issue, not a risk. Issues belong on the task board as card s.
Easy to miss People (departures, crunch), outside parties ( vendors, approvals), assumptions (specs not ye t fixed).
2. Where Risks Co...
Sources of risk
Schedule
Waiting on dependencies
Technology
Unproven tech choices
Requirements
Specs still in flux
People
Turnover, peak workload
Vendors
Delays and approvals
Cost & legal
Overruns, contract terms
縦軸: Likelihood (l...
Small each time, but they add up. Change the process so it stops happening, or make handling i t routine.
Act first. Avoid it or change the plan. Name an owner and a date this week, and check progress weekly.
Accept it. Keep the line in the register, do nothing, and revisit once a quarter.
Prepare rather than act. Define the warning sign and who does what when it fires, then move it to monitoring.
How to think abou...
Example moves
What to record
Avoid
Take the cause out of the plan - cut the scope or pick an other approach.
Drop the unproven technology and use the option you've al ready shipped.
Why it was dropped, and what replaced it.
Reduce
Lower either the likelihood or the impact. The workhorse response.
Prototype early to prove it out, or pull work forward to build slack.
The action taken, and the score after it.
Transfer
Move the exposure outside the team through contracts or i nsurance.
Renegotiate the deadline clause, outsource it, or buy a s upport contract.
Who carries it now, and what stays with you.
Accept
Live with it deliberately - which is not the same as igno ring it.
Set aside contingency and a fallback, then move it to mon itoring.
Who accepted it, and when it gets revisited.
Review monthly, not weekly Weekly never sticks. Take 30 minutes at the st art of the month and update only what changed.
One owner per line The team won't do it. Put a name and the next review date on the card.
When to close a line The assumption is gone, the window has passed, or it landed and became an issue.
Questions for the review What's new this month? What scored higher? Whose response has stalled?
ドラッグで移動・ホイールで拡大縮小