Pete as a Newspaper

If you’re like me, you’re still learning. You’ve read a ton about web development, web project management, freelance business management, and a shit ton of Garfield comics.

You might know that when planning a project, that there should be what’s essentially a ‘hand-off plan’. In the absence of such a plan, both you and the client will suffer from the lack of direction, and the project will linger and torture you and everyone you love.

‘hand-off’ topics

Melodrama aside, here’s an overview of ‘hand-off’ topics you may want to address:

Finalization of any services

Are there unresolved items from your contractual agreement? Were there mutually-agreed-upon scope adjustments that need addressing? This is the time to dot those i’s, folks.

Collection and handover of documents

Drawings, specs, maintenance docs, etc. Get those gator clips out, and wrangle all the hard copy that’s relevant to the work you’ve just completed. You created usage manuals, right? ;)

Outline project success

You did it! Yay, all those plans and hard work were accurately measured, and you passed with flying colors. Now summarize. note: it’s likely that something wasn’t as successful as you’d hoped. Point it out to your stakeholders, explain why.

Summary report

Wrap up the hand-over by summarizing the ups and downs of the project. Make sure you explain and reinforce any changes made along the way (adjustments in scope, budget, schedule, quality, etc.), and assign an accountable/approving party to each change.

Final meeting

Did I say meeting? I meant party. Yes, happinees, beer, and the depths of celebration that come when those things are combined. Don’t forget the paperwork :)