Completion Report
Project Summary:
.
The project has achived its Objectives and Deliverables, with all MVM sites moved to managed hosting by Service Management or onto satndard IS support infrastructure (four new servers built).
Project Scope change are logged on this page as well as the PICCL.
Objectives
1) Setting up a governance mechanism to enable MVM and IS to review current and future service support and development - Achieved. 2) adapt the current support model provided by LTS IT Services, to fit service the support model provided by IS to ensure the eLearning team have access to the types of 1st/2nd/3rd line support they need - Achieved. 3) transition the existing responsibilities for management (platform upgrades, configuration, capacity, change and availability management) to appropriate teams in IS - Achieved. 4) transition the responsibility for software platform technology upgrades and security patching to IS - Achieved. 5) transition the responsibility for hardware lifecycle (through Virtualisation and scaleable storage hardware technology) to IS - Achieved. 6) ensure dedicated authentication and security setup is not compromised as part of transition - Achieved. 7) ensure services have adequate environments in place for successful delivery of service. - Achieved.
Deliverables
1) agree and publish the governance mechanism - the project will develop a governance mechanism as the project progresses. - Achieved. Part way through this project the requirements of the complete governance mechanism shall become clear and will be finalised. 2) categorise current services into three service types: - Achieved. - simple hosting - dedicated hosting - complex application 3) establish service delivery model for each service type - as the project progresses, the service delivery model shall develop.- Achieved through migration to Plesk, C-Panel and to dedicated MVM servers. The service delivery model shall not be wholly defined at the outset, it will grow as its requirements become clear over the course of the project. 4) establish what infrastructure can be retained, and to what extent the LTS Servers and server rooms shall continue to be used in the short/medium and long terms - Achieved. 5) establish end of life position of existing infrastructure to help inform decision-making about priorities - Achieved. 6) review authentication and security setup and define security model for service - Achieved. 7) review environment requirements by service type - Achieved. 8) establish service delivery and migration plan for each service type, including priority, dates and resources/costs - Achieved. 9) estimate the general build-infrastructure requirements and complete the build-structure requirements - Achieved.
10) migrate services and infrastructure - Achieved.
11) review existing service availability monitoring and and determine who shall take responsibilities for these in the migrated services - Achieved.
12) review existing change-control and operational procedures to determine suitability of these in the migrated context - Achieved.
Analysis of Resource Usage:
Staff Usage Estimate: 150 days
Staff Usage Actual: 140 days
Staff Usage Variance: -7%
Other Resource Estimate: 0 days
Other Resource Actual: 44729 days
Other Resource Variance: 0%
Explanation for variance:
The additional capital costs of £44,729 are due to unplanned expenditure on
building additional MVM servers building additional TEST servers Adobe Connect license
The project is completing a year after the original planned date of March 2015. The main factors here were
having to spec and build the four new MVM servers restructuring of MVM IS USD and the impact on staff as they were re-assigned roles and responsibilities the discovery of additional sites not on the MVM servers - most notably Adobe connect but also other unexpected sites, and some dependencies between servers
Key Learning Points:
Although we comnunicated with webiste owners to give advance warning that their site was being migrated or being decomissioned, we had one instance of the website owner not repsonding to the team - resulting the website being removed whilst stil being used. The site was restored from backups onto the new servers. In future, we woudl have to be more pro-active, or perhaps aggressive, in contacting all owners to ensure they were aware / taking action.
Where we have infrastructure and software built over years, time to replace and decommission will always take a long time as there are normally many iterations where additional services and infrastructureare "found" during the project. Typically, these take longer to resolve - website ownership may be unknown, site usage also not known, there may be unexpected dependanecies and technologies, or outdated code that needs upgraded, etc. We should allow enough time for several iterations of 'discovery and review'.
We have excellent people ready to apply common sense and innovation to solutions, cutting across silos and collaborating well.
Outstanding issues:
None