Handing it over

Documentation somebody else can maintain, and the handover conversation that stops you being the permanent owner of everything you built. THE DOCUMENTATION IS SHORT AND IT IS SPECIFIC. Per artefact: what it does, who it is for, where it runs, what it depends on, what to do when it fails, and who owns it now. One page each. A twenty-page design document is a document nobody opens, and the parts of it somebody needs at 7am are the four lines above. Name the OWNER, and name a person rather than a team. "Finance operations" owns nothing; a named person does, and they know they do because you had the conversation. THE HANDOVER CONVERSATION IS THE PART THAT ACTUALLY WORKS. Walk the person through running it, breaking it, and fixing it — in that order. Have THEM do it while you watch, rather than demonstrating. Everything they have to ask you…

In this module: Module 18 · Capstone: one technical work package, end to end

1. 1The brief
2. 2Sequencing the work
3. 3Building it
4. 4Proving it
5. 5Handing it over
6. 6Where to go next