...
Action Item | Assigned Person | Comment/Link | Done? |
|---|---|---|---|
Define the 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. |
| ||
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. |
| ||
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. | Communication 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. | The contact post handover from the SolDevelo side - Artur Lebiedziński |
|
Additional information about points
1. Define the Scope:
Create a summary of what will be in scope of the handover.
Leading question: What systems, projects, or processes are being handed over?Clearly state what is outside of the handover scope.
Leading question: Are there aspects that are out of the scope of this handover?
2. Inventory and Documentation:
Prepare a summary of what was used for the project.
Leading question: What tools or technologies are involved in the project?
Prepare a summary of the documentation. Ensure that all documentation is up-to-date and relevant, if it isn’t explain the discrepancy.
Leading question: What documentation is available and are there any gaps in the documentation that need to be addressed?
3. Access Details:
Are there critical system or application logins that need to be transferred?
Who currently has access, and who should have access post-handover?
How will credentials be securely transferred?
4. Ongoing Tasks and Responsibilities:
What tasks are currently in progress?
Are there any impending deadlines?
Which tasks are recurrent or routine?
What part will not be finalized in scope of project and has to be moved to next tender?
5. Training Sessions:
What key areas might need a live demonstration or walkthrough?
Are there any complex processes or tools that need in-depth training?
Are there video recordings or training sessions that can be revisited later?
Are there any materials that can be shared and used for users onboarding?
Are materials part of the existing learning materials? If not how could they be included.
6. Review Current Issues & Challenges:
Are there any outstanding bugs or unresolved tickets?
Which challenges are likely to recur or are inherent to the system or process?
How further development of other openIMIS parts may affect created modules?
7. Environment Details:
How many different environments (dev, test, prod) are there?
How coreMIS instance is different from other imis instances like demo (custom configurations, etc.)?
Are there specific configurations or settings unique to each environment?
How are deployments currently managed and who is responsible?
8. Feedback Mechanism:
How can the receiving team raise concerns or ask questions post-handover?
Description of ticketing system and points of contact.
9. Wrap-Up Meeting:
What concerns does the receiving team have that haven't been addressed yet?
Are there resources or contacts they need access to, post-handover?