Project Service Handover Checklist

 

Project Service Handover Checklist

 

This document should be reviewed at the planning stage of a project.

  • Any elements not required should be so indicated (not deleted)
  • Any additional elements or additional detail should be added (this could be at ay sage of the project)
  • Communication should begin as early as possible  

 

The document needs to be completed as part of the handover to support before project can close.

 

 

 

Required for Handover to Service

Acceptance / Not Required

Notes

Service Owner identified and agreed to accept role

 

 

Service Manager identified and agreed to accept role

 

 

Business Service Owner identified and agreed to accept role

 

 

Service Desk identified and agreed to accept role

 

 

Service entered into Service Catalogue

 

 

Service object  (or subcategory if Business Service) created in UniDesk

 

 

 

UniDesk Operator Groups First and Second  line identified and agreed to accept role

 

 

EdHelp and Helpline informed of new/changed service

 

 

 

 

 

SLA Agreed with Stakeholders

 

 

OLA Agreed with Stakeholders

 

 

 

 

 

User Acceptance Testing signed off

 

 

Deployment Checklist signed off

 

 

Delivery signed off

 

 

Risk register signed off

 

 

EQIA signed off

 

 

GDPR signed off

 

 

Other regulatory, standards and certification signed off

 

 

Service continuity plan signed off

 

 

Service monitoring and accounting in place.

 

 

Users and Staff trained

 

 

Knowledge transfer from project to support

 

 

Operational documentation signed-off

 

 

Operational processes implemented including monitoring, DR recovery, etc.

 

 

 

 

 

Third party contracts and renewal procedure in place

 

 

Underpinning contracts comply with service level agreement

 

 

Underpinning contracts comply with University policy

 

 

Dependencies on other services recorded

 

 

All critical components are covered by third party or internal support agreements

 

 

Administration roles defined and agreed

 

 

Issue escalation paths defined and recorded

 

 

Advertisement and launch communications defined and circulated

 

 

 

 

Project Info

Project
ITI Project Template
Code
ITI001
Project Manager
Maurice Franceschi
Project Sponsor
Anthony Weir
Current Stage
Close
Status
Closed
Start Date
24-Mar-2016
Planning Date
n/a
Delivery Date
n/a
Close Date
31-Dec-2016
Programme Priority
24
Overall Priority
Normal
Category
Discretionary