A walking skeleton is a minimal implementation of a pipeline that covers all the desired activities and controls. In this video, see a walking skeleton example and discover why it increases visibility over the release process.
- [Instructor] This is a Typical Delivery Pipeline … for many teams. … It focuses on the technical activities … we know we need to perform. … Build our artifacts, test them and deploy to production … at some point. … This is what organizations adopting Continuous Delivery … tend to start with and it makes sense … from a purely software development perspective. … But if we consider the goal of a delivery pipeline … to be about proving that the release candidate … is not ready for production, … then we might wonder if building tests are enough … to give us confidence that this change … won't lead to issues in production … that might end up affecting our clients. … Hopefully, it's not a matter of feeling lucky, … but ensuring that the relevant set of technical … and business criteria is met before changes get deployed. … The typical pipeline focuses on the mechanics … of taking a code change from version control … all the way to production. … But this does not answer questions like, … are we releasing the intended fixes, features …
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.