Custom software maintenance

Software that keeps improving

Planned corrections, updates, and small improvements for custom applications after release.

EVIDENCE / DECISIONDIAGNOSTIC VIEWINPUTFIX01Focused improvements02Reliability work03Platform evolution
  1. 01Focused improvements
  2. 02Reliability work
  3. 03Platform evolution

Lifecycle work

Treat delivery as the start of operation

Custom applications encounter new data, operating environments, user needs, dependencies, and performance expectations. Maintenance provides a controlled way to respond.

Focused improvements

Add small capabilities and usability refinements against an agreed backlog.

Reliability work

Investigate reported issues and strengthen affected workflows.

Platform evolution

Update dependencies, deployment targets, documentation, and supported environments.

Operating model

Preserve context between releases

A useful maintenance relationship retains architecture knowledge, test evidence, release notes, and clear ownership of the production baseline.

Next step

Define the lifecycle before the next urgent change.

Separate routine evolution, incident response, and larger product investment into clear workstreams.