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

What are you looking for?

Standard : Changes are introduced into production frequently and sustainably (DF)

Purpose and Strategic Importance

This standard ensures changes are deployed to production frequently and sustainably, enabling faster feedback, safer releases, and quicker time-to-value. Deployment Frequency (DF) is a key DORA metric and a signal of healthy engineering flow.

Aligned to our "Fast Feedback Loops" and "Empower Teams to Self-Serve" policies, this standard promotes autonomy, reduces risk, and supports continuous delivery. Without it, releases become bottlenecks, innovation slows, and operational risk increases.

Strategic Impact

  • Shorter feedback cycles between idea, build, and release
  • Reduced change risk through smaller, more frequent batches
  • Higher confidence in the delivery pipeline and system observability
  • Improved time-to-value and customer responsiveness
  • Increased autonomy for product and platform teams

Risks of Not Having This Standard

  • Long delays between completed work and customer impact
  • Greater risk per change due to large, infrequent releases
  • Poor visibility into delivery system health
  • Reduced ability to respond to learning, risk, or urgency
  • Bottlenecks in governance, review, or deployment practices

CMMI Maturity Model

  • Level 1 – Initial: Deployments are infrequent, manual, and often stressful. Releases require significant coordination and are prone to delays or rollbacks.

  • Level 2 – Managed: Some automation exists, but deployments are still periodic and depend on manual approval or synchronisation between teams. Release cadence is inconsistent.

  • Level 3 – Defined: Teams deploy frequently via automated CI/CD pipelines. Releases are decoupled from user impact using techniques like feature flags, blue-green deployments, or canary releases.

  • Level 4 – Quantitatively Managed: Deployment frequency is tracked, benchmarked, and reviewed. Data is used to identify variation across teams or services and inform targeted improvements.

  • Level 5 – Optimising: Deployment is a routine, low-risk activity. Teams continuously improve delivery speed and safety, with frequent, small-batch releases that drive rapid learning and high system resilience.


Key Measures

  • Median time between successful production deployments
  • Percentage of deployable changes shipped per week
  • Percentage of teams with fully automated deploy pipelines
  • Ratio of deployments to rollbacks or hotfixes
  • Deployment frequency per system or service (software, data, platform)
Associated Policies
  • Fast Feedback Loops
Associated Practices
  • Error Budget Policies
  • Trunk-Based Development
  • SLOs, SLIs, and SLAs
  • Feature Toggles (Flags)
  • Release Orchestration Tools
Associated Measures
  • Deployment Frequency

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

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