FN SDK RISK REGISTER

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

 

 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

 

 SDK3

SDK4

SDK5

 SDK1

SDK6

SDK7

 

Reference

Type

Risk

Mitigation

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

SDK4

Firmware Updates

If devices get firmware updates during dev phase, and it negatively affects functionality or changes interfaces, it may impact schedule

Postpone firmware updates?

Leave some devices un-updated?

Set up firmware discussion

SDK5

No test tools or user manual

No test/verification tools or user manual make developing for and testing of the device harder

Coordinate with Jabil - user manuals provided but still a risk

SDK6

UWP

Access to Windows native BLE stack in may require Unity project to target UWP.
May affect integration with existing VictoR app

Investigate using Windows SDK w/o UWP target.
Build BLE interface as standalone app.

May not be a risk as they are already using UWP

SDK7

X-platform support

Initial research suggests it may be difficult to create a cross-platform SDK that requires OS-specific functionality

Extend development phase?
Scope OS or protocol specific implementations to separate phases? Android USB not required

May need to clarify with FN (Should take place week of feb 08)

 

 

 

 

 Action items