Scribd
Upload
60 views2 pages

Knowledge Transfer Process at Cubet

The document outlines the knowledge transfer process at Cubet, emphasizing the importance of proper documentation and communication within the project management system. It details methods for knowledge transfer, including mentorship, guided demos, work shadowing, paired work, and client introduction, ensuring a smooth transition for new resources. The process aims to maintain project continuity and equip new team members with the necessary knowledge to operate independently.

Uploaded by

Rony James
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
60 views2 pages

Knowledge Transfer Process at Cubet

The document outlines the knowledge transfer process at Cubet, emphasizing the importance of proper documentation and communication within the project management system. It details methods for knowledge transfer, including mentorship, guided demos, work shadowing, paired work, and client introduction, ensuring a smooth transition for new resources. The process aims to maintain project continuity and equip new team members with the necessary knowledge to operate independently.

Uploaded by

Rony James
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

KNOWLEDGE TRANSFER PROCESS IN CUBET

KNOWLEDGE ACCUMULATION
● Proper documentation is followed for all projects.
● All documents involved in a project starting with SRS, is maintained within
the project management System
● All tasks in the project are given proper detailed description
● All conversations related to the project happen only within the PM system
under the project.
● Video documentations of complex modules and codes are created by the
corresponding developer and maintained within the project

KNOWLEDGE TRANSFER
Depending on how soon we are able to identify the resource, who will be taking
over from the current resource, we use the following processes:
● Mentorship : The leaving resource will do multiple sessions to explain the
various documentations gathered as part of the project.
● Guided Demo : The person with first-hand knowledge works to share and
show it to the individual who is learning the function.
● Work shadowing : The new resource is put as a shadow resource in the
project and given tasks under the supervision of the leaving resource.
● Paired Work : Where in both resources work parallelly with peer reviewing
● Take over and intro to client :The new resource confirms that full KT is
completed and he is able to independently work on the project. Once this
is complete, the new resource is given independent tasks to work with, and
then introduced to the client for full take over.

You might also like