Software Maintenance & Optimization
Plan maintenance for a live application around its users, operational risks and release process, whether Dicem built it or another team did.
Planning your project
Taking over an existing application
Begin with access to the repository, deployment process, infrastructure and available documentation. Review dependency health, error logs and backup recovery before promising changes. The initial review should identify urgent risks, missing access and the scope of ongoing support.
Agree support coverage explicitly
Response times, support hours and incident severity need to be agreed in the service scope. A response-time commitment is not a guaranteed resolution time. Define how incidents are reported, who can authorise changes and which third-party outages fall outside the support team's control.
Prioritise measurable improvements
Use actual error rates, slow user journeys and customer feedback to prioritise work. Test changes in a separate environment and maintain a rollback path. Budget maintenance capacity separately from major new features so the application can remain supported as the roadmap grows.
Bring to your first conversation
- Repository, hosting and deployment ownership details
- Current issues, logs and the most important user journeys
- Required support hours and a prioritised improvement backlog
Discuss your existing application