• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Codebases consistently meet high standards of quality

Purpose and Strategic Importance

This standard ensures codebases consistently reflect high-quality engineering practices, enabling systems that are reliable, maintainable, and scalable. It promotes shared accountability for technical integrity and strengthens confidence in delivery outcomes.

Aligned to our "Engineering Excellence First" policy, this standard drives consistency, readability, and long-term value across teams. Without it, teams risk fragmented code, technical debt, and reduced ability to evolve systems with speed and safety.

Strategic Impact

Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.

Risks of Not Having This Standard

  • Reduced ability to respond to change or failure
  • Accumulation of technical debt or friction
  • Poor developer experience and morale
  • Decreased confidence in releases and features
  • Misalignment between technical implementation and business priorities

CMMI Maturity Model

  • Level 1 – Initial: Quality is inconsistent and varies by individual developer.

  • Level 2 – Managed: Teams adopt informal practices to improve quality.

  • Level 3 – Defined: Quality standards are shared, documented, and consistently applied.

  • Level 4 – Quantitatively Managed: Quality is measured through automated tools and metrics.

  • Level 5 – Optimising: Quality practices evolve through feedback, benchmarking, and innovation.


Key Measures

  • Adoption metrics relevant to the standard (to be defined)
  • Quality, throughput, and system health metrics aligned to capability
  • Maturity scores based on structured assessment
Associated Policies
  • Engineering Excellence First
Associated Practices
  • Code Reviews & Pull Requests
  • Compliance-as-Code
  • Dependency Management Policies
  • Evolutionary Architecture
  • Linting and Static Code Analysis
  • Microservices Architecture
  • Mocking and Stubbing
  • Refactoring
  • Secure Code Training
  • Static Code Analysis
  • Engineering Onboarding Playbooks
  • InnerSource Development
  • User Session Replay Tools
  • Container Security Scanning
  • Dynamic Application Security Testing (DAST)
  • Threat Modelling Workshops
  • Vulnerability Management Dashboards
  • Accessibility Testing
  • Ensemble Testing
  • Shift-Left Testing
Associated Measures
  • Code Review Cycle Time
  • Automated Test Coverage
  • Automated Test Pass Rate
  • Code Churn
  • Code Coverage
  • Defect Escape Rate
  • Technical Debt Ratio

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering