01Understand the application before changing it
Support starts with a review of source code, environments, deployment instructions, and known issues. The aim is to identify what the business depends on and establish a clear way to make and verify changes.
02A manageable queue of improvements
Bugs, content changes, performance work, and new features are prioritised together. Each agreed change has a clear outcome, and significant changes are reviewed before release. Response windows and monthly scope are defined in the support agreement.
03Preserve the ability to recover
Application changes should be traceable through Git. Database and uploaded-file backups need a defined schedule and a recovery process. I can help review and document those procedures as part of ongoing support.