The problem it answers
- A bug list with no owner
- Fixes bundled into a rewrite that never starts
- Regressions
How this category works
Maintenance is how software stays safe and useful. It is a planned service — contracts, response, upgrades — not a favor after the project invoice. Every build we do has a path into this category.
1. Define the scope
Which systems, which hours, what counts as urgent.
2. Stabilize the backlog
Known bugs, risky versions, and missing monitors first.
3. Run the cadence
Patches, small improvements, and a report of what changed.
4. Plan versions
Upgrades scheduled, not forced by an outage.