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

What are you looking for?

Standard : Infrastructure is version controlled and peer reviewed

Purpose and Strategic Importance

This standard ensures infrastructure is managed as code-version controlled, peer reviewed, and tested before deployment. It brings rigour, traceability, and collaboration to infrastructure changes, reducing risk and improving quality.

Aligned to our "Inclusive & Diverse Engineering Culture" policy, this standard promotes shared ownership, continuous learning, and safer delivery. Without it, changes are harder to track, review, and recover from.

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: Infrastructure changes are manual and inconsistently tracked.

  • Level 2 – Managed: Version control is used, but peer review is informal.

  • Level 3 – Defined: Infrastructure is managed as code with peer review and testing in place.

  • Level 4 – Quantitatively Managed: Deployment metrics are monitored and used to guide improvements.

  • Level 5 – Optimising: Infrastructure as Code practices evolve continuously based on feedback and automation outcomes.All infrastructure changes are tracked in source control, reviewed by peers, and tested automatically before deployment.


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
  • Infrastructure as Code (IaC) & Policy as Code
Associated Practices
  • Configuration as Code
  • Immutable Infrastructure
  • Chaos Engineering
  • End-user Experience Monitoring
  • Release Orchestration Tools
Associated Measures
  • Infrastructure as Code (IaC) Coverage

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

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