In 30 seconds
- Deploy often; release when the business decides.
- Techniques: feature toggles, dark launches, gradual rollouts.
- A SAFe term for the final stage of its continuous delivery pipeline.
Deploy vs release
| Deploy | Release | |
|---|---|---|
| What | Code goes to production | Users can use the feature |
| Who decides | Engineering | Business and product |
| How often | Very often | When it makes sense |
Techniques
- Feature toggles: code ships switched off
- Dark launches: run new code without exposing it
- Canary and staged rollouts: release to a small group first
Why it helps
Small, frequent deploys are less risky than big ones, and releases can be timed for marketing, training or customer readiness. In the Scaled Agile Framework, release on demand is the last stage of the continuous delivery pipeline.
Myth vs reality
Myth · Release on demand means releasing constantly.
Reality · It means being able to release whenever chosen.
Myth · It's only for web products.
Reality · Mobile and enterprise products use toggles and staged rollouts too.
Myth · Toggles are free.
Reality · Old toggles become debt; remove them once released.
FAQ
Is this the same as continuous deployment?
No; continuous deployment releases automatically. See the comparison page.
What do we need first?
Automated tests and a reliable deployment pipeline.
Who decides when to release?
Usually the Product Owner or product management.