Report for May 2019

Project Info

Project Manager's Commentary

INF134 AP89-023

Logging Data Retention

Milestones              

RAG Status

Green

Report by Ian Mitchell for May 2019

Achievements in last period

• Stefan’s two outstanding actions* from last meeting complete.
• All actions to date complete
• Discussion about policy and entries and references to various technologies
• On track for next milestone – ‘Recommendations for selected key Technologies’ due 21 June
• Next meeting 13 June.

*1. Outstanding action - Stefan – to discuss privacy statements as regards data logging with the DPO, Service Management and the Director of Student Systems (Renate Gertz, Alex Carter and Lisa Dawson).

*2. Outstanding action - Stefan – to go to the OGG and request that the ITI draft policy becomes APPs policy.

Issues

• No major issues. 

Next Steps

• On track for next milestone – ‘Recommendations for selected key Technologies’ due 21 June

INF135

CF10 Updates

Milestones

There is no confidence in these dates due to latest resource issues

RAG Status AMBER

Report by Sue Woodger for May 2019

Achievements in last period

• Retain and FOI apps manually copied to servers on Dev as no working Bamboo plans

Issues

• The major issue on this project is getting Dev resource - The project has been conflicted again. There has been no CF resource available.
• Summary of resourcing issues:
• Had Dev resource booked but he didn’t do the booked work but then we couldn’t get the resource beyond the time he was booked
• Conflicted with FIN119 at the beginning of April - lost as FIN119 was highest priority. Had project raised to Highest
• Further conflicts on Dev time with FIN119 is still ongoing and MLE005 – all three projects are highest priority and INF135 lost out again
• Resource manager suggested that we conflict with HAS002 (sponsor funded project) to get resource but PM on this project kindly gave us 4d from HAS002. However the developer was only able to do 3d due to live issues on EST103 (also highest priority). He is also expecting much more work to come out of EST103 so PM would also be conflicting against this and against HAS002 which is a sponsor funded project
• PM is eating into the budget having to deal with all these resource conflicts. Have escalated to programme manager and project sponsor to ask if we continue conflicting or if we wait until resource is available
• Project sponsor suggested we continue to conflict but there are at least 12 projects using developers with ColdFusion skills. Asked resourcing manager and he has given a list but says that Adrian, Geir and Michael also have CF skills but doesn’t say what projects they are working on. PM has asked resourcing manager which are likely to finish soonest and has asked about John Allison’s time as according to his resource histogram he has capacity 3, 17, 24 June and 15 July. PM has meeting with ProgM after both their leave to discuss how to take forward.
• We are continuing with workarounds to the Bamboo issues but this is not ideal – it is taking more time to do and we will have to revisit once resource is available
• Further issues in the build means we cannot take build forward for the Linux as we need software dev resource to fix the issues that are in jiras
• DevTech resource booked on project from 13 May for Windows work but did not start the work or inform anyone  that work was not started
• Meantime the support for CF10 ran out on 16 May 2019

Next Steps

• Complete build

Commentary: Resourcing still an issue. Description: Despite having priority promoted to highest the project is again having conflict with other highest priority projects and losing those conflicts( latest has been against FIN119 again and MLE005). Impact: We are trying to move apps between environments manually but this is adding to our time to complete plus the time spent in conflicts is adding to the budget. We need Software Dev time for the Windows build but can’t get it without another conflict. Meantime the support for CF10 ran out on 16 May 2019. Plan to resolve issue/manage risk: Escalated to programme manager and project sponsor to advise how we move forward.

INF137

Annual Infrastructure Rationalisation Decommissioning

Milestones

RAG Status

 GREEN

Report by David Watters for May 2019

Achievements

• Final work on updating server listings
• Planning of any decommissions that are 'orphaned'

Issues

• None

Next steps

• Finalise delivery milestone
• Closure of project

INF138 AP89-017

Annual DR Review and Tests

Milestones              

RAG Status

GREEN

Report by Ian Mitchell for May 2019

Achievements in last period

• Heather agreed to arrange amendment to deployment checklist to record system changes.
• Heather finalised TADs and moved to SharePoint for Ewan Scott to review.
• Stefan added a risk to University risk log outlining inability of Production Management to run a DR test due to lack of budget.
•  Milestone 'Agree List of Top and Medium Priority services' completed.

Issues

• No major issues.  

Next Steps

• Review of current DR documentation completed by DevTech and handed to TechMan.
• Meeting set for 10 May to agree DevTech's report dopcument and spreadsheet with TechMan having four days prior to milestone to sign-off. 

INF139 Annual Upgrades of Development Tools + frameworks 18/19 (18-19 Project)

AP89-018

Milestones

RAG Status

 GREEN

Report by Anne Mathison for May 2019

Achievements

Python

• Python  completed UAT in May
• Python  went LIVE on 29-May

Bamboo

• Deprecated code identified affecting up to 40 plans and completed
• Bamboo deprecated 40 plans

