Standard : Teams own and evolve their internal technical standards
Purpose and Strategic Importance
This standard ensures teams take active ownership of their internal technical standards, evolving them to meet changing needs while sustaining high engineering quality. By embedding autonomy and accountability into daily work, teams are empowered to innovate confidently while maintaining consistency and alignment.
Aligned to our "Engineering Excellence First" and "Architect for Change" policies, this standard encourages teams to continuously improve their craft, reduce friction, and strengthen their shared identity. Without it, quality drifts, practices stagnate, and teams become overly dependent on top-down mandates.
Strategic Impact
- Greater consistency and quality across delivery teams
- Reduced rework and operational risk through shared best practices
- Higher engineering morale and accountability
- Accelerated learning and continuous improvement through peer-led governance
Risks of Not Having This Standard
- Increased delivery variability and technical inconsistency
- Quality erosion due to lack of ownership or shared practices
- Slower adoption of new patterns, tools, or technologies
- Greater reliance on centralised enforcement rather than team autonomy
CMMI Maturity Model
Level 1 – Initial
| Category |
Description |
| People & Culture |
Standards are informal or ignored; improvements rely on individuals. |
| Process & Governance |
No clear structure for evolving or sharing technical practices. |
| Technology & Tools |
Tooling and environments vary widely without alignment to shared standards. |
| Measurement & Metrics |
No tracking of technical quality or adherence to internal standards. |
Level 2 – Managed
| Category |
Description |
| People & Culture |
Some teams define and apply standards, but ownership is unclear. |
| Process & Governance |
Practices exist but are inconsistently applied or reviewed. |
| Technology & Tools |
Shared tools exist but without governance or usage norms. |
| Measurement & Metrics |
Informal feedback highlights inconsistencies; no formal tracking. |
Level 3 – Defined
| Category |
Description |
| People & Culture |
Teams clearly own their internal standards and take pride in consistency. |
| Process & Governance |
Regular reviews and shared practices ensure standards remain relevant. |
| Technology & Tools |
Standard toolchains and practices are documented and maintained. |
| Measurement & Metrics |
Adherence to team-owned standards is reviewed and discussed routinely. |
Level 4 – Quantitatively Managed
| Category |
Description |
| People & Culture |
Teams use data and retrospectives to improve their standards. |
| Process & Governance |
Peer reviews, playbooks, and governance loops support continuous evolution. |
| Technology & Tools |
Tooling reinforces standard adoption and simplifies compliance. |
| Measurement & Metrics |
Metrics on quality, performance, and technical consistency are tracked. |
Level 5 – Optimising
| Category |
Description |
| People & Culture |
Continuous improvement of standards is embedded in culture and rituals. |
| Process & Governance |
Cross-team sharing drives convergence on high-quality patterns. |
| Technology & Tools |
Tools enable automated feedback, versioning, and pattern adoption. |
| Measurement & Metrics |
Maturity and impact of standards are measured across the engineering org. |
Key Measures
- Adoption and coverage of internal technical standards across teams
- Impact on code quality, deployment success, and defect rates
- Developer satisfaction and confidence in team-owned practices
- Frequency and effectiveness of standards reviews and improvements
- Evidence of cross-team learning and shared governance