When software releases require manual steps not mapped in the pipeline, the current status of changes becomes blurry. In this video, you will learn how to map the value stream in the pipeline to increase visibility.
- [Instructor] Regardless of how much autonomy a team has … to develop and deliver their software, … dependencies on other teams are inevitable. … Therefore, we cannot look at to deliver pipeline … as being owned by a single team. … But rather, a collective ownership. … The pipeline needs to include all the necessarily … release activities, not just what's in scope … of the delivery team. … Whatever release processes exist in our organization, … whether documented or not, they need to be visible … in the delivery pipeline as well. … It's common in enterprises for release to production … to require checks or approvals from change control boards, … security teams, legal compliance teams, … networking teams or traditional database and ops teams. … For example, database or firewall changes … are often not tied to development team's responsibility. … When interactions required with the enterprise … for release to go live are missing … from the delivery pipeline, it becomes … more likely that we will find unexpected dependencies …
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.