Section One: Programme Commentary, RAG and Resources Update
In this reporting period, progress has been made across the programme. The Accessibility Statements project has delivered and now closed. The IDM DB project has completed build with DEV signed off during this month. As planned, the Wiki Crowd Implementation project started. The programme notes two AMBER projects.
The first project is the Staffmail to O365 Migration. The project management has been handed over to a project manager in Applications. The team have now signed off the migration plan and resources have been secured. The project is expected to return to GREEN after the first week of migrations. The second AMBER project is COM059, VRS Rewrite. This project has not started yet, the start has been delayed until late November 2020.
TEST and LIVE VM environments received from ITI and work has commenced on building the database environments. No work will happen to migrate or switch over the databases until we receive the go-ahead from the People and Money project.
Due to People and Money requiring access to the TEST environment for UAT, it has not been possible to complete the TEST upgrade by the stated milestone. This project is to be re-planned to run behind People and Money. The COM045 Project Manager has reviewed the dates with the People and Money Test Manager, and it has been agreed that COM045 can switch TEST over to the new VM and database after 13/11/2020.
LIVE deployment is likely to happen at the end of January / start of February. This is due to start of term activities by Student Systems during January.
Sue Woodger took over as project manager on 2 October 2020
New project meetings set up
PM met with Veronica O'Malley to discuss comms with Helpline
PM met with Abdul Majothi, relationship manager, to discuss his role and his requirements around comms
PM revisited milestones and budget and piccl 16 was approved by WIS moving closure out to 10 Dec 20 and increasing budget by 10d (from 100d to 110d with split 19/20 73d and 20/21 37d))
Communications meetings held for Comms plan for warning banner
Comms sent out by Project team on 28 October and by Service Management on 30 October
Original deployment date for the warning banner was 28 October. However key members of staff who were sending the comms were off wb 19 October. As communications are important in this change it was agreed at Go-Cab to delay the deployment by one week to allow comms to go out
Project management has been handed over to Tim Gray, PM time will be coded to COM Programme Management
Fiona Vine will pick up the crucial role of Business Lead
Revised plan for migrations has been agreed
Resources for a 12 step migration between 09.11.2020 and 20.12.2020 has been agreed
Quest resources for migration have been secured
Two migrations are scheduled each week from 09.11.2020, 1. Tuesday starting at 17:00 and Thursday at 17:00 hrs. The migrations should be completed by 10:30 the following day, with the new (O365) mail routing enabled by 11:00.
Resource issues in Service Management have continued to impact on the project
The plan to start migrations on October 27th was delayed, this has resulted in a negative impact for colleagues in SCE.
Prepare batches of accounts for migration
Update all help pages including creating new FAQs
Issue comms to account holders prior to their migration. One mail 7 days prior and a final confirmation the day before migration.
AMBER as the project has encountered delays with scheduling due to resource availability in Service Management. The resourcing has now been resolved with the first migration scheduled to start on 10.11.2020.
These milestones (apart from the warning banner) require to be revisited and re-planned
Report by Chris Konczak for October 2020
Achievements this period
Agreement made to proceed with project. There was initial concern as Atlassian are discontinuing their self-hosted server products from 2024, so the installation may only give a limited lifespan. The decision was made to go ahead with the implementation, but to add in an objective to minimise the user account cost if we go ahead with the SAS solution in the future. This could be similar to the approach used by TestRail.