Standard : Code and infrastructure are maintained only while they deliver real business value
Purpose and Strategic Importance
This standard ensures that codebases and infrastructure components are actively evaluated and maintained only when they continue to deliver tangible business value. Retiring or refactoring obsolete elements prevents waste, reduces technical debt, and optimises resource allocation.
It supports the policy “Deliver What’s Needed, Not Just What’s Possible” by promoting disciplined lifecycle management. Without this standard, organisations risk carrying unnecessary maintenance burdens that slow innovation and increase costs.
Strategic Impact
- Reduces technical debt and maintenance overhead
- Improves system agility and scalability
- Optimises engineering resources and focus
- Enhances system reliability and performance
- Supports clear ownership and accountability
Risks of Not Having This Standard
- Accumulation of legacy code and infrastructure increasing risk
- Wasted effort maintaining low-value or unused components
- Reduced ability to innovate or respond to change
- Increased operational costs and complexity
- Lower team morale due to frustration with outdated systems
CMMI Maturity Model
Level 1 – Initial
| Category |
Description |
| People & Culture |
- Legacy code and infrastructure persist without evaluation of value or relevance. |
| Process & Governance |
- No formal lifecycle or decommissioning processes exist. |
| Technology & Tools |
- Limited tooling to track usage or value of code and infrastructure. |
| Measurement & Metrics |
- No metrics assess maintenance effort versus business impact. |
Level 2 – Managed
| Category |
Description |
| People & Culture |
- Some awareness of technical debt but inconsistent practices for cleanup or retirement. |
| Process & Governance |
- Basic processes encourage evaluation of code and infrastructure value. |
| Technology & Tools |
- Tools provide partial insights into usage and maintenance costs. |
| Measurement & Metrics |
- Some tracking of maintenance effort and impact on delivery exists. |
Level 3 – Defined
| Category |
Description |
| People & Culture |
- Value-based maintenance and decommissioning are embedded in engineering culture. |
| Process & Governance |
- Formal lifecycle management processes govern cleanup and refactoring decisions. |
| Technology & Tools |
- Integrated platforms support tracking and analysis of component value and usage. |
| Measurement & Metrics |
- Metrics guide prioritisation of maintenance and retirement efforts. |
Level 4 – Quantitatively Managed
| Category |
Description |
| People & Culture |
- Data-driven decisions optimise maintenance and retirement to maximise value. |
| Process & Governance |
- Metrics influence resource allocation and technical debt reduction strategies. |
| Technology & Tools |
- Advanced analytics predict maintenance risks and recommend refactoring actions. |
| Measurement & Metrics |
- Quantitative links exist between maintenance activities and business performance. |
Level 5 – Optimising
| Category |
Description |
| People & Culture |
- Continuous improvement culture drives disciplined lifecycle management. |
| Process & Governance |
- Policies adapt dynamically to evolving system architectures and business goals. |
| Technology & Tools |
- AI-assisted tools support proactive maintenance and decommissioning decisions. |
| Measurement & Metrics |
- Organisational maturity in lifecycle management drives agility and cost-efficiency. |
Key Measures
- Percentage of code and infrastructure actively delivering business value
- Maintenance effort versus value delivered ratios
- Frequency and success of decommissioning or refactoring initiatives
- Impact of maintenance decisions on system reliability and delivery speed
- Engineer feedback on maintenance burden and lifecycle clarity