Report for May 2020

Report Date
May 2020

We are working towards the conclusion of this phase of the API programme, aiming to launch the initial API service.

There are some development and testing tasks that are nearing completion that have had issues to resolve in order to complete.

Service management and development are collaborating on completion of the initial service delivery model for APIs. This has taken longer than anticipated because of resource pressures within Service Management and Development but is making steady progress.

If resource pressures in Service Management and Development could be eased then this work could complete more quickly.

We are in early stages of a re-planning exercise to clarify the longer term vision for API's at the University.

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 of EDW Person Resolver ID API 20-Mar-2020
Delivery of PURE Id Resolver API 20-Mar-2020
Delivery of UniDesk API 03-Apr-2020
Deployment review 17-Apr-2020
Close 24-Apr-2020

 

RAG: AMBER

 

 

Report for May 2020

Achievements in Last Period

  • PURE Resolver Id API 

    • Functionality completed.  Access and authentication process being worked on.

  • Unidesk API
    • 2 of the 3 testers have been able to successfully retrieve data using the API.

    • Documentation being reviewed to ensure suitability with regards the target audience.  In particular relating to the level of technical knowledge required by the user and the quality regarding external consumption. 

    • Liaise with Service Team regarding progression of API and documentation. 

  • Person ID resolver API for EDW

    • Testing raised issue with incomplete responses.  Investigation ongoing.

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.
  • Work within DTI029 to merge internal instances of WSO2 may impact progress as a result of staff availability and generating work to migrate APIs across to the single retained instance. 

Next Steps

  • PURE Resolver Id API 

    • Complete deployment checklist.

    • Creation and sign off of authentication SharePoint site for locker process .

    • Authentication process added to Production Wiki page.  

  • Unidesk API

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

    • Sign off of internal testing of API via WSO2. 

    • Initiation of external testing.  St Andrews lined up as test external institution. 

  • Person ID resolver API for EDW

    • Call arranged with development team to agree way forward.

    • Completion of testing within WSO2 and signed off.

  • Handover process for API's to be agreed.  Liaise with Service and Production Management regarding support and handover process.

 

DTI029 Maturing the API Service

Milestone Due Date
Delivery - D10 (Forward visibility of the API pipeline) 04-June-2020
Deployment Review 26-June-2020
Closure 17-July-2020

 

RAG: AMBER

 

Report for May 2020

Achievements in Last Period

  • Weekly review meetings continuing to revive project momentum.
  • Revised service initially raised with Project Services PMO.
  • Service "Walk Through" held with Production Management, Enterprise Architecture and PMO. 
  • Proposed service agreed along with a soft launch targeted by the end of July 
  • Service Management and Development Services to complete development of initial service delivery model.
  • Scope increase to include work to merge the IS and People and Money instances of WSO2 formally approved at WIS of 29/5/2020.

Issues

  • Present plan is for Service Management and Development Services to develop the initial service delivery model. Service management and development have little spare capacity to devote to this exercise and it is therefore taking longer than expected to complete. Once this is completed the scope of remaining tasks and responsibility for them will become clear.

Next Steps

  • Service Management and Development Services to continue development of service delivery model based on review feedback.
  • Clarify tasks and those responsible to complete tasks to deliver initial service model and re-plan project accordingly.
  • API publishing process to be agreed and then raised with People and Money.
  • Kickoff call and follow up workshop scheduled to address WSO2 merge process.
  • Commence review of Communications tasks to publicise the API service in time for soft launch.

 

CLOSED PROJECTS

 

DTI026 API Gateway and API Management Tool

Category: Discretionary

RAG Status

BLUE (Closed)

Report by Ken Miller 

DTI028 - Maturing the API Infrastructure

 

Category: Discretionary

RAG Status

BLUE (Closed)

Report by Ken Miller 

 

 
 
 
Programme Status
RAG Status
Overall
AMBER
Has formal escalation taken place?
Yes
Escalated to
Stefan Kaempf, Dave Berry
RAG Commentary
Amber due to resource issues within Service Management and Development mean that forming the operating model for APIs is taking much longer than expected.