migush / project-handover-checklist

List of checkboxes for IT project handover

project-handover-checklist

Handover

When a new person joins a project, project members are changed, or project is moved to another team, a handover should be thoroughly planned and executed.

Why?

• Reduce handover time.
• Make clear for everyone how handover will affect schedules/communication/budget.
• Reduce risks of post-handover work.
• Ensure good confidence for new members.

Handover is not a task, and it is not instant. Handover is always a project. Therefore it should be planned and executed like a project.

How to use this template

This template that will work for most teams. In some cases, new checkboxes may need to be added, or existing checkboxes removed.

This template can be used in a physical or digital way:

Physical

Print lists on paper and check items off when they are done.

Digital (fork)

Fork this project and edit the source to mark completed issues with '[x]' E.g.

• read this
• fork project
• plan and do handover
• PROFIT!

Digital (copy to issue tracker)

Create a project in your chosen issue tracker and add tasks.

Checklists

Project handover

Code handover

System handover

Handover completeness - Used to verify if handover was successful.

Links

Using task lists in GitHub-flavored markdown

License

Futurice Creative Commons Attribution 4.0 International (CC BY 4.0)