Continuous delivery allows teams to reduce dramatically the transaction cost of releasing high-quality software, so you can do it much more frequently, providing a much richer and faster feedback cycle from users back to product teams. But, in turn, you need to change the way you think about managing the flow of work through the software delivery process.
This article presents five practices of continuous delivery that can help you to create the most efficient path from hypothesis to continuous feedback. Following the practices outlined here, you can deliver single-feature or small-story batches that dramatically decrease the time needed to build a new product or new release, testing and moving forward on successful features and redesigning or dropping features that fail (or that users show they don’t really want). The five practices discussed in this article are:
* Start with a minimum viable product (MVP).
* Measure the value of your features.
* Perform just enough analysis up front.
* Do less.
* Include feature toggles in your stories.