• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Automation is embedded in team thinking and architecture

Purpose and Strategic Importance

This standard ensures automation is a core part of team mindset and system architecture—not an afterthought. By embedding automation into how we design and build, teams reduce manual effort, improve consistency, and deliver with greater speed and confidence.

It supports our policy to "Automate everything possible" and reinforces a modern engineering culture that values self-service, resilience, and scalable operations. Without this focus, teams risk fragmented systems, slower delivery, and rising operational debt.

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

Category Description
People & Culture - Automation is ad hoc and treated as optional.
- Only specialist team members use automation tools.
Process & Governance - No formal automation strategy or practices.
- Manual processes dominate builds and releases.
Technology & Tools - Limited or no automation tools integrated into workflows.
- Scripts or tools exist but lack standardisation.
Measurement & Metrics - No metrics tracking automation coverage or impact.

Level 2 – Managed

Category Description
People & Culture - Teams begin adopting automation reactively to solve pain points.
- Some awareness of automation benefits.
Process & Governance - Basic automation scripts and tools are adopted.
- Automation considered during delivery but not mandated.
Technology & Tools - CI/CD pipelines begin incorporating automated steps.
- Manual interventions still common.
Measurement & Metrics - Tracking of automated build/test coverage starts but is inconsistent.

Level 3 – Defined

Category Description
People & Culture - Automation is embedded in team culture and engineering practices.
- Teams proactively seek automation opportunities.
Process & Governance - Automation requirements included in design and architectural decisions.
- Standardised automation processes across teams.
Technology & Tools - Mature CI/CD pipelines with comprehensive automated testing and deployment.
- Use of infrastructure as code and automated configuration management.
Measurement & Metrics - Regular metrics on automation coverage, build success rates, and deployment frequency.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Teams use data to prioritise automation investments.
- Automation is a shared responsibility across roles.
Process & Governance - ROI on automation activities measured and used to inform strategy.
- Automation practices audited for consistency and effectiveness.
Technology & Tools - Advanced automation includes security, performance testing, and environment provisioning.
- Automated rollback and recovery integrated.
Measurement & Metrics - Quantitative tracking of automation impact on delivery speed, defect rates, and operational resilience.

Level 5 – Optimising

Category Description
People & Culture - Automation is a continuous, evolving enabler of innovation and resilience.
- Teams lead innovation by experimenting with new automation approaches.
Process & Governance - Automation strategy is adaptive, incorporating emerging technologies.
- Automation supports organisational agility and technical debt reduction.
Technology & Tools - Intelligent automation leverages AI/ML for predictive operations.
- Fully self-service environments with end-to-end automation.
Measurement & Metrics - Continuous improvement metrics capture automation efficiency, quality improvements, and cost savings.

Key Measures

  • Automation coverage (% of build, test, deployment automated)
  • Deployment frequency and mean time to recovery (MTTR)
  • Defect rates related to manual vs automated processes
  • ROI on automation efforts (time saved, error reduction)
  • Developer satisfaction and productivity indicators related to automation
Associated Policies
  • Architect for Change
Associated Practices
  • Drift Detection & Correction
  • GitOps
  • Continuous Delivery (CD)
  • Continuous Deployment
  • Continuous Integration (CI)
  • Infrastructure as Code (IaC)
  • Deployment Pipelines
  • Automated Rollbacks
  • Alert Fatigue Management
  • Automated Incident Response

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

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