Report for February 2022

Project Info

Programme Manager's Commentary

COM045

IDM Database Upgrade

Compliance

Milestones

Milestones

RAG Status

AMBER

Report by Chris Konczak for February 2022

Achievements this period

• DSOR signed off
• Agreement for further upgrade to Oracle 19 to be handled by an INF project

Issues

• Due to time constraints on the Project Manager, the closure report has been delayed. This has been due to more time being spent on a SAC088 which is a "Highest" priority project and is currently under a red RAG status. It is anticipated that the closure date will be 18/03/2022

Next Steps

• Project Closure

COM059

VRS Rewrite

Compliance

Milestones

Reviewed due to re-prioritisation based on SW Dev resource availability. Proposed new milestones:

RAG Status

AMBER

Report by Colin Watt for February 2022

Achievements this period

• Further user exploratory testing sessions completed during February.
• Rework on APIs continuing to ensure transactions are robust. Some additional integration work necessary due to interaction points with the Card service.
• Security patching of Library patron self reg java app in progress.
• Latest SharePoint UI build contains some library functionality, and functional account features.

Issues

• Some impact on library work due to industrial action (Library staff and DevTech staff).
• SW Dev resource availability continues to present challenges to the scheduling work on the critical path. Timeline has been pushed out to ensure the solution is fit for purpose. Milestones to be revised in agreement with Project Sponsor.

Next Steps

• Complete the SharePoint build
• Progress Data Migration tests
• Progress UAT plan
• De-scope the IDM components and split into separate in-year project.

COM061

Annual JIRA Upgrade

Compliance

Milestones

RAG Status:

BLUE (Suspended)

Report by David Watters for February 2022

Achievements this period

• Project suspension extended to late March; P&M staff cannot allow downtime

Issues

• Deployment dates for second upgrade still to be finalised with P&M

Next Steps

• Remove project from suspension
• Upgrade LIVE with second upgrade

COM063

Serengeti Bi Annual Upgrade

Compliance

Milestones

RAG Status

AMBER

Report by David Watters for February 2022

Achievements

• Agreement reached with vendor on upgrade costs

Issues

• Planning milestone several months behind schedule

Next Steps

• Commence planning communications with vendor
• Prepare project brief/plan
• Establish upgrade requirements

COM064

Annual Business Objects Upgrade

Compliance

Milestones

RAG Status

AMBER

Report by David Watters for February 2022

Achievements

• Completed upgrade of DEV environment
• Sign-off of build work
• Training team used DEV for preparation of videos and documentation
• Decision taken to progrees to upgrade in TEST

Issues

• Configuration of SSO requires further work
• Upgrade in TEST delayed by a few days because of industrial action
• P&M/Finance have requested project be suspended because of their workload

Next Steps

• Complete upgrade of TEST environment
• Carry out UAT with business users
• Continue to engage user community with familiarisation and training
• Make final decision on deployment to LIVE

RAG Commentary:

The current status is Amber because, although progress is being made in line with the project plan, there are two risks that could impact the deployment into Live. One is the impact of recent industrial action, and the other is the recent demands from P&M/Finance that the project team delay going live as it may cause problems for them. This has been addressed and mitigated but things can change.

COM065

Annual Service Audits

Milestones

(Note that these milestones are indicative and will be formalised once Project Brief approved)

RAG Status

GREEN

Report by Ailsa Glass for February 2022

Achievements this period

• Project Brief updated and circulated for sign off 

• Successful recruitment of student testers  

• All key project resource secured 

• Regular project meetings underway 

• Key applications and websites for prioritisation agreed within the Project Team 

• Project Plan produced and circulated around the project team for review and comment 

• Initial discussion with staff journalist with a view to producing an article in the coming weeks 

Issues

• Kit for the testers is being secured. This may be tight in advance of them starting employment. 
• The Planning milestone (scheduled 17/02/22) has been missed and is now out of tolerance. This is partly due to industrial action and the availability of resource. A Change Request will be submitted to Apps Review in due course. This delay should not impact overall deliver of the project. 

Next Steps

