Report for January 2020

Report Date
January 2020

The API programme has come to an important point where we have delivered a lot of the major infrastructure and basic service elements.

We now need to review where we are and plan where we are going both in terms of vision and in terms of further projects in the near future to fully develop the service and move to an API First culture.

There is a planning workshop on 13th February to move this forward.

DTI018 (Continuous Service Improvement APIs) - Pure API and EDW Person API delivered to WS02.  UniDesk API undergoing internal testing.

DTI026 (API Gateway and API Management Tool) - Cloud WSO2 configured.  Handover to Production to be agreed prior to closure.

DTI028 (Infrastructure) - Review workshops completed.  Project set for closure.

DTI029 (Maturing the service) - Project approved for closure but scope to be reviewed following planning workshop on 13th Feb.

Programme status is Amber as there have been delivery challenges.

Section Two: Projects Not Started

There are no projects not started.

Section Three: Projects in Progress

Project Info                                                                                   Project Manager's Commentary

DTI018

 

Milestones

Delivery (end of design / build / accept / deploy iterations) 19-Jul-2019
Deployment review 24-Jul-2019
Close 31-Jul-2019

 

RAG: AMBER

 

 

Report for January 2020

Achievements in Last Period

  • PURE API 

    • Testing raised issue with incomplete responses.  Resolved and re-released for test.  

  • Unidesk API

    • WSO2 configured to manage UniDesk API.

    • Testing raised issue with responses.  Resolved and re-released for test.

    • Liaise with Service Team regarding progression through internal Test and prep prior to external testing.

    • Reschedule project timescales to allow for internal and external testing and sign off.  

  • Person ID resolver API for EDW

    • Testing raised issue with incomplete responses.  This has been raised with Dev Services for resolution

Issues

  • With UniDesk upgrade on the horizon should we continue to develop the present API.  It was confirmed that the API being developed at present would remain in use during the staggered upgrade and was therefore worth continuing with.

Next Steps

  • PURE API 

    • Completion of testing within WSO2 and signed off.  

  • Unidesk API

    • Liaise with Service Team regarding progression through internal Test and prep prior to external testing.

    • Initiation of external testing.  Probably using St Andrews as test institution. 

    • Promotion of API from Test to Live.

    • Internal testing of API via WSO2.  .  

  • Person ID resolver API for EDW

    • Correction of error and re-release for test.

    • Completion of testing within WSO2 and signed off.  

  • Handover process for API's to be agreed.  Appropriate documentation agreed and commenced if not already in existense.

 

DTI026 API Gateway and API Management Tool

 

Milestones

Milestone Due Date
Acceptance Review 19-Aug-2019
Delivery 20-Aug-2019
Closure 11-Sep-2019

 

RAG: AMBER

Report for January 2020

Achievements in Last Period

  • Documentation with regards delivery of training reviewed.

  • UniDesk API now managed by WSO2

  • Close report drafted

Issues

Next Steps

  • Review handover of WSO2 and associated training to Production and address outstanding actions.

  • Close project

 

DTI028 Maturing the API Infrastructure

Milestones

Milestone Due Date
WP 4.1 - Python templates  Done
WP 7.1 and 7.2 Centralised Logging (writing/reporting to logs) 19/07/2019
WP 8 API Standards  Done
WP 6.2 Security Scanning – Dependency Check  Done
WP 6.1 – Security Scanning – ZAP  Done
Approval of API standards and security scanning 11/10/2019
D6 Secure Software Development  Done
Closure 25/10/2019

 

RAG: AMBER

 

Report for January 2020

Achievements in Last Period

  • Final deliverables for WP 6.1 & 6.2 - Security document workshops carried out.
  • Summary statement on WP 7.1 and 7.2 Centralised Logging to be signed off following review and present position agreed.

Issues

  • Final deliverables for WP 6.1 & 6.2 require review workshops followed by proposals raised at OGG.  Initial deliverables suggested that project would include implementation of both elements but costs and timescales make this not achievable within the confines of this project.

Next Steps

  • Project closure.

 

DTI029 Maturing the API Service

Revised Milestones To Be Confirmed Post Workshop.

RAG: AMBER

 

Report for January 2020

Achievements in Last Period

  • Closure report completed and forwarded for review.
  • Closure report sign off received from the majority of reviewers prior to decision to hold API Service Planning Workshop in mid Feb.

Issues

  • Existing milestones need updated in response to project review.  Present plan is to review deliverables and their relevance in light of the evolution of the project.  Project will be undertake a controlled closure with outstanding tasks being picked up by the next tranche of the programme.

Next Steps

  • Attend API Service Planning Workshop and rescope project depending upon the outcomes.
  • Raise revised milestone PICCL OR close project.
Programme Status
Has formal escalation taken place?
No