Completion Report
Project Summary:
IS Applications Division has built up reliance on a number of key products over the years to assist in project and service delivery. Annual upgrades will be undertaken in order to ensure that these products remain supported.
This project was focussed on the upgrade of the Bamboo product.
The underlying application stub, CITESTER, which is used to test the Bamboo environment is working for Coldfusion applications was also upgraded from CF9 to CF11. (The infrastructure supporting the CF9 version of Coldfusion is at end-of-life in July 2016 & will no longer be supported by the supplier so there is a need to migrate this applications to a more recent and supported version of Coldfusion.)
Objectives and Scope
Bamboo was upgraded on existing Test and Live environments.
The dev, beta, test and live CITESTER CF9 applications were upgraded to CF11.
Not in Scope
Load testing and Disaster Recovery testing was not in scope.
It was agreed to keep the current configuration (non resilient). A future project may change the server configuration so that it is resilient.
No new Infrastructure will be introduced as part of this project.
Deliverables
TAD and Operations Document updated [Must Have]
Upgrade of Bamboo [Must Have]
Upgrade of CITESTER dev,beta, test and live environments from CF9 to CF11 [Must Have]
Benefits
We have taken on the above products as part of our core workflow for project (and support) delivery in recent times. As such they are essential to our ability to successfully deliver change within the University. Failure to keep the products up to date and in a supportable position exposes us to the risk of serious issues with the software that may affect their ability to run and operate in our environment. It also avoid costly “big bang” upgrades we have experienced in the past when we have had to put significant resources towards upgrading products.
The upgrade of the CITESTER stub from CF9 to CF11 will allow future Bamboo upgrades to continue to make use of this application stub to verify Bamboo environments.
Success Criteria
The 'must have' deliverables need to be met in order for the project to be a success. The deliverables will be measured as follows:
- Deliverable 1: Upgrade of Bamboo
- This will be tested and verified by Software Dev team members who currently use Bamboo for deployments.
- Deliverable 2: CITESTER dev,beta, test and live environments upgraded to CF11
- This will be tested and verified by Software Dev team members who currently use Bamboo for deployments.
Closure Review Notes
It was agreed that all the objectives for the project were met, and that all deliverables were completed.
- Bamboo upgraded on Test and Live Infrastructure
- The TAD and Operations Document are up to date.
- CITESTER dev,beta, test and live environments upgraded to CF11
- The project completed under budget. Due to migration tasks being carried out quicker than anticipated by Dev Tech resource with experience of process (Riky)
- A delay was encountered delivering final milestone of CITESTER application due to resources being booked on other higher priority projects.
Analysis of Resource Usage:
Staff Usage Estimate: 29 days
Staff Usage Actual: 14.5 days
Staff Usage Variance: -50%
Other Resource Estimate: 0 days
Other Resource Actual: 0 days
Other Resource Variance: 0%
Explanation for variance:
The breakdown of the effort across each stage of the project is shown below:
The project progressed well and completed under budget despite a couple of issues being encountered Issue 1 due to a dependecy with a plugin which was unsupported and Issue 2 Milestone changes due to Dev Team resource availability.
| Stage | Estimate | Actual | Difference |
|---|---|---|---|
| PM | 5 | 3 | -2 |
| Planning/Systems Design | 3.5 | 1.5 | -2 |
| Build/Testing and Acceptance Bamboo | 3.5 | 4.5 | +1 |
| Deployment Bamboo | 3 | 1.5 | -1.5 |
| CITESTER Upgrade | 6 | 3 | -3 |
| Closure | 1 | 1 | 0 |
| Contingency | 7 | 0 | -7 |
Total | 29 | 14.5 | -14.5 |
The breakdown of effort by team is:
| Team | Effort (days) |
|---|---|
| Development Technology | 9 (including 4 days for Gillian Henderson in PM role) |
| Production Management | 0.5 |
| Project Services | 0 |
| Software Development | 5 |
Key Learning Points:
The project completed under budget. Due to migration tasks being carried out quicker than anticipated by Dev Tech resource with experience of process (Riky).
We should be careful introducing Bamboo plugins which may not be compatible with subsequent versions of Bamboo. This project removed a dependency which had prevously been introduced. See Issue 1
Future Project should consider introducing resilience for Bamboo due to increased reliance on this software for deployments.
Outstanding issues:
None