FN CONTROLLER UPDATE RISK REGISTER

Owned by Jem Tari (Deactivated), created
Last updated: Feb 14, 2022
2 min read

 

 Background

https://confluence.unity3d.com/plugins/servlet/samlsso?redirectTo=%2Fpages%2Fviewpage.ac[…]LS%26title%3D06_Risk%2BAssessment%2BFN%2BController%2BUpd

 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

 

 

 

 

PROBABLE
Risk will occur

 FNCTRL3

 FNCTRL5

FNCTRL6

FNCTRL7

 FNCTRL1

FNCTRL2

FNCTRL4

 

REF

TYPE

RISK

IMPACT

MITIGATION

REF

TYPE

RISK

IMPACT

MITIGATION

FNCTRL1

Not enough devices

There will be a shortage of victor devices as these will need to be shared with the other project

 

Two weeks loss of development.

 

 

FNCTRL2

Device recall

FN requires devices

 

Impact: Unable to test.

Day to day slide for period that the devices are gone. (expected to be 4 weeks)

Appears to be around Feb 28 - Mar 11 coinciding with S.4

FNCTRL3

Time zone alignment

Client in EU

 

Schedule key meetings 4AM-10AM PST

FNCTRL4

Networking unfunctional

  • Currently networking does not work and a sufficient number of tasks depend on it.

 

Consult with Benoit to find out last working version (as this has allegedly worked in the past). 

FNCTRL5

Firmware updates

  • Request required ICD updates from Jabil and get an accurate timeline of when this will be available.

Some issues we are finding are potentially going to impact firmware.

Set a clear timeline for when required firmware updates will be needed and available so as to track any blockers / unblockers.

FNCTRL6

Multiple Devices

  • Need to find out if multiple devices can be connected to a single session currently and the path to extending that to work with 4 devices.

  • Likely will require UI updates.

 

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

  • To accommodate an ask from FN the Unity team will need to migrate to using FN's DevOps server rather than our internal Github instance. This may interrupt some development.

 

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

Device Mounting

Device seems to flip orientation.

 

Feb 14th we agreed that Unity had addressed this and FN were now dependent on Jabil for a fix

FNCTRL9

 

 

 

 

 Action items