Completion Report

Project Summary:

 

These were the Business Deliverables for the project

 

No

Description

New or Changed (Y/N)

O1

Define a common change management processes across the three universities(MUST)

Delivered

D1

Deploy the change management process across the three universities(MUST)

Delivered

O2

Define a common release management process across the three universities(MUST)

Delivered

D2

Deploy the release management process across the three universities(MUST)

Delivered - see below 1

D3

Deliver appropriate service support documentation, awareness and training for all partners and customers of the service (MUST)

 

Partially Delivered - see below 2

D4

Provide documentation on how new process with integrate with / change existing project delivery, request for change, release management in UniDesk (MUST)

Partially Delivered - see 3

D5

Change & Release roles and responsibilities agreed and clarified to support the process (MUST)

Delivered

D6

Provide a framework for the categorisation of changes and release types published (MUST)

 

Delivered

D7

fields that need to be held for each standard change, e.g. Service, approver, description, expected outcome, others? (MUST)

 

Delivered

D8

Providing a framework for CAB's or change approval (MUST)

Delivered - see 4

D9

Configure Unidesk to support the change and release process (MUST)

Delivered

D10

Gap analysis on the data in C&R against data used by Alerts system (SHOULD)

Not Delivered - see 5

 

1 - St Andrews and Edinburgh will launch C&R on Unidesk v 5, after the upgrade is comlpeted in May/June.

2 - St Andrews and Abertay will provide their own training. Sheffiled Hallam are not interested in C&R for now. Edinburgh have an offer open to end of July that partners and Sheffield Hallam can request a one-day workshop.

3 - The project engagement will be revisited once C&R process is available through version 5. An initial approach has been agreed, where a RFC specific template will be set up for projects, but this has to be designed and agreed. A separate process is felt to be too much for now.

4 - A framework has been provided, and two services are to be selected for initial trials of the new process.

5 - Some analysis was done that can be picked up, but priority of this was low and budget not extended to allow further analysis as it is Edinburgh-specific.

 

Issues - All jiras closed

Risks - all risks closed

Action - all actions completed

 

 

 

 

 

Analysis of Resource Usage:

Staff Usage Estimate: 105 days

Staff Usage Actual: 101 days

Staff Usage Variance: -4%

Other Resource Estimate: 6894 days

Other Resource Actual: 8982 days

Other Resource Variance: 30%

Explanation for variance:

Variance in 'other resources' - an extra day's consultancy was required

Estimate vs Actuals by Resource - As this is a funded project, then all effort is for Apps and Service Management

Project Services         estimate    19         actual  22 (Planning and Management)

Apps  Management                       26                      28 (Analysis, Design)

Service Management                    39                     42 (Analysis, Design, Configurations, UAT))

Director/Senior Management        3                        3 (Governance)

Other Applications                         17                        6 (Deployments, Unplanned)  

Total                                                 105                   101  

 

 

 

Key Learning Points:

 

Using senior staff members as key team member from production has the advantage of bringing experience and common sense to the analysis and implementation

Using senior staff members from production has the disadvantage of conflicting with higher priority projects and RDS and KSR activity, thus extending the elapsed time for the project

 

Feedback from project team, board and other stakeholders (survey results).

The following scored mostly 4/5 from responses (no less than 3) Business Requirements Met Objectives Met Within Budget Within Scope Quality of C&R Process Risks Managed Issues Raised Estimation Stakeholder Participation Communication Effective Meeting Project Management Project Goverance The following scored mostly 3 or Less Timescales kept Milestones Met Resourcing Effective  

 

 

 

 

 

Outstanding issues:

All jiras are closed, all issues resolved.

These are now within scope of the uniDesk v 5 Upgrade project

St Andrews's launch of C&R Edinburgh launch of C&R to full community Updated C&R documentation for v 5 Projects' engagement with C&R

USD will provide workshops to a selected group on Unidesk v 4, and are available to provide a one-day workshop to partners or Sheffield Hallam if they do choose to have one before end of July.

 

Project Info

Project
UniDesk Change & Release
Code
ITS081
Programme
ISG - IT Service Management (SMI)
Project Manager
Maurice Franceschi
Project Sponsor
Bryan MacGregor
Current Stage
Close
Status
Closed
Start Date
10-Aug-2011
Planning Date
n/a
Delivery Date
n/a
Close Date
10-Apr-2013
Programme Priority
1
Overall Priority
Higher
Category
Discretionary