<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Phase 4: Deliver on Demand on MinimumCD Practice Guide</title><link>https://beyond.minimumcd.org/docs/continuous-deployment/</link><description>Recent content in Phase 4: Deliver on Demand on MinimumCD Practice Guide</description><generator>Hugo</generator><language>en</language><atom:link href="https://beyond.minimumcd.org/docs/continuous-deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Deploy on Demand</title><link>https://beyond.minimumcd.org/docs/continuous-deployment/deploy-on-demand/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beyond.minimumcd.org/docs/continuous-deployment/deploy-on-demand/</guid><description>&lt;div class="pageinfo pageinfo-primary"&gt;&#10;&lt;p&gt;&lt;strong&gt;Phase 4 - Deliver on Demand&lt;/strong&gt; | &lt;span class="scope-label scope-label--org"&gt;Scope: Org&lt;/span&gt;&#10;| Original content&lt;/p&gt;&#10;&lt;p&gt;Deploy on demand means that any change which passes the full automated &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#pipeline"&gt;pipeline&lt;/a&gt; can reach production without waiting for a human to press a button, open a ticket, or schedule a window. This page covers the prerequisites, the transition from &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#cd-continuous-delivery"&gt;continuous delivery&lt;/a&gt; to &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#continuous-deployment"&gt;continuous deployment&lt;/a&gt;, and how to address the organizational concerns that are the real barriers.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="continuous-delivery-vs-continuous-deployment"&gt;Continuous Delivery vs. Continuous Deployment&lt;/h2&gt;&#10;&lt;p&gt;These two terms are often confused. The distinction matters:&lt;/p&gt;</description></item><item><title>Progressive Rollout</title><link>https://beyond.minimumcd.org/docs/continuous-deployment/progressive-rollout/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beyond.minimumcd.org/docs/continuous-deployment/progressive-rollout/</guid><description>&lt;div class="pageinfo pageinfo-primary"&gt;&#10;&lt;p&gt;&lt;strong&gt;Phase 4 - Deliver on Demand&lt;/strong&gt; | &lt;span class="scope-label scope-label--team"&gt;Scope: Team&lt;/span&gt;&#10;| Original content&lt;/p&gt;&#10;&lt;p&gt;Progressive rollout strategies let you deploy to production without deploying to all users simultaneously. By exposing changes to a small group first and expanding gradually, you catch problems before they affect your entire user base. This page covers the three major strategies, when to use each, and how to implement automated &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#rollback"&gt;rollback&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="why-progressive-rollout"&gt;Why Progressive Rollout?&lt;/h2&gt;&#10;&lt;p&gt;Even with comprehensive tests, &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#production-like-environment"&gt;production-like environments&lt;/a&gt;, and small &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#batch-size"&gt;batch sizes&lt;/a&gt;, some issues only surface under real production traffic. Progressive rollout is the final safety layer: it limits the blast radius of any deployment by exposing the change to a small audience first.&lt;/p&gt;</description></item><item><title>Experience Reports</title><link>https://beyond.minimumcd.org/docs/continuous-deployment/experience-reports/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://beyond.minimumcd.org/docs/continuous-deployment/experience-reports/</guid><description>&lt;div class="pageinfo pageinfo-primary"&gt;&#10;&lt;p&gt;&lt;strong&gt;Phase 4 - Deliver on Demand&lt;/strong&gt; | &lt;span class="scope-label scope-label--org"&gt;Scope: Org&lt;/span&gt;&lt;/p&gt;&#10;&lt;p&gt;Theory is necessary but insufficient. This page collects experience reports from organizations that have adopted &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#continuous-deployment"&gt;continuous deployment&lt;/a&gt; at scale, including the challenges they faced, the approaches they took, and the results they achieved. These reports demonstrate that &lt;a href="https://beyond.minimumcd.org/docs/reference/glossary/#cd-continuous-delivery"&gt;CD&lt;/a&gt; is not limited to startups or greenfield projects - it works in large, complex, regulated environments.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="why-experience-reports-matter"&gt;Why Experience Reports Matter&lt;/h2&gt;&#10;&lt;p&gt;Every team considering continuous deployment faces the same objection: &amp;ldquo;That works for [Google / Netflix / small startups], but our situation is different.&amp;rdquo; Experience reports counter this objection with evidence. They show that organizations of every size, in every industry, with every kind of legacy system, have found a path to continuous deployment.&lt;/p&gt;</description></item></channel></rss>