Do you know how to handover a project?
A common source of pain, is picking up a project without a decent/complete handover. To have a successful project you must navigate over the problem of changing resources/people leaving etc.
As soon as an employee has given their resignation notice, their manager should become responsible for ensuring a successful handover takes place. Each project they were involved in should be reviewed and another employee with a matching skill set should be selected to receive the handover. Handovers should be booked in for each project with both employees in attendance, as early as possible and with high priority.
Once the handover is complete, the resigning employee should no longer work on that project so that any gaps in knowledge can be covered ideally before their notice period expires.
Always ensure that you complete the following checklist and always send the email confirming the handover is complete.
Here are the 8 steps you should follow for a good handover.
- Confirm current tasks
- Confirm future tasks
- Confirm the primary contacts
- Do a code review (only for developers)
- Review the client portal
Confirm and document the location of info and procedures (hopefully, these are on a wiki or SharePoint document library). For a development project this may include:
- Source control. Make sure there is no stale or old branches. Check out: Do you know when to branch in git?
- How to Build and Package
- Testing Steps and users and passwords to access the test and staging servers
- Deployment Steps
- Servers and Passwords
- Failure & Recovery Steps
- Test that the users, passwords, URLs and server details provided in the handover are correct by logging in with each
- Complete the Handover by sending an email with: As per our meeting the handover has been completed to my satisfaction
|Subject:||SSW - Northwind handover|
- Confirm outstanding tasks Nothing.
- Confirm planned tasks Get release 43 out.
- Source control: Nothing
- Data storage: file://server/DataSSW/SSWProducts/Northwind
- Deployment: Make a build by using WISE
- Test: seadragon
- Production: squirrel
- Failure & Recovery: Do not work on the Master folder, work on local machine. If it has some issue, grab the file from master folder. Always backup master folder’s file before uploading the changes to the master folder
- Update the Employee Responsibilities in SSW intranet: TODO
Figure Bad Example - This handover is incomplete and light on details
|Subject:||SSW - Northwind handover|
Done - As per our meeting the handover has been completed to my satisfaction
- Confirm outstanding tasks: Nothing.
- Confirm planned tasks: Next release is Release 43. The aim of this release is to improve the reporting available from the management module with chart reports Query = tfs\Northwind\Work Items\Team Queries\All Work Items - R43 - Management Module Reporting Backlog is in TFS. Query = tfs\Northwind\Work Items\Team Queries\All Work Items - Backlog
- Source control: file://tfs.ssw.com.au/tfs/Northwind
- Data storage: file://server/DataSSW/SSWProducts/North wind
- Make a build by using WISE
- Test db to connect to: server: seadragon database: SSWNorthwind_test
- Production db to connect to: server: squirrel database: SSWNorthwind
- Failure & Recovery: Do not work on the Master folder, work on a local machine. If it has some issue, grab the file from the master folder. Always backup master folder’s file before uploading the changes to the master folder. If a problem occurs, restore the backup of the master folder and restart
- Update the Employee Responsibilities in SSW intranet: DONE
- Complete Handover
Figure: Good Example - This handover has lots of URLs and is complete
If you need to handover only a single task there are more details here: Do you know how to hand over tasks (aka Emails) to others?