Completion Report
Project Summary:
This project looked to install to the latest stable and supported version of Coldfusion, version 11 and migrate one application to verify the new Coldfusion Implementation. The project was not be responsible for migrating any other applications.
The Objectives, Deliverables and Success Criteria stated at the outset of the project were:
Objectives & Scope
We will look to install to the latest stable and supported version of Coldfusion (currently version 11). This project will implement the relevant infrastructure and latest Coldfusion environment. One application will be migrated to verify the new Coldfusion Implementation. The project will not be responsible for migrating other applications.
The following tasks will be carried out as part of this project:
- Review Infrastructure requirements, determine infrastructure for new Coldfusion version and setup new Intrastructure if required.
-Request and Implement Coldfusion licence in dev, test and live.
-The application to be migrated will be confirmed during design phase.
- Review Coldfusion documentation for new version and determine if there are any essential changes to the implementation/configuration of Coldfusion 11 which differ from the current Coldfusion 10 environment. (We are looking to implement Coldfusion 11 largely the same as Coldfusion 10 environment other than essential changes that are identified)
-Combined TAD & Operations Doc and Build Document will be produced
- Install and Configure ColdFusion 11 in Dev, Test and Live environments (All environments will be load balanced)
- One application will be migrated to validate new infrastructure.
- DR Test
- Prepare summary document stating support positions of current and future releases of Coldfusion. Required for Road Map.
Not in scope
- Application migrations, other than the application identified to validate Infrastructure, will be handled by subsequent projects.
- A load Test will not be carried out. Load testing, if deemed necessary, will be carried by subsequent projects utilising the new Infrastructure .
Deliverables
- New version of Coldfusion 11 on Dev, Test and Live [Must Have]
- Combined TAD & Operations Document. [Must Have]
- One Application migrated to validate Coldfusion Infrastructure [Must Have]
- Cold fusion licence in place for dev,test and live [Must Have]
- Coldfusion Road Map [Should Have]
Benefits
We are in a fully supported position moving forward for our main Coldfusion delivery platform
Consequently will be able to ensure security issues are in a position to be addressed with the vendor.
Success Criteria
- New version of Coldfusion 11 on Dev, Test and Live [Must Have]
- Combined TAD & Operations Document.[Must Have]
- Cold fusion licence implemented in dev, test and live [Must Have]
Closure Review Notes
It was agreed that all the objectives for the project were met, and that all deliverables were completed.
- New version of Coldfusion 11 installed on Dev, Test and Live
- The TAD and Operations Document are up to date including details of CF 11 config settings.
- One application, ISkills has been sucessfully migrated to the new CF11 Infrastructure
- Coldfusion Enterprise licences purchased and applied to dev, test and live
- Coldfusion dates added to End Of Life Road Map
- The project schedule remained largely on target according to original timelines. A two week delay was encountered due to conflict with priority 1 timetabling project (TTU010) but this short delay was agreed with the Project Sponsor.
Analysis of Resource Usage:
Staff Usage Estimate: 65 days
Staff Usage Actual: 64.9 days
Staff Usage Variance: 0%
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, a couple of minor unexpected issues which were encountered and resolved Issue 2 cosign and Issue 5 Config settings consistency. These issues increased the effort required in the build and deployment stages and required some additional contingency time. There were also some replanning and milestone changes due to conflict with TTU010 which added to PM time (Issue 1, Issue 3 & Issue 4).
The cost of the 3 Enterprise Licences and the 6 servers for the Coldfusion 11 Infrastructure were core funded and are not listed in the costs section.
| Stage | Estimate | Actual | Difference |
|---|---|---|---|
| PM | 10 | 10 | 0 |
| Planning | 4 | 3.3 | -0.7 |
| Design | 7.5 | 7.1 | -0.4 |
| Build | 13 | 17.7 | +4.7 |
| Testing and Acceptance | 10 | 11.1 | +1.1 |
| Deployment | 6.5 | 10.1 | +3.5 |
| Closure | 1 | 1 | 0 |
| Contingency | 13 | 4.6 | -8.5 |
Total | 65 | 64.9 | -0.1 |
The breakdown of effort by team is:
| Team | Effort (days) |
|---|---|
| Development Technology | 52.5 (including 10 days for Gillian Henderson in PM role) |
| Production Management | 3.5 |
| Project Services | 0.5 |
| Software Development | 8.4 |
Key Learning Points:
- Purchasing ColdFusions licences, navigating through the request process and working out what we required with SoftCat was very time consuming. In future technical questions should be directed to Adobe then SoftCat should be contacted to purchase what Adobe already agreed we require. SoftCat did not have the level of technical expertise to answer some of the questions and there where then having to follow these up with Adobe themselves making the process take an excessive amount of time. We required 3 Enterprise Licences (2 for production, with 1-1 mapping giving us 2 test licences and 1 for dev with 1-1 mapping giving us 2nd dev server) We did not require Gold Support as we already have this for our CF environment. We did not require a Maintenance licence as this is required if we carry out inplace upgrade i.e from CF10 to CF11 (this is not how we inmplement CF environments, we run versions in parallel while migrations are carried out)
- ColdFusion Settings are open to human error as there are lots of changes being made on multiple servers (See Issue 5 for details). If we carry out future upgrades we should include a peer test step for settings to be reviewed by another member of the team or we should change the process to extract the settings from one server and implement these across all servers during the setup of each environment.
- Feedback from Closure Survey "these types of projects arre ideal for being run by a technical team. This has proved to be very effective." "well run project, good communication, , milestones planned and met, or changed with appropriate change control"
Outstanding issues:
None - All objectives met.