Do you know how to hand over a project?

Last updated by Piers Sinclair [SSW] 4 months ago.See history

Transitioning a project smoothly is crucial, whether due to changing project assignments or planned absences. A thorough handover process ensures continuity and minimizes disruption.

The handover is the responsibility of the person transitioning away from the project.

It's essential to initiate the handover planning as soon as a transition is known. Review the project with the selected team member who will take over, then schedule a handover meeting with high priority.

Tip: If you are leaving a company, ideally your handover should be done as soon as possible so that the developer taking over can start working on them while you’re still available to answer any questions.

Figure: This is not how you hand over a project

Handover Checklist

Send this checklist in an email before the handover meeting to guide the discussion:

Ensure you reply done to this email after the handover meeting, with a checked by from the recipient.

For individual task handovers, see how to hand over email tasks to others.

Tip: Recording the handover process via a Teams call can be beneficial for future reference.

Even better at the end of a long call record a quick summary so everybody knows what was agreed. And it's easier for other people to watch.

Adam Cogan
Brady Stroud
We open source.Loving SSW Rules? Star us on GitHub. Star
Stand by... we're migrating this site to TinaCMS