• Project Brief to be signed off by Project Stakeholders and submitted to Apps Review 

• Change Request to be submitted to Apps Review re change of Planning Milestone date 

• Audit approach and scope to be finalised 

• Kit for student testers to be secured 

• Training of student testers to be undertaken 

• Project Plan to be agreed by Project Stakeholders and uploaded to the Projects site 

• Planning Milestone to be completed 

This project is reporting GREEN as project activities are on track. However, there has been a missed milestone (Planning due 17/02/22). This is largely due to industrial action and availability of resource. A Change Request will be submitted to Apps Review with a revised date in due course. It is not envisaged that this delay will adversely impact the project. 

COM066

Bi-Annual Grouper Upgrade

Milestones

(All dates are indicative at this stage)

RAG Status

AMBER

Report by Stephen Stanley for February 2022

Achievements in last period

• Initial project brief released for team review 21/02/22
• Continued with project plan and agree resource schedule across all teams 

Issues

• Delay with planning sign off. This has been primarily due to delays in confirming Grouper upgrade details from Dev Tech/ITI due to staff availability in regards to a new mandatory container software architecture. Also due to new PM’s familiarisation with planning process
• The delay to planning means that we do not yet have details on the work to be carried out and confident estimates for these tasks. This means that we do not yet have a definite plan and milestones, and so cannot confirm the dimensions and timings of the project at this time.

Next Steps

• Establish the scope of the work that needs to be carried out, and by which teams, so that realistic estimations can be conducted
• Prepare a plan based on the above WBS and estimations and book resources as required
• Commence the analysis & design work that is needed
• Confirm environment details with Dev Tech staff from Thursday 03/03/22
• PM to confirm with stakeholders their approval of a revised brief and resource plan and submit to Apps Review 10/03/22

RAG Commentary

Description: Technical requirements yet to be confirmed. Key resource availability is compromised by potential impact of commitment to other projects of the same or higher priority.

Impact: This puts the estimated delivery dates for 21/22 at risk. But current planned activity can continue without intervention.

Plan: PM to work with technical team, when available, to agree plan and resource.

COM067

WIKI Annual Upgrade

Milestones

RAG Status

GREEN

Report by Chris Konczak for February 2022

Achievements this period

• Planning meeting completed and project brief circulated for approval
• Resourcing assigned

Issues

• None

Next Steps

• Signoff planning phase
• Start the Database upgrade on DEV

COM069

Committees’ Intranet: Update end of life components

and tightening of security and compliance

Milestones

(Note that these milestones are indicative and will be formalised once Project Brief approved)

RAG Status

GREEN

Report by Ailsa Glass for February 2022

Achievements this period

• Introductory meeting held with Programme Manager and Project Sponsor

• Project Stakeholders have been identified and are being secured

• Initial project meeting set up

Issues

• The users of Committee Intranets are diverse with a variety of external and internal use. Ensuring a diverse project team to represent the different types of users is important but also a challenge. Key user groups have been identified and discussions are underway to have named resource allocated to the project.

Next Steps

• Stakeholders to be secured

• Introductory project meeting to be held with regular project meetings set up

• Estimation Log to be produced

• Project scope to be reviewed and agreed

• Project Brief to be prepared and reviewed by stakeholders

• Project Plan to be agreed by Project Stakeholders and uploaded to the Projects site 

• Risk Log to be produced

• Project Brief signed off by Project Stakeholders and submitted to Apps Review 

• Planning Milestone to be completed   

This project is reporting GREEN as project activities are on track. However, the recent Industrial Action has contributed to difficulties securing stakeholders which may delay completion of the Planning milestone. Given that this project is not due to compete until the next financial year, it is not envisaged that this delay will adversely impact the project. 

COM057 Wiki Crowd Implementation 

Closure Report

Closure Milestone

Closed on 15/09/2021

COM055 O365 Staffmail Migration

Closure Report

Closure Milestone

Closed on 04/11/21

COM062 Qlik-Sense and Qlikview Annual Upgrade

Closure Report

Closure Milestone

Closed on 25/02/22