continuous delivery
An approach that makes every completed feature ready for user release right away, using small batches and heavy automation across build, test, and deployment steps.
Key Points
- Automates the path from code commit to a production-ready build (pipeline for build, test, and deploy).
- Uses small, frequent changes to lower risk and speed up feedback from users and stakeholders.
- Code is always in a releasable state; release timing can still be a business decision.
- Often relies on practices like trunk-based development, feature flags, and strong test coverage.
Example
An agile team completes a user story, merges it to the main branch, and an automated pipeline runs unit, integration, and security tests. If everything passes, the system creates a production-ready artifact and deploys it to a staging environment, allowing product owners to release to customers at any time.
PMP Example Question
A scrum team ensures every completed story flows through an automated pipeline and is always in a ready-to-release state, though product leadership decides when to push to customers. What practice does this describe?
- Continuous deployment
- Continuous delivery
- Rolling wave planning
- Iterative development
Correct Answer: B — Continuous delivery
Explanation: Continuous delivery keeps increments deployable at all times through automation and small batches, while the actual release can be a deliberate business decision.
