Develop on Cadence, Release on Demand: Understanding Continuous Delivery, Deployment, and Release

Last week I wrote an article titled “Continuous Delivery, Continuous Deployment, I Can’t Tell Them Apart”, which sparked a lot of discussion because even Jez Humble’s definitions have evolved, making the confusion understandable.

The core idea is to decouple technical behavior from business decisions, summarized as “Develop on Cadence, Release on Demand”.

Both continuous delivery and DevOps aim for fast value delivery, but the ultimate goal is rapid, safe, sustainable, and high‑quality releases.

Jez Humble defines continuous delivery as the ability to get changes—features, configuration changes, bug fixes, experiments—into production or users safely and quickly in a sustainable way.

Deploying quickly requires a short deployment lead time, measured from code commit to successful production run, which drives MTTR and overall reliability.

SAFe’s continuous delivery pipeline splits the value stream into a technical domain (cadence) and a business domain (demand). The technical side focuses on version control, automated testing, CI, automated deployment, environment management, and loose coupling.

Key practices include:

Focusing on deployment lead time (minutes‑level targets)

Layered, hierarchical pipelines that ensure quality at each stage

Using feature toggles, canary releases, blue‑green deployments, and rolling updates to enable low‑risk, on‑demand releases

These pipelines bridge the gap between development and operations, turning deployment into a low‑risk, routine activity and empowering business decisions without heavy technical bottlenecks.

Assumption‑driven development ties each feature to a hypothesis about market impact, requiring feedback loops to validate assumptions before full release.

SAFe’s DevOps model, derived from the DevOps Handbook, emphasizes rapid, small‑batch deployments, automated pipelines, and continuous feedback to achieve sustainable value delivery.

Examples such as Etsy’s high‑frequency deployment pipeline illustrate how technical capability can dramatically simplify business decision‑making.

In summary, a well‑designed continuous delivery pipeline integrates technical and business domains, enabling fast, safe, and demand‑driven releases while maintaining high quality and low risk.