📋 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 |
|
|
|
|
| SEVERITY | |||
---|---|---|---|---|
ACCEPTABLE | TOLERABLE | UNDESIRABLE | INTOLERABLE | |
IMPROBABLE |
|
|
| |
POSSIBLE |
|
|
|
|
PROBABLE | FNCTRL3 | FNCTRL5 FNCTRL6 FNCTRL7 | FNCTRL1 FNCTRL2 FNCTRL4 |
|
REF | TYPE | RISK | MITIGATION |
---|---|---|---|
FNCTRL1 | Not enough devices | There will be a shortage of victor devices as these will need to be shared with the other project | Appears to be around Feb 28 - Mar 11 coinciding with S.4 |
FNCTRL2 | Device recall | FN requires devices | |
FNCTRL3 | Time zone alignment | Client in EU | Schedule key meetings 4AM-10AM PST |
FNCTRL4 | Networking unfunctional |
| Consult with Benoit to find out last working version (as this has allegedly worked in the past). |
FNCTRL5 | Firmware updates |
| Set a clear timeline for when required firmware updates will be needed and available so as to track any blockers / unblockers. |
FNCTRL6 | Multiple Devices |
| Find out when we can have access to additional hardware such that at the very least a single developer can test with 2 devices and QA can also test with 2 devices. |
FNCTRL7 | Need to move to FN's DevOps instance |
| Migrate EOD Friday such that all sprint 1 tasks can be worked uninterrupted and if problems occur in the transition they can be identified without sacrificing sprint goals. |
FNCTRL8 |