Technical Handover Plan
This documents cover points that should be covered in scope of handover process. Handover is essential step in ensuring the continuity of a project or task when responsibilities are being transitioned from one person or team to another.
Actions checklist
Action Item | Assigned Person | Comment/Link | Done? |
---|---|---|---|
Define the Scope | @Artur LebiedziĆski | Â | Done |
Inventory and Documentation | @Seweryn Niedzielski | Â | Done |
Prepare a summary of tools/technologies used. | Â | Â | Done |
Ensure all documentation is up-to-date. | Â | Â | Done |
Access Details | @Seweryn Niedzielski | Â | Â |
Transfer critical system/application logins. | Â | Â | Done |
Update access list post-handover. | Â | Â | Done |
Ensure secure credential transfer. | Â | Â | |
Ongoing Tasks and Responsibilities | @Artur LebiedziĆski | Â | Â |
Document in-progress tasks. | Â | Â | |
Document recurrent or routine tasks. | Â | Â | |
Identify unfinished tasks for the next tender. | Â | Â | |
Training Sessions | @Artur LebiedziĆski | Â | Â |
Identify areas needing live demos/walkthroughs. | Â | No demos were initially in the project scope. Weâd love to host them but it will require additional budget | |
Document available training sessions/recordings. | Â | User guides are available on the confluence page | |
List available onboarding materials. | Â | https://openimis.atlassian.net/wiki/spaces/OP/pages/3579838478 | |
Check if materials are in existing learning resources. | Â | Â | |
Environment Details | @Seweryn Niedzielski | Â | |
List number of environments (dev, test, prod). | Â | Â | |
Document differences between coreMIS and demo instances. | Â | Â | |
Detail environment-specific configurations/settings. | Â | Â | |
Describe deployment management and responsibilities. | Â | Â | |
Feedback Mechanism | @Artur LebiedziĆski | Â | Â |
Define post-handover communication methods. | Â | Communication after the handover can be done through e-mail or WhatsApp group. | |
Wrap-Up Meeting | @Artur LebiedziĆski | Â | Â |
Address receiving team's concerns. | Â | Â | |
Ensure access to necessary resources/contacts post-handover. | Â | The contact post handover from the SolDevelo side - @Artur LebiedziĆski |
Did you encounter a problem or do you have a suggestion?
Please contact our Service Desk
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/