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

What are you looking for?

Standard : Engineering lead time is minimised from start of work to safe deployment (LTFC)

Purpose and Strategic Importance

This standard ensures teams minimise lead time-from the start of work to safe production deployment-by targeting Lead Time for Change (LTFC), a key DORA metric. Shorter lead time lowers risk, accelerates learning, and increases delivery flow efficiency.

Aligned to our "Fast Feedback Loops" and "Limit Work in Progress (WIP)" policies, this standard reveals and resolves bottlenecks that slow value creation. Without it, teams endure lengthy development cycles, delayed feedback, and hidden coordination costs.

Strategic Impact

  • Enables faster learning and course correction
  • Increases predictability and reduces scheduling risk
  • Shortens time-to-value for business outcomes
  • Exposes bottlenecks and constraints in delivery flow
  • Builds confidence in continuous improvement and operational excellence

Risks of Not Having This Standard

  • Teams experience long delays between start of work and impact
  • Bottlenecks in review, testing, or approval processes go unnoticed
  • Engineering output increases, but user or platform value lags behind
  • Metrics fail to reflect real flow health due to poor instrumentation
  • Platform teams operate with opaque or inconsistent delivery times

CMMI Maturity Model

  • Level 1 – Initial: Lead time is unmeasured and unpredictable. Teams cannot assess how long it takes to deliver value or where delays occur.

  • Level 2 – Managed: Teams manually track lead time for some work, but practices vary. Observations may include broad stages like development and deployment, without detailed instrumentation.

  • Level 3 – Defined: Lead time is consistently measured using automated tooling across source control, CI/CD, and work tracking systems. Work is scoped to enable fast, testable delivery.

  • Level 4 – Quantitatively Managed: Lead time metrics are analysed across phases. Delays are traced to specific causes, such as review queues, coordination gaps, or flaky tests, and actively addressed.

  • Level 5 – Optimising: Lead time metrics inform platform and process optimisation. Teams run flow acceleration experiments and share improvements across the organisation to raise overall maturity.


Key Measures

  • Median lead time (commit to deploy) across all services and systems
  • Breakdown of lead time by phase (dev, review, test, deploy)
  • Variance in lead time across teams or systems
  • Percentage of work deployed within a defined lead time threshold
  • Time-in-status tracking in ticketing systems aligned with delivery events
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
  • Lead Time for Change

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

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