Issues

• No issues

Next Steps

Python

• Meeting planned in June with technology Management to discuss how Python should be maintained in the future

ASTA

• ASTA versions to be discussed with the supplier in June
• ASTA requirements will be completed in June
• ASTA JIRAs to be set up for the tasks required in June

Bamboo

• Sign off Bamboo UAT
• Agree and schedule Bamboo Go Live
• Set up Service Alert for Bamboo
• Set up Go Cab for Bamboo
• Bamboo deployed to LIVE

Oracle Grid

• Dev Tech will be looking into Oracle Grid in early June
• Dev Tech will be implementing Oracle Grid in June

Sentry

• Sentry UAT is planned for early June
• Sentry is planned for 2nd week in June

PMP

• PMP UAT in June
• PMP Live Planned for July

GREEN RAG status

INF140 - Middleware Patching Process

Milestones

TBC  M3: Patch Strategies Complete

TBC M4: Initial Patch Cycle Complete

TBC M5: Delivery

31 July-2019 M6: Project Close

RAG Status

AMBER

Report by Karen Stirling for May 2019

Achievements in Last Period

• Two successful patching strategy workshop sessions held
• Significant progress made in creating patching strategies c. 8 remaining to be completed
• Completed patching strategies  have been issued for review at OGG
• Middleware patching calendar created
• Agreement to complete patching for Consul and MS SQL Server
• Cold Fusion Patching has already been completed

Issues

• Remaining strategies to be completed requires further Dev Tech resource, request issued to resource manager for this  to be fulfilled
• Milestones to be reviewed week commencing 11th June once key resource return from annual leave for patching of Consul and MS SQL Server
• Patching activity can happen in parallel with remaining patching strategies to be completed

Next Steps

• Complete remaining strategies
• Revise milestones
• Plan activity for Consul and MS SQL Server

The project is reporting AMBER due to 

Description of issue/risk : Milestones require to be agreed for patching cycle activity which is expected to complete this financial year Impact on project : Budget will be reviewed and unspent days will be returned to ISG Programme Plan to resolve issue/manage risk : Meeting arranged for week  commencing 10th June to map out activity and agreed new dates for remainder of project.

.

INF141 (18-19 Project)

Milestones

RAG Status

AMBER

Report by Maurice Franceschi (for Nigel Binns) for May 2019

Achievements this period

• resource clarification and assignments - not achieved 

Issues

• software development resources still not booked

Next Steps

• resource clarification and assignments to the development team

INF142 (18-19 Project)

Move IS based Oracle databases to VMs and stretched cluster

Milestones

RAG Status: GREEN

Report by David Watters for May 2019

Achievements

• Project brief finalised and approved
• Listings of RedHat/CentOS boxes and server numbers updated

Issues

• Resourcing for 18-19 delayed by staff absence

Next steps

• Familiarisation for colleagues in Dev Tech
• Build of VMs and CentOS version of database
• Work to continue on analysis of server estate and licences required

INF143 - MySQL Environment Migration

Milestones

RAG Status

AMBER

Report by Geoff  Cropley for May 2019

Achievements in Last Period

• Dev and Test servers for pilot applications have been delivered
• Maria DB has been installed and configured on the pilot application Dev Environment including encryption at rest
• As the result of SME absence, these milestones were slightly behind of schedule but the time has been recovered during the reporting period

Issues

• None

Next Steps

• Build the test environments for the remaining services
• Migration of pilot applications to Test servers and commence system testing
• Build UAT plans

The project is reporting AMBER due to;  

Description of issue/risk : The project is moving to deliver and close in 2019-20 however there is no budget agreed as yet for the new academic year. Impact on project: The impact of this will delay the migration of a number of services and prevent the decommissioning of the existing environments. 

Plan to resolve issue/manage risk:  A planning request for 100 days has been lodged to support the activities to complete the migration during 2019-20.

INF145 (18-19 Project)

Protecting Data in the EDW

Milestones

RAG Status

RED

Report by Kevin Hone for May 2019

Achievements

• WIS gave approval to closing the Project Planned Milestone.

Issues

• Assigned resource has been absent through holiday and sickness so momentum on the project has yet to pick-up.

Next Steps

• A Jira project is to be created with an allocation of tasks across the technical resource.
• Technical resource to pickup work.

The project is reporting RED due to;  

Description of issue/risk :  Lack of technical resource involvement/availability since scheduled project start date (due to illness).

Impact on project:  The timescale for delivery is likely to be a challenge. 

Plan to resolve issue/manage risk:  To address the timescale concern, a request is to be made for additional resource to be assigned to the project.

INF127 (17-18 Project)

LAMP / WIMP Platform Upgrade

Closure Report

Closure Milestone

Project Closed 12-Oct-18

Closure Report

Project Closed 3-May-2019

Closure Report

Project Closed 3-May-2019

Closure Report

Project Closed 3-May-2019