The Risk Evaluation Framework for the COIN Risk Register
Risk category
|
|
|
F - Financial |
R - Reputation (of LGO) |
U - User Confidence |
I - Data integrity |
S - Service Disruption |
D - Delay in Going Live |
|
|
|
Risk matrix
|
Risk Assessment Residual Risk Ratings |
|||||
|
Impact |
|||||
|
1 (Very Low) |
2 (Low) |
3 (Medium) |
4 (High) |
5 (Very High) |
|
Likelihood |
5 (Very High) |
M1 |
M2 |
M3 |
H2 |
H3 |
|
4 (High) |
L2 |
L3 |
M3 |
H1 |
H2 |
|
3 (Medium) |
L2 |
L3 |
M2 |
M3 |
H1 |
|
2 (Low) |
L2 |
L2 |
L3 |
M2 |
M2 |
|
1 (Very Low) |
L1 |
L2 |
L2 |
L2 |
M1 |
Risk ID |
Risk |
|
Consequence |
Impact |
Control Arrangement |
Likelihood |
Response |
Residual Risk |
Acceptable? |
|
|
|
|
|
|
|
|
|
|
Jun 09 |
|
|
|
Category |
|
|
|
|
|
Previous |
Current |
|
1 |
Requirement is inadequately specified. |
S, F |
System does not meet expectations or development exceeds budget. |
4 |
Conduct business process analysis and involve users in refining specification. Proj Exec to authorise any further spending on development. |
4 |
Maintain Comtrac if system fails. Request additional funds. |
|
H1 |
|
2 |
Extra requirements for new workstreams cause delay and budget overrun. |
F, R, U, D |
System is delayed |
4 |
Prioritise support for existing workstreams if development schedule is compromised. New workstreams have additional funding allocated. |
3 |
Define any additional requirements as early as possible. |
|
M3 |
|
3 |
Supplier is unable to deliver an acceptable solution by April 2010. |
R, S, U, D |
System implementation delayed and/or contract with supplier broken. |
4 |
Good project management by LGO, CAS and IPL. |
3 |
Maintain Comtrac if system not delivered on time.
|
|
M3 |
|
4 |
Solution fails to meet Requirement |
S, U |
Users lose confidence in system. Contract dispute. |
4 |
Ensure that users are involved in system development. Address any issues in a timely manner. |
3 |
Maintain Comtrac if system unacceptable.
|
|
M3 |
|
5 |
Unavailability of key project staff |
D, F |
Cannot meet development timetable |
4 |
Set out development timetable clearly and prioritise project above other commitments. |
4 |
Do not hesitate to provide cover for potential long-term unavailability. |
|
H1 |
|
6 |
Increase in development costs |
F |
Budget pressures on other LGO expenditure or reduced requirement |
3 |
Good project management by LGO, CAS and IPL. |
4 |
|
|
M3 |
|
7 |
Inadequate training given to staff |
U |
Ensure training programme in place early. |
3 |
Good project management by LGO, CAS and IPL. |
2 |
|
|
L3 |
|
8 |
Infrastructure does not support new system |
S, U, D |
Identify and action any upgrades before end of December 2009. |
4 |
WAN upgrade scheduled for December. Minor LAN alterations in August. Consider replicating servers. |
2 |
Work in hand to upgrade network. Work with IPL to investigate server replication. |
|
M2 |
|
9 |
Data migration is not 100% successful |
R, U, I, S, D |
Need to spend time and effort cleaning up data or reworking migration exercise |
5 |
Test migration out early. |
3 |
Incorporate in project plan. |
|
H1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|