Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

📋 Background

🤹‍♂️ Risks management

Identify and prioritize risks based on their probability and severity. Then define what further actions you need to take to control the risks, and who needs to carry out these actions.


Risk rating

LOW

MEDIUM

HIGH

EXTREME

  • Acceptable

  • Ok to proceed

  • As low as reasonably practicable

  • Take mitigation efforts

  • Generally unacceptable

  • Seek support

  • Intolerable

  • Place event on hold



LIKELIHOOD

SEVERITY

ACCEPTABLE
Little to no effect on event

TOLERABLE
Effects are felt, but not critical to outcome

UNDESIRABLE
Serious impact to the course of action and outcome

INTOLERABLE
Could result in disaster

IMPROBABLE
Risk is unlikely to occur

 

 

 

POSSIBLE
Risk will likely occur

 

 

 SDK2

 

PROBABLE
Risk will occur

 

 

 SDK1

 

Reference

Type

Risk

Mitigation

SDK1

Devices

Shortage of victor devices at key point during development

Feb28-Mar11 tentative dates - this maps onto sprint 3

SDK2

Short Project

Scope changes will (seriously)impact schedule

Define and control scope from the start of the project

SDK3

Time zone

Client in EU.

Schedule key meetings 4AM-10AM PST

✅ Action items

  •  

  • No labels