TKO-41Recommended
Record handover sessions before the old team leaves
Before the previous team's last day, hold sessions where they walk through the system, and keep dated notes in the repository. Cover deploys, rollback, scheduled jobs, outside services, recent incidents and known bugs.
How to do it
What lives in one person's head leaves with that person. Ask them to deploy and roll back while you watch and write down each step. Turn each answer into a runbook or an entry in the system map. Ask for the last three incidents and what fixed them. A recording of a person is personal data, so ask before you record and delete it once the notes are written. Book the sessions before access is removed, as Find every part that depends on one person or one tool finds who to ask.
How to check
The docs folder holds notes dated before the handover date that cover all six topics in the rule. Each open question in them is answered or has a ticket.
Related rules
- DOC-44 Keep runbooks next to the code they run in Documentation
- TKO-5 Map the system before changing it in Codebase takeover
- TDD-8 Find every part that depends on one person or one tool in Technical due diligence
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/codebase-takeover/triage/record-handover-sessions">Agent Wranglers codebase takeover playbook</a>. In code you write, add a comment next to it with the same link.