Impact
Priority and Funding
Normal IS priority. Note this the priority 1 project within SSP programme
Funded by Core SSP funding
Impact and Dependencies
- Dependency from Tribal (SITS vendor) to make the changes required to the HESA table hosting the new code. They are required to apply some of the changes in SITS and to all the downstream components.
- Dependency from SITS software upgrade SAC083. Dates are Dev upgrade in Dec19, Test upgrade in Jan 20, Live upgrade 8 March 20. PM to manage dependency across programme for downtime periods
Impact for the completion of the next statutory return with February onwards being the validation of data. Hard deadline.
-Feb- hard deadline for go live to meet 19/20 stat returns/data validation
-Before peak in March and after course roll forward in Jan
Project Risks
|
Ref |
Title-Description
|
Impact |
Probability |
Mitigation |
Risk Owner |
|
|
1 |
(dependency) Tribal does not deliver the changes in time |
High |
Medium |
Have consulted with Tribal and informed them of our timeline. We are aware they are planning work and current delivery date is Jan 2020 Also raised with team leader so that it can be addressed at the next technical meeting in Dec |
Defeng Ma |
|
|
2 |
(dependency) Because the SITS upgrade is scheduled early March20, HECoS changes are applied in February onto the old SITS version of SITS (9.7.0) |
Medium |
High |
-Option 1 (accept) can the Student Data team work in Feb in Test rather than Live to validate the data for statutory return? Assume Test is refreshed with Live data prior to being upgraded in Jan. Con: Student Data team has to rekey data changes post live upgrade in March. -Option 2: Retain risk and Student Data team validate data using Live old version for a month. Con: further work to re- validate data against new version when it is upgraded |
Franck Bergeret |
|
|
3 |
As a result of the Project Manager move to Core Systems, the project does not get the required drive to complete its objectives |
High |
High |
Raised issue with IS Apps. Requested additional PM resource on SSP programme. In the meantime programme manager is covering this project |
Muriel Mewissen |
|
|
4 |
As a result of planned industrial action in Nov/Dec, there is a risk of delay in the build |
Moderate |
High |
Monitor build progress and escalate to Dev team leader if required |
Defeng Ma |
|
|
5 |
The BA effort is greater than the BA days available |
Moderate |
Low |
Reduce- resource secured to help processing the conversion to be brought in during Dev conversion in Dec |
Franck Bergeret |
|
|
6 |
The project does not deliver the 2 objectives by early Feb 20 which is a hard deadline for starting the 19/20 statutory returns exercise to validate data to be returned |
High |
Medium |
Review where the showstoppers are with sponsor. Escalate to programme owner to divert SSP resources. |
Paula Webster |
|
|
7 |
Availability of resources outside student systems control from GaSP |
Medium |
Low |
Confirm priority of GASP work in Dec/Jan |
Lesley Elliot |
|
| 8 | Local required changes are not being done by the business | Moderate | Medium |
Risk owner is responsible to communicate the changes. But the local changes will need to be done by the business as owner of local reports |
Paula Webster | |
| 9 |
|
Moderate |
Medium | Secure SSP tester to QA the data reference and functional changes applied to key processes like CCAM (course creation and maintenance), so that Operations staff QA/check on behalf of users | Franck Bergeret |