Project Risk Register: Score by Likelihood and Impact, Act Early

プロジェクト管理・開発

Project Risk Register: Score by Likelihood and Impact, Act Early

Opened by the project lead in the first week, then reopened at the monthly risk review. The whiteboard leads with a likelihood-by-impact matrix that sets priority, plus a mindmap of where risks come from, a table of the four responses - avoid, reduce, transfer, accept - and the rules that keep the register from going stale. The task board runs from Identified through Assessing, Responding and Monitoring to Closed, and starts with five parent tasks - identify, score, respond, monitor and review - each with its own subtasks.

0 いいね 0 コピー 作者: WeProcess
risk management risk register likelihood impact scoring mitigation
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 Project Risk Register: Score by Likelihood and Impact, Act Early

ホワイトボード プレビュー

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 &amp... Warning signs &am... Scoring notes &am... GoalFewer scrambles after the fact. Decide up front who does what, and when, if the risk lands. How to write a lineUse: because of , happens, and follows.e.g. Approvals drag on and work starts two weeks late. What not to logSomething already happening is an issue, not a risk. Issues belong on the task board as cards. Easy to missPeople (departures, crunch), outside parties (vendors, approvals), assumptions (specs not yet fixed). 2. Where Risks Co... Sourcesof risk Schedule Waiting ondependencies Technology Unproventech choices Requirements Specs stillin flux People Turnover,peak workload Vendors Delays andapprovals Cost & legal Overruns,contract terms 縦軸: Likelihood (l... Small each time, but they add up. Change the process so it stops happening, or make handling it 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 another approach. Drop the unproven technology and use the option you've already 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 insurance. Renegotiate the deadline clause, outsource it, or buy a support contract. Who carries it now, and what stays with you. Accept Live with it deliberately - which is not the same as ignoring it. Set aside contingency and a fallback, then move it to monitoring. Who accepted it, and when it gets revisited. Review monthly, not weeklyWeekly never sticks. Take 30 minutes at the start of the month and update only what changed. One owner per lineThe team won't do it. Put a name and the next review date on the card. When to close a lineThe assumption is gone, the window has passed, or it landed and became an issue. Questions for the reviewWhat's new this month?What scored higher?Whose response has stalled?
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Identified 16件

Identify the risks
Score every risk
Decide the response
Watch for triggers
Review each month
List by category
Revisit past misses
Merge duplicates
Agree the scales
Score on both axes
Sort the top risks
Set owner and date
Define the triggers
Set a review cadence
Update the scores
Close settled risks

Assessing 0件

Responding 0件

Monitoring 0件

Closed 0件