Risks - XYZ Project

Probability Key Severity Key

High (H) - Critical Path Risk. If realised the resulting issue w
High (H) – 90% Probability of risk being realised.
delivery dates.

Medium (M) – If realised the resulting issue would cause sl

Medium (M) – 60% Probability of risk being realised.
would have an immediate effect on overall cost /project deliv

Low (L) – If realised the resulting issue would not impact de

Low (L) – 50% Probability of risk being realised.
deliverables.
Log No

Type
Description Mitigation Strategy
1 Clarety project board meeting was held over B See if we can engage he use of a hired test server
the telephone with Julius Caesar (AZW from XYZ Ltd.
Insurance) he stated that the test server
would not be set-up on time (targeted
27/04/04). This will cause slippage to the
migration work
2 P

3 T

4 T

5 B

6 T

7 T

8 P

9 P

10 P

11 B

12 B

13 B

14 B

15 B
k. If realised the resulting issue would immediately impact cost / project

e resulting issue would cause slippages in deliverable release dates but

fect on overall cost /project delivery dates.

ulting issue would not impact delivery dates but could impact the quality of
Probability
Severity

Target
Owner

Date Resolution Days

Identified Date Overdue
H H JF 1/31/2008 3/26/2008 940

H M BF 1/31/2008 9/12/2008 770

L M BF 1/31/2008 10/13/2008 739

M M BF 1/31/2008 9/10/2008 772

M H BF 1/31/2008 9/10/2008 772

M M BF 1/31/2008 9/10/2008 772

M M BF 1/31/2008 9/10/2008 772

M H BF 1/31/2008 9/10/2008 772

M M BF 1/31/2008 9/10/2008 772

H M BF 1/31/2008 10/13/2008 739

L M BF 1/31/2008 8/2/2008 811

M M BF 1/31/2008 7/3/2008 841

H M BF 1/31/2008 6/8/2008 866

L M BF 1/31/2008 9/8/2008 774

M L BF 1/31/2008 10/13/2008 739

 Issues - XYZ Project

Issue Type Key Impact Key

High (H) - Critical Path issue. Non-resolution will effect tar
B- Business
P - Project Medium (M) - Non-resolution will cause slippage but not an
D – Development dates.
S – Security
Low (L) - Non-resolution will cause slippage/effect quality b
Log No

Type
Description Resolution Strategy
1 Clarety project board meeting was held over B See if we can engage he use of a hired test server
the telephone with Julius Caesar (AZW from XYZ Ltd.
Insurance) he stated that the test server
would not be set-up on time (targeted
27/04/04). This will cause slippage to the
migration work
2 P

3 T

4 T

5 B

6 T

7 T

8 P

9 P

10 P

11 B

12 B

13 B

14 B

15 B
e. Non-resolution will effect target release dates.

on will cause slippage but not an immediate effect on target release

ll cause slippage/effect quality but will not impact delivery dates.

Target
Impact

Owner

Date Resolution Days

Identified Date Overdue
H JF 1/31/2008 3/26/2008 940

H BF 1/31/2008 9/12/2008 770

L BF 1/31/2008 10/13/2008 739

M BF 1/31/2008 9/10/2008 772

M BF 1/31/2008 9/10/2008 772

M BF 1/31/2008 9/10/2008 772

M BF 1/31/2008 9/10/2008 772

M BF 1/31/2008 9/10/2008 772

M BF 1/31/2008 9/10/2008 772

H BF 1/31/2008 10/13/2008 739

L BF 1/31/2008 8/2/2008 811

M BF 1/31/2008 7/3/2008 841

H BF 1/31/2008 6/8/2008 866

L BF 1/31/2008 9/8/2008 774

M BF 1/31/2008 10/13/2008 739

 5.4 Risk Management Performance Metric - Weekly
Metric Wk 1 Wk 2 Wk 3 Wk 4
Total Number of open risks 10 20 30 40
New risks logged 8 9 8 9
Total Closed this period 2 1 2 1
Total Number of (H) high severity (H) high probability risks 9 18 25 30
New (H) high severity high probability risks 4 5 5 6
Total Closed this period (H) high severity (H) high probability risks 2 1 2 1
No of risks exceeding target mitigation dates by >14 days 0 10 20 30
No of risks exceeding target mitigation dates by >14 days which are (H) high
severity (H) high probability 0 5 10 15

Aggregate Risk Management Performance

40
Total Number of New risks logged Total Closed this
open risks period
30

20

10 9 9
8 8

2 1 2 1

Wk 1 Wk 2 Wk 3 Wk 4

High Severity High Probability Risk Mitigation Performance

30

25
Total Number of New (H) high Total Closed this
(H) high severity severity high period (H) high
(H) high 18 probability risks severity (H) high
probability risks probability risks

9
5 5 6
4
2 1 2 1

Wk 1 Wk 2 Wk 3 Wk 4

Risk Age Performance

30
No of risks No of risks
exceeding target exceeding target
mitigation dates mitigation dates
by >14 days by >14 days 20
which are (H)
high severity (H)
15
 Risk Age Performance
30
No of risks No of risks
exceeding target exceeding target
mitigation dates mitigation dates
by >14 days by >14 days 20
which are (H)
high severity (H)
15
high probability
10 10

0 0
Wk 1 Wk 2 Wk 3 Wk 4
5.3 Issue Management Performance Metric - Weekly
Metric Wk 1 Wk 2 Wk 3 Wk 4
Total Number of open Issues 20 30 20 10
New Issues logged 10 20 5 2
Total Closed this period 0 10 10 10
Total Number of (H) high impact issues 10 15 10 0
New (H) high impact issues 5 10 2 0
Total Closed this period high impact issues 0 5 5 5
No of issues exceeding target resolution dates by >14 days 2 3 4 5
No of issues exceeding target resolution dates by >14 days with (H) high impact 0 5 3 5

Aggregate Issue Management Performance

30
Total Number of New Issues logged Total Closed this
open Issues period

20 20 20

10 10 10 10 10

5
2

0
Wk 1 Wk 2 Wk 3 Wk 4

High Impact Issue Resolution Performance

Total Number of 15New (H) high Total Closed this
(H) high impact impact issues period high impact
issues issues
10 10 10

5 5 5 5

0 0 0
Wk 1 Wk 2 Wk 3 Wk 4

Issue Age Performance

5 5 5
No of issues No of issues
exceeding target exceeding target4
resolution dates by resolution dates by
>14 days >14 days with (H)
3 high impact 3

0
Wk 1 Wk 2 Wk 3 Wk 4