Closure Report

Project Summary

This project (DTI013) supported delivery of APIs by delivering requirements / user stories to inform designs of individual APIs. 

No. Deliverable Priority Delivered?
D1 Analysis of requirements for each business area / API Must Yes - analysis of requirements for projects DTI015 (Student Record APIs) and DTI017 (VLE API) informed the project briefs for these projects (the end of planning / project briefs for these projects were approved by WIS on 19/5/17 and 21/7/17 respectively).  Analysis of requirements for DTI018 (Continuous Service Improvement APIs) also took place within this project.
D2 Specification of requirements / user stories for each business area / API Must Yes -  requirements for projects DTI015 (Student Record APIs) and DTI017 (VLE API) informed the designs of these APIs (see key learning point 2 below).  In the case of DTI017 the requirements were delivered for the initial proof of concept only.  Specification of requirements for DTI018 (Continuous Service Improvement APIs) also took place within this project.
D3 Analysis and documentation of how each API interacts with the University's wider IT systems Should Yes - the first draft of the API data landscape was included in the Enterprise APIs Service Roadmap document.  Work will continue to update the API data landscape as part of further development of the Service Roadmap (this will be managed and funded as a BAU task by Service Management).
D4 Analysis of API designs against enterprise architecture principles Should Yes - this was undertaken by the Enterprise Architecture Team as part of the design work within DTI015 (Student Record APIs) and DTI017 (VLE API).
D5 Specification of change requests Must Yes - a process for managing change requests was developed and agreed.  No change requests, however, were raised during the execution of this project, but it was agreed by the Project Team that the deliverable was delivered as any change requests would have been specified and managed using the agreed process.
D6 Technical Analysis - Proof of Concept for StuTalk Must Yes - delivered 12/4/17 - see here

The project additionally delivered:

  1. an agreed process for managing change requests
  2. the first draft of the Service Roadmap (this was a change of scope logged as Change 8).

Key Project Dates

  1. End of Planning 23/3/17
  2. Requirements Sign-Off - Student Record APIs 19/5/17
  3. Requirements Sign-Off - VLE API 21/7/17
  4. Accept initial service documentation (Change 8 - change to project scope) 16/11/17
  5. Project Closure 24/11/17

Key Project Issues and Changes

Refsort descending Date Identified Type Short Description
1 10-Mar-2017 Issue Departure of business analyst assigned to project
2 30-Mar-2017 Change Change to project budget
3 31-Mar-2017 Decision Project Priority
4 12-Jun-2017 Change Change to project milestones
5 10-Aug-2017 Issue Departure of business analyst assigned to project
6 14-Aug-2017 Change Change to project budget
7 01-Sep-2017 Change Change to project milestones
8 10-Oct-2017 Change Change to project scope and project budget
9 24-Nov-2017 Change Change to project budget and milestones
10 11-Jan-2018 Change Change to project milestones

Analysis of Resource Usage:

Staff Usage Estimate:  120 days

Staff Usage Actual:  120 days

Staff Usage Variance:   0

Other Resource Estimate: £0

Other Resource Actual: £0

Other Resource Variance: N/A

Explanation for Variance

  1. The project budget was increased from 40d to 45d to accommodate a change of scope - see Change 2. The project budget was further increased from 45d to 95d to accommodate a change of scope - see Change 8.  The project budget was further increased from 95d to 120d to accommodate required additional effort - see Change 9

Key Learning Points

  1. This project delivered requirements to inform designs of APIs within other API projects.  The anticipated benefits of using a dedicated project to deliver requirements included: continuity of business analyst resource(s); consistency in dealing with different requirements; reuse where possible - no need to 'reinvent the wheel' each time; improved efficiency.  In practice these benefits weren't realised, due to changes in business analyst resources as a result of staff changes (see Change 1 and Change 5), and the requirement to use business analyst resources with knowledge of student systems within SSP as well as from IS Apps.  For future projects it is recommended therefore that requirements and analysis tasks are embedded instead within specific API projects.  This means that the planned use of the follow-on project DTI023 should be reviewed.
  2. Although successfully achieved, difficulty was experienced specifying detailed requirements and user stories for DTI015 and DTI017 due to a lack of clarity in what functionality was required by the APIs.  The requirements were high level in each case (and in the case of DTI017 the requirements were delivered for the initial proof of concept only).  Adoption of an agile method for developing user stories and iteratively deploying releases of APIs was helpful here. 
  3. There are several cross-cutting projects (eg within Service Excellence) which meant that some requirements for APIs (eg for DTI018) could not be approved and progressed.

Outstanding Issues

  1. Possible requirements for DTI024 (Maturing Student Record APIs) were documented in the DTI013 JIRA project.  These requirements will be reviewed, prioritised and closed where possible as part of deliverable D4 within DTI024 and are listed in the attachment below.  There are no other open JIRAs.

dti013_jira_summary.pdf

Project Info

Project
Enterprise API Business Areas - Analysis and Specifications of Requirements
Code
DTI013
Programme
Digital Transformation - Enterprise APIs (DTIP03)
Management Office
ISG PMO
Project Manager
Chris Copner
Project Sponsor
Alex Carter
Current Stage
Close
Status
Closed
Start Date
10-Mar-2017
Planning Date
n/a
Delivery Date
n/a
Close Date
24-Nov-2017
Programme Priority
1
Overall Priority
Highest
Category
Discretionary

Documentation

Close