Closure Report
Project Summary
This project was to upgrade the existing Risk Management System (4Risk) from version 1 to version 2.
| Number | Description | Priority | Objective met/delivered (Y/N) | Comments |
| Objective 1 | Build a test environment for 4RISK version 2 | MoSCoW | ||
| D1.1 | Take a copy of the existing live data on 4Risk version 1 | Must Have | Y | |
| D1.2 | Build and configure a new test environment | Must Have | Y | |
| D1.3 | Updated SSO in conjunction with SaaS supplier | Must Have | Y | |
| D1.4 | Successful UAT by Risk Group users | Must Have | Y | |
| Objective 2 | Upgrade live environment to 4RISK version 2 | |||
| D2.1 | Build and configure new live SaaS server with latest 4Risk v2 | Must Have | Y | |
| D2.2 | Migrate live database from existing 4Risk v1 to 4Risk v2 | Must Have | Y | |
| Objective 3 | Advanced user communications and training on 4Risk v2 | |||
| D3.1 | Ensure risk group users have sufficient notice for changes to application | Must Have | Y | |
| D3.2 | Update system and user manuals to reflect version 2 changes | Must Have | Y | The manuals are within the online help included in the v2 of the application |
| D3.3 | Provide in person and online training roadshows to inform and train users on version 2 changes | Must Have | Y | 2 training sessions have been delivered, the second of which was recorded to provide ongoing reference for new users |
Analysis of Resource Usage:
Staff Usage Estimate: 26 days
Staff Usage Actual: 22 days
Other Resource Estimate: £0
Other Resource Actual: £0
Other Resource Variance: N/A
Explanation for Variance
- The project spent 4 days under budget; less project management days were required for managing user testing and resolution than expected.
Outcome
- The system has been successfully upgraded to v2.
Key Learning Points
- Build in more contingency time (timeline) for projects like these where the upgrade presents significant changes
- The recording of the training session worked well and has been accessed subsequently
Outstanding Issues
The following are not issues which prevented the deployment of the application but comments for future reference.
- The project sponsor raised an issue regarding 'risk prefix' in v2 of the application that didn't exist in v1, and has stated this is a degradation of the system. The supplier doesn't have an immediate resolution and instead are looking at it as a product development. Project Sponsor has been shown the workaround by the supplier and noted by supplier for product development, but no immediate date has been provided.
- The supplier has confirmed they will achieve WCAG accessibility compliance at level 'A' by October, when the system is deployed. There are two 'known' accessibility issues being worked on by the supplier in the short term and in the medium term, they are looking at how to achieve 'AA' WCAG compliance. The sponsor is fine with that status for the time being, but the project sponsor will ensure a dialogue is maintained with the supplier post-project.