When to make a feature available to customers should be a business decision. In this video, learn how to decouple feature deployment from release and move away from high coordination release plans.
- [Instructor] If we could automate each and every step … in our release process and put changes live in production … as soon as they pass through the delivery pipeline, … we'd been doing what is called continuous deployment. … However, in the enterprise world, … release decisions often involve different areas … of the business and cannot be fully automated. … For example, marketing might need … to prepare a media campaign around the new offering. … Sales might need to send out an email … explaining a changing in pricing … and possibly prepare for a backlash. … Compliance might require regulators' approval, … or support might need to be trained for an upcoming release. … So continuous delivery, as opposed to continuous deployment, … is really about making timely, … well-informed release decisions unhindered … by technical constraints. … For that, we first need to trust our delivery pipeline … to ensure any release candidate passes … a sufficiently strong set of checks and controls. … Secondly, we need to be able …
In this course, instructor Manuel Pais shows leaders how to rethink CD in their organization to boost the speed and safety of their delivery workflow. Manuel explains why true continuous delivery is an organizational capability, and why software releases should be treated as business decisions. Plus, learn how to define a single path to production that balances speed and reliability; extract and transform data to enable faster release decisions; improve key metrics for high performance sustainably; and more.