Report for April 2019

DTI026 API Gateway and API Management Tool

Milestones

RAG

RED

Report for April 2019

Achievements in Last Period

• Handover activity undertaken within Development Technology – build documents completed
• Analysis of differences with Cloud solution

Issues

• The Build, testing, handover, acceptance and deployment milestones have been missed due to delays experienced in:

  • resolving the disaster scenario procedure (now resolved).
  • testing, acceptance and deployment being put on hold in order to focus on handover activity in Development Technology and discussions regarding a potential change in scope to WSO2 in the Cloud
• As a result, the Time RAG remains at RED this month as a revised project delivery date is to be agreed pending a decision on project scope and will move back by more than 1 month.

• A suggestion has been put forward to move to trial the WSO2 Cloud solution.  A meeting should take place to discuss how this affects the project scope and existing build, plus the associated impact on timescales and budget.  As a result, scope has been marked as RED this month.

• Development Technology team member leaving post later in May.  Handover activity is underway to pass on the knowledge and document what has been learnt about WSO2, including the associated procedures to deploy it.  Two other team members have been identified to be receive the handover.  Resources have been marked as AMBER for now as other commitments have competed for time, and the handover has not yet been completed.  Cost has been marked as AMBER as some additional cost has been incurred to invest the required time in the handover and involving others.

• Additional time and effort was spent resolving the Disaster scenario, above the original estimates, so the Cost RAG has been shown as Amber due to this pushing the overall project estimate over budget.

• DR/resilience position – the recommendation to externalise the database has been successfully implemented so this issue was closed.

• No decision made on which existing API is to be used first in WSO2.  The sponsor is discussing this with the Business Lead and will confirm.

Next Steps

• Decision to be made on potential move to trialling the WSO2 Cloud solution and impact on project scope

• Confirm re-planned milestones and review budget requirements

• Complete handover activity within Development Technology – specifically working though the deployment steps to ensure continuity of knowledge

DTI028 Maturing the API Infrastructure

Milestones

RAG: RED

Report for April 2019

Achievements in Last Period

• Continued work on Python templates

Issues

• Python APIs build estimate has increased significantly and cannot be absorbed within the existing project budget.  Additional budget will be sought through the sponsorship group.  As a result, the Cost RAG remains at RED this month.

• Resource conflict regarding Security Scanning tasks has meant that they will have to be reassigned for 2019/20.  Time RAG remains at RED this month.  Planning meeting scheduled to review project tasks and estimates against remaining project effort.

• Additional scope to bring in security deliverables from DTI029 into DTI028 confirmed.  As a result, the Scope RAG revised to RED this month.

• Implications of WSO2 moving to the cloud have yet to be incorporated into the project.

Next Steps

• Propose revised budget and timeline for consideration by sponsorship group and programme board
• Work continuation on Python templates
• Work on API standards to be rescheduled

DTI029 Maturing the API Service

Revised Milestones To Be Confirmed

RAG: AMBER

Report for April 2019

Achievements in Last Period

• Work on planning a proposed Target Operating Model work on-going.
• Events API reviewed and new delivery date tbc.

Issues

No New issues

Next Steps

• Completion of D7 Events Utility Booking development deliverables.
• Assign D4 Secure Software Development Standard to DTI028 and updated project schedule accordingly.
• Agree new milestones for project.

DTI018

Continuous Service Improvement APIs

RAG RED

Report for April 2019

Achievements in Last Period

• Work is well underway on the Unidesk API

• Decision taken to progress development using NGINX configuration - NGINX config files are now complete

• Resource assigned in Asta in order to integrate the config into the existing puppet configuration once the API users set up in Unidesk by Service Management

Issues

• Software Development's booking for building the API has expired.  This has been discussed this with the Resource Manager, and a meeting has been arranged with the developer to agree how best to manage the remaining effort on the Unidesk API  – it may be possible to manage this alongside the UWP023 work given that there is still nearly 3d effort remaining on the booking.

• It has not yet been possible to establish the status of the testing of the Pure API – this has been escalated to Service Management.

• Budget is likely to be exceeded by more than 20%

Next Steps

• Complete Unidesk API development, testing and deployment

• Complete testing of Pure API (see issue opposite)

• Start person ID resolver API for EDW (to start after delivery of Unidesk API)

22/12/17 - Project withdrawal approved by WIS 22/12/17 - PICCL Change 6

6/12/17 - Recommendation is to withdraw and review requirements again in 18/19 due to PICCL Issue 5, project risk 5

13/10/17 - Project suspension approved by WIS 13/10/17 - PICCL Change 4

Project closure approved by WIS 23/3/18

5/2/18 - Recommendation is to close project early - PICCL Decision 8

6/12/17 - Recommendation is to review conditions for removing project from suspension in 18/19, PICCL Change 7, project risk 10, project risk 11

17/11/17 - Project suspension approved by WIS 17/11/17 - PICCL Change 7