The work
Maintenance covers the applications and environments named in the agreement. It can include defect investigation, dependency updates, changes required by an API vendor and smaller application changes. The agreement also sets out how requests are submitted, prioritized and approved.
Taking over maintenance requires a usable copy of the source and an understanding of how it reaches production. We review the deployment setup and important application behavior before changing it. Access to the relevant repositories and services must remain available for the covered work.
Each update has a record of what changed and the checks performed. Configuration or recovery instructions are revised when the change affects them. New features, hosting administration, monitoring and incident response need explicit coverage, including any response arrangements.
Technical considerations
- Coverage depends on access to source code, deployment systems and the third-party services the application uses.
- A maintenance request should identify the affected version and behavior, so the change can be reproduced and checked.