Gather what you already have
Start with code, documentation, operational information, accounts, agreements and contact details. Also try to capture the knowledge held by users and others who have worked closely with the system.
Secure access
Check that the company has access to code repositories, servers, databases, domains, cloud services and other important accounts. It's hard to take responsibility for a system no one can access.
Don't try to understand everything at once
Start with the parts that matter most to the business and the areas where the risk is greatest. Knowledge can then be built up step by step as the system is maintained and changed.
Document what the next person needs
Good documentation does not need to describe every line of code. It should explain the system's key components, how to operate it, what it depends on and how to make common changes.
Make sure responsibility doesn't rest with one person
The goal should be to reduce reliance on individuals, not just shift it from one developer to another. Code, documentation and working practices need to make knowledge easy to share.
Contact us
Do you need someone to take over?
We can get to know existing systems and fill gaps in the knowledge needed to maintain and develop them.
