Closure Report
Project Summary
As the project completes, with a hard deadline of 4th August for budget and funded innovation projects, we have achieved the main objective of a unified GiT for ITI and Apps.
Objectives and Deliverables
Technical:
1. Implement and test shared Git environment to enterprise standard including structured logical repository design
2. Implement ecosystem which enables automation using Git including with Puppet Enterprise
Functional:
1. Process and operational documentation enabling positive and collaborative adoption of the new technologies
2. Work with ENT019 to produce draft road-maps of ITI & Applications deliverables using Puppet/Git during 2017
Organisational:
1. Identify and propose changes to ISG working methods which could be expected to improve KPI's
| Objective 1 Unified GIT Service by May 2017 | Description of the Deliverables needed to achieve the objective | MoSCoW | Key Milestones | ||||
| Deliverable D1.1 | Unified Git service designed to support the automation processes of ISG Apps and ITI | M | Achieved (July) | ||||
|
Deliverable D1.2 |
Git service that ENT019 can use for Puppet development and continuous integration/deployment | M | Achieved | ||||
| Deliverable D1.3 |
|
S |
Partially Achieved. EDINA will have their own GiT service offering some functionality which was out of scope for this project but EDINA will also use the new service. Aim is still to move to one service. |
||||
| Objective 2 The structural design of the git repository by July 2017 | |||||||
| Deliverable D2.1 | Sections for existing and new applications, infrastructure & other components. | M | Achieved | ||||
| Objective 3 Devolved authorisation and process documents by July 2017 | |||||||
|
Deliverable D3.1 |
Recommend how the above should used in consonance with DevOps practice. |
M | Achieved | ||||
| Objective 4 Acceptance of the migration of existing service configuration and software component data into this repository | |||||||
| Deliverable D4.1 | Execute and sign-off one or more migrations from each existing source into Git | M | Not Achieved - Planned for 24 August *during* the Special CAB period as this will reduce risk and impact on services to almost zero. | ||||
This table was used through Business and Technical Analysis, Design, Build, and Testing/UAT as a Traceability Matrix to ensure the project brief project objectives and deliverables are followed through.
Benefits
Benefits management and realisation will be available on the ITI Sharepoint space.
The project will help to address several of the key observations and recommendations made by Forrest Consulting and the University of Edinburgh project team during the delivery of project API003.
This project aimed to help ISG to transform and improve IS through
1. Strategic alignment of tools, objectives, standards and approach, 2. Improved collaboration including shared ownership, responsibilities, processes and policies, 3. Organisation and automation of the software delivery life-cycle within Application and Infrastructure teams and 4. Consolidation of siloed, localised technology and practice onto high-quality, centralised systems. These improvements were attaied will result in the improved efficiency, consistency and quality of ISG's products and services and will also be representative of industry best practise.
Success Criteria
A unified Git service which ITI and Apps use for allnew deployments and to which they endeavour to migrate existing deployments. Success criteria met.
Analysis of Resource Usage:
Staff Usage Estimate: 60 days
Staff Usage Actual: 37 days
Staff Usage Variance: 39%
Other Resource Estimate: £0
Other Resource Actual: £0
Other Resource Variance: 0%
Reason For Variance
The Planned migration is happening in August, which means a day or two less to the project. Some of the technical Shoulds were not developed or delivered - none of these prevent the service from being used by ITI/Apps but we have some developments that would be good to develop in future. https://www.wiki.ed.ac.uk/display/AWMA/Consolidated+Gitlab+Requirements. These were typically elements that are not out-of-the-box and will need effort to develop for our use.
The original budget also anticipated possible use of consultants, which would have mean less days for the project team. As it was, this was not required.
Key Learning Points
None
Outstanding Issues
No outstanding issues