Thursday, August 19, 2010

Project Plan post 3: Risk Analysis and Success Plan

Risk

Probability

(1-5)

Severity

(1-5)

Score

(P x S)

Action to Prevent/Manage Risk

Staffing (loss of)

2

3

6

Staff time is relatively small, and organisational drive for success should be sufficient to ensure coverage of any staff shortages.

Staff not able to commit sufficiently to project

2

4

8

Effectively this equates to losing HEI partners (as below). One could be tolerated, but not more. Need project manager to keep close check on progress.

Organisational (loss of)

1

4

4

Project is important to the partner institutions. Additionally, with 5 partner HEIs the loss of one partner could be tolerated. Prevention would be for the project to be successful, to ensure continued engagement.

External suppliers (loss of service)

1

4

4

Supplier bills in advance, to ensure resource availability.

Self-archiving barriers still too high

3

4

12

This is one of the central themes of the project. Evaluation processes should allow the project to determine how best to deal with this eventuality.

Success overwhelms staffing

2

2

4

Additional staffing budget will be sought, while the robustness of the repository workflows will be used to hold incoming material.

Storage capacity plans exceeded

1

1

1

Ensure that there is a large amount of storage available early in the project. Make allowances for growing the storage later.

Software performance compromised due to load

1

1

1

Ensure the software runs on adequate production-grade hardware. Monitor system performance.

Lack of academic buy-in

4

4

16

This is one of the central themes of the project. The advocacy strategy needs to be tailored to deal with this issue. Reviewing previous projects’ success and failures should help ameliorate this.

Delayed REF reduces drive for success

3

2

6

Some partners engage in periodic performance reviews which are a driver in addition to the REF. This approach will be considered by all the partners.

Low deposit quality

3

2

6

Availability of RoMEO data during deposit will hopefully help reduce this. Otherwise, the partners will rely on the robustness of the repository workflows to aid in cleaning data, and soliciting appropriate content.



Posted by: Lizzie Dipple

No comments:

Post a Comment