...
Action Item | Assigned Person | Comment/Link | Done? | |||
---|---|---|---|---|---|---|
Define the Scope | Create a summary of handover scope. |
| State what's outside of the handover scope. |
| ||
Inventory and Documentation |
| |||||
Prepare a summary of tools/technologies used. |
| |||||
Ensure all documentation is up-to-date. |
| |||||
Access Details | ||||||
Transfer critical system/application logins. |
| |||||
Update access list post-handover. |
| |||||
Ensure secure credential transfer. |
| |||||
Ongoing Tasks and Responsibilities | ||||||
Document in-progress tasks. |
| List any impending deadlines. |
| |||
Document recurrent or routine tasks. |
| |||||
Identify unfinished tasks for the next tender. |
| |||||
Training Sessions | ||||||
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. |
| |||||
Check if materials are in existing learning resources. |
| |||||
Review Current Issues & Challenges | ||||||
List outstanding bugs or unresolved tickets. |
| |||||
Document recurring/inherent challenges. |
| |||||
Environment Details |
| |||||
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 | ||||||
Define post-handover communication methods. |
| Detail the ticketing system and points of contactCommunication after the handover can be done through e-mail or WhatsApp group. |
| |||
Wrap-Up Meeting | ||||||
Address receiving team's concerns. |
| |||||
Ensure access to necessary resources/contacts post-handover. |
|
...