Section One: Programme Commentary, RAG and Resources Update
In this reporting period, the programme ownership has temporarily transferred to Susan Cooke. The outcomes of the project review have left some unanswered questions with regard to two projects, namely the O365 Staffmail migration and Accessibility Statements. The Office 365 Security Hardening project has been replanned again but has suffered the loss of a key resource. Options to plug this gap are under review.
Due to the overall position of projects the Programme RAG has been set at AMBER.
We are still working with ITI to resolve the firewall issues which were encountered during the go live. The project team are attempting to test connections from SOA to the ITI services but have been delayed due to higher priority work.
Milestones revised but still to be confirmed once we've resolved the issues and agreed a revised go live date with business partners.
Work with ITI to resolve the firewall issues for their services.
Schedule another suitable go live date with business partners.
Amber status as the issues encountered during the go live have not been resolved yet. We expect to make progress w/c 4 May and be able to confirm if the firewall issues have been resolved.
Crowd R&D has been set up in an unobtrusive way so not linked to DEV. Service Management and Dev Tech have been allocated 5 days for installation and R&D. This can now run until the end of the project, or until the 5 days has been used up. There is now no requirement to roll DEV back before we start the upgrade.
Enterprise version of Confluence has now been released. The project has been replanned and resourced. This has got approval at WIS and we have now started on the DEV upgrade.
The deployment of Global Admin Account restrictions is in progress and due for completion.
The email warning banner for ISG was scheduled for deployment at the end of April.
Initial testing of the auto forwarding ban has been completed
CPAG members have yet to confirm whether they wish to opt-in/opt-out of the email warning banner work.
There is no communication strategy in place for the roll-out of the auto forwarding ban.
The Head of Service Management was previously going to oversee the communication strategy for the security hardening changes. In his absence and with his work now being distributed across other Service Managers, the ability to take the work forward quickly is now a new challenge. A re-plan with extended time-lines to absorb the increase in scope amongst existing team members is presently under consideration.
A further re-plan is required to include a communication and roll-out of the auto forwarding ban.
Agreement is to be reached on who is best placed to manage the communication and timelines to achieve.