Closure Report
Project Summary
This project saw a number of enhancements being made to the SPQS system.
- The updates to the code were deployed on the 12th December, 2019.
- Sign-off of the OLA was provided on the 19th February, 2020.
Regular meetings were held with good attendance and which allowed for review of progress and agreement on prioritisation of work.
The present Project Manager would like to acknowledge the role of others for their contribution to the successful delivery:
| Name | Business Area | Role |
|---|---|---|
| Alistair Duthie | Enhancement and Quality Assurance | Academic Administrator |
| Gavin Pennycook | Software Development | Developer |
| John Allison | Software Development | Developer |
| Brian Denholm | Production Management | Applications Support Analyst |
| Suran Perera | Production Management | Production Manager |
| Veronica O'Malley | Service Management | Service Manager |
Analysis of Resource Usage:
Resource Estimate: 54 days (original planning budget)
Resource Actual: 98 days
Resource Variance: 81%
Explanation for Variance
The project remained open for an extended period in order that the content of the OLA could be agreed amongst project stakeholders.
There was a change in Project Manager so a degree of familiarisation had to be taken into account.
Outcome
Twelve project risks were raised over the duration of the project and covered:
- Planning
- Resourcing
- Budget
- Delivery time-lines.
Six change records were raised over the duration of the project and covered:
- Change in Project Manager
- Change in budget
- Changes in project milestones.
| Reference | Description | Priority (Moscow) | Delivered ? |
|---|---|---|---|
| O1 | To Implement functional enhancements, as identified by members of the CAHSS College QA Committee and SCE College representatives. | ||
| D1.1 | To perform SPQS system configuration changes to programme-level report template/s, so that GPDR breaches can be identified. | Must | Yes |
| D1.2 | To perform updates to the current SPQS system design, so that there is reporting capability for CAHSS courses that do not form part of a specific programme | Should | Yes |
| D1.3 |
To complete SPQS report formatting enhancements, which would support more effective transfer of MS Word documents, without further re-editing in SPQS. |
Should | Yes |
| D1.4 | To perform SPQS report tracking enhancements, as identified in the HSS029 Business Requirements Document (BRD). | Should | Yes |
| D1.5 | To deploy approved HSS029 system configuration changes to Production | Must | Yes |
| D1.6 | To perform post-deployment support for HSS029 deliverables from Deployment date until Project Closure | Must | Yes |
| D1.7 | To coordinate project-related communications to HSS029 stakeholders | Should | Yes |
| 02 |
To perform review of and consider options for revisions to the current system support model for SPQS, including the underlying Operational Level Agreement (OLA). |
||
| D2.1 |
To review the current OLA for SPQS, identify and implement ‘quick win’ process improvements including:
https://www.wiki.ed.ac.uk/pages/viewpage.action?pageId=338333604 |
Must | Yes |
| 03 | To extend the SPQS support model to the other colleges in the University (SCE and MVM) | ||
| D3.1 |
To develop a roadmap for implementation of the SPQS support model beyond CAHSS. This work would involve identification of:
|
Should | Yes |
Key Learning Points
- The use of Microsoft Teams might have been helpful in getting more immediate responses over that of eMail.
- Having the original developer on hand meant that there was wider knowledge transfer across the team.
- The effort involved in concluding the OLA was greater than anticipated.
Outstanding Issues
The following Jira's were deemed not imperative to successful project delivery. They have been noted as 'Won't Fix' and will be for consideration in any future development or enhancements to the SPQS system. Project budget focused on 'Must Haves':
|
JIRA Issue |
Description |
Owner |
MOSCOW Rule |
|
UUN dynamic User Lists |
John Allison |
Could Have |
|
|
Configure Oracle DB to run automated tests |
Gavin Pennycook |
Un-prioritised |
JIRA 4 - Although the original MS-Word support request was resolved, a follow on request was made to allow for colour coding of text. This was rejected and accepted by the business as not achievable within the time of the project. It is noted for future consideration.