Project Handover Process
VERSION NUMBER [1.2]
Submission Date 29/05/2022
Copyright
The copyright in this work is vested in LINK Development, and the document is issued in confidence for the purpose only for
which it is supplied. It must not be reproduced in whole or in part or used for tendering or manufacturing purposes except
under an agreement or withEgypt HQ:inA:
the consent 94 Street
writing of LINK 105, 11431and
Development Maadi
then Cairo,
only on Egypt.
the condition that this notice is
included in any such reproduction. No information as to the contents or subject matter of this document, or any part thereof,
arisingT: +(202)
directly 2529 5800
or indirectly thereF: +(202)
from will be2529 5888orE:ininfo@linkdev.com
given orally www.linkdevelopment.com
writing or communicated in any manner whatsoever to any third
party, whether an individual, firm or company, or any employee thereof, without the prior consent in writing of LINK
Development.
Issuance Date Version Number Produced By Notes
4/5/2020 0.1 Antwan Adel Document Created
4/27/2020 0.2 Hossam ElKady 1st Round Review
4/28/2020 0.3 Antwan Adel Apply Comments
4/29/2020 0.5 Hossam ElKady 2nd Round Review
4/30/2020 1.0 Antwan Adel Apply comments and Apply
Template
4/11/2022 1.1 Mohammad Aly Support Project and Audit
Check list meeting
Antwan Adel
comments
5/24/2022 1.2 Mohammad Aly Apply comments based on
Meeting on 2022-05-22
Antwan Adel
1 PURPOSE OF THE DOUCMENT
This document is to standardize the process for handover a project from delivery to the
support team by identifying criteria, steps, deliverables required to achieve a smooth
handover.
2 ENTRY CRITIERIEA
this section describes when shall the project is eligible to be handed over to the support
team and the conditions that should be applied.
Project to be handed over to the support team based on the following criteria and condition
- Project must have a valid support contract or warranty contract for more than six
months.
- Project has been deployed to production server and signed off by the customer.
- All CRs, milestones and deliverables are signed off.
- No critical and major Issues still open by QC team or reported by the customer.
3 HANDOVER PROCESS
3.1 PREREQUISITES
- Support Manager will have a meeting with delivery heads on monthly basis for
forecasted projects that will meet the entry criteria mentioned and expected to be
handed over to the support team within 6 months.
- Handover process will start with support team within 2 months from notification.
- Delivery Team to share all technical or Technology material to Support team
- Head of Delivery or Delivery PM, to recommend the needed capacity according to
their expectations.
- The Support team to read to all technical document ex : RSD, design documents,..
- Support team to be aware of required technologies and frameworks used in the
project
3.2 HANDOVER
- Delivery team to send the handover agenda to the support manager covering all
project Modules.
- Delivery team to include Technical and Business handover
- Handover sessions will be recorded.
- Based on the Project size, and once handover is completed, A shadowing period of 1
month or based on Project Needs between the delivery and support teams for
technical and management activities is recommended.
- Delivery team to provide the latest code as deployed on production.
Delivery team to provide a stable development and staging environment with the
latest code and all the features deployed and working properly as the production
environment.
4 HANDOVER DELIVERABLES
The following items are required to be delivered by the delivery team to the support
team:
- Updated project documents (RSD, Design, Integration, Data migration, Release note,
User Manual, Deployment guide. etc.) .
- VSTS Walkthrough on the logged items
5 SUPPORT ACTIVITIES
- Kick off presentation/document for support activities to be prepared by support
manager and reviewed by the delivery PM that contains the Scope, Assumptions,
communication plan and share the consumption sheet.
- Monthly Status Report to be shared with the customers.
- Frequent status meeting (Monthly/Quarterly) to be conducted with customers.
