Catherine WatsonProgram Manager, EPMO| Aged Care Quality & Safety CommissionKingston, Tasmania, Australia
Has anyone ever had to produce a Handover document at the closure of the project?? I am moving on and want to leave my project in a firm state to continue its development etc within the business. I've been advised to produce a handover document but have no idea of the kind of information to include. Any ideas??? Saving Changes...
At project closure you may want to document what you delivered. A simple table comparing your original project objectives, acceptance criteria, and what you actually delivered may enlighten the business and provide accountability for the future.
In addition, a "lessons learned" summary would be valuable. List what happened, what you desired to happen, and how to prevent or improve upon each factor in the future.
Finally any relevant technical and planning information, including compiled links to any online deliverables would help the business come enhancement time. Saving Changes...
Isabelle BadinandAgile Delivery Manager| AvivaLondon, United Kingdom
Hello, Where I work in the hand over document we include a brief description of the system, who has worked / has knowledge about it, maintenance rules (for example clean up the database etc..), things to do if the application fails (are there some simple testing procedures to try to find out the problem, does the database need to be rebooted before the application server etc..), how often back up need to be made...
"Ambition is like a frog sitting on a Venus Flytrap. The flytrap can bite and bite, but it won't bother the frog because it only has little tiny plant teeth. But some other stuff could happen and it could be like ambition."
