Notes

I wanted to summarise the current status of the Scheduler deployment at the Southampton site.
Several data issues have been identified with the Scheduler deployment. While some changes have already been made, there are pending fixes that require a live copy of the database and additional storage space on the customer site. Compounding the situation, our developers were pulled into other projects, which has impacted their availability to address these fixes promptly.
Database changes and fixes: The responsibility for making the required database changes and applying fixes lies with the database team. However, it has come to my attention that approval from the customer is necessary for these changes (getting live copy of the database, extra storage space at customer site). I have been informed that Kayleigh Sheldon is responsible for sorting out the approval, and this action is currently pending. I have reached out to Kayleigh to request an update on the situation, but I am yet to receive feedback.
Estimated resolution date: Unfortunately, when I asked for a task completion date (or estimate), the database team are unable to provide an estimated resolution date for the import issues when asked. They have stated that while fixing current issues, there is a possibility of other issues arising due to the database changes. Additionally, approximately one week is estimated for testing the deployment to ensure its stability.
Documentation and ticketing: To ensure proper tracking and prioritisation, these issues have been documented as a release in Aha! and corresponding tickets have been raised in Jira with high priority status. This will help us monitor and manage the progress effectively.
Weekly follow-up: Given the importance of these data issues, I will be conducting weekly follow-ups on those tickets until the work is completed. This will allow us to stay informed about the progress, address any concerns, and make necessary adjustments if required.
Processes: Thankfully Andy has created an avenue in Aha! to encourage standardising our processes for handling similar requests to avoid encountering such issues in future deployments.