Access and ownership
Agree repository access, intellectual property terms and account ownership early. List the services the application depends on and identify who controls each account. Transfer credentials through an agreed secure process rather than adding them to documentation or source code.
- Repository access
- Intellectual property terms
- Account ownership
- An agreed secure process for credentials
A repeatable setup
Ask for setup instructions that another engineer can follow. They should cover dependencies, configuration, environment differences and the build process. Verify the instructions by using them, and record anything that still requires manual action.
- Dependencies
- Configuration
- Environment differences
- The build process
Release and recovery
Document the deployment steps, the checks after release and the approach to rollback or recovery. Make clear who has access to production and who makes the decision to proceed. Include known limitations so the receiving team knows what to watch.
- Deployment steps
- Checks after release
- Rollback or recovery
- Who decides to proceed
Support after the handover
Agree which issues are covered, how they are reported and who responds. Keep enhancement requests separate from defects so priorities remain clear. A walkthrough gives the receiving team a chance to ask questions while the people who built the system are still available.
- Which issues are covered
- How they are reported
- Who responds
- Defects kept apart from enhancements