Report compiled by David Watters (Programme Manager) for Alex Carter (Programme Sponsor)
Section 1: Programme Summary
Programme Manager's Commentary
There are several positive points to report this month, with progress being made on the majority of COM projects in March, but there is still that lingering risk of some projects being mired in uncertainty around getting things finally completed. This is simply down to the type of circumstance for which we cannot always plan - absences, unforeseen testing issues - and is frustrating for all involved as there is a lot of good work getting done and much time and effort going into seeing things to the finishing line.
The IDM DB migration project has recently hit a problem in integration testing and the project team are now working through a potential solution. This is likely to impact the delivery date and the effort required. The project has been reported as Amber for these reasons.
The O365 Security Hardening project has had to be adjusted dates-wise again. The Amber status is due to these modifications.
The Staffmail migration work is reported as Amber again. There was a need to replan some 'missed' migrations, hence this status.
The Wiki Crowd Implementation project has continued with the completion of the DEV build and installation. The next steps include the integration with other internal systems and the build in TEST.
The VRS Rewrite project is AMBER due to the delay on the design decision on the VRS components. The project is expected to return to GREEN next month. There continues to be a lot of effort put into advancing this one.
So, overall the programme has more Amber than Green projects, but the current reasons for these are recognised and being addressed. It is hoped that these latest solutions do indeed help us to advance the batch of open projects. One other thing to report is that COM060 (MFA Rollout Support) has been withdrawn for 2020/21. This leaves the Qlikview project as the only COM project to start and this is still planned for early June.
Changes have been made to the auto-forwarding text and all that is now needed for the final version is the link to the request form – Service Management will provide this
The tasks to complete the auto-forwarding work have been held up due to a pivotal member of staff in Service Management being on sick leave. Interim revised dates were therefore submitted to WIS though these may be revised depending on when he returns to work and how soon the tasks can be completed. The piccl to extend the delivery and closure dates was submitted to WIS 30/3/21(piccl22)
Sponsor has asked for a team meeting to review and refresh the roll-out plan – is on 9 Apr 21
Service Management to provide link to request form for auto-forwarding comms
Rescheduling of dates for delivery with Service Management and ITI
Handover within Service Management on how set up comms
Service Management to recheck the flow for the authorising side of things (as it has been in place for a while so needs to ensure it runs as it should)
Service Management comms (Schools and Colleges Leads - copying in Abdul Majothi, Relationship manager; Users in the current email forwarding group) to be sent out 2weeks before deployment date
Project comms (Helpline and EUSA) to be sent out 2weeks before deployment date
Description: Project is Amber because of all the delays to auto-forwarding being complete
Impact: Costs continue to rise the more the project is extended
Plan: If not delivered by new revised dates then a decision will need to be taken by Project Sponsor whether to close or suspend the project
ADA and System Design (IDM) and Design Review (for IDM) held. The Design Review milestone was replanned to allow a separate design document for the VRS component to be included.
A Demo of the VRS components using SharePoint was held. This demo was positively received however, some further work needs to be completed in order to confirm SharePoint as the solution. The demo was created without the need for any additional license costs, only using the campus licenses already in place.
Good progress has been made on the IDM component build. The focus is on developing the IDM read and write micro services. idmread-ms/idmwrite-ms microservices
Initial comms were sent out to all stakeholders. The comms included a short questionnaire. Based on the feedback we are planning to hold a limited number of workshop type sessions to gather information about how each individual school use the current VRS in their processes. The project does at they stage not plan to complete a full business requirements, instead we will use the outcome of the stakeholder sessions and the comprehensive requirements completed under COM011.
The decision regarding the BVRS solution is taking longer than expected. This design will be based not only on the SP Demo and accompanying design document and estimates. Head of Development Services has requested that an estimate to build the VRS solution in Python is also considered. This estimate is currently outstanding.
Complete and estimate the design document for VRS components
make a decision on the solution for the VRS components
Plan out stakeholder workshops
Continue building the IDM components
Continue with technical build documentation
AMBER: The project is AMBER due to the delay on the design decision on the VRS components. The project is expected to return to GREEN next month.