Evolving a walking skeleton to a fully fledged pipeline requires time and sustained effort. In this video, discover how to gradually raise the bar on release controls and the definition of ready.
- [Instructor] After the initial setup … of the delivery pipeline Walking Skeleton, … what we have is a broad but minimal set of criteria … that gives us a baseline understanding … of the adequacy of a change to go into production. … Now we need to gradually fine-tune and increase the controls … in our pipeline, according to the expectations … of our business, our customers, and our teams. … We increase our confidence that the changes … going to production are safe, fit for purpose, … and maintain or improve the overall health … of our code base. … Sustainable evolution of the pipeline … comes from the fact that we have a baseline … of release confidence with the current set of criteria. … Knowing that, we can identify and start tackling … the next highest priority gap in our Walking Skeleton. … For example, if we are concerned about the health … of our code, we might evolve from not just detecting … new blocking issues during static analysis, … but actually failing the pipeline … if there are any blocking issues at all. …
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.