At the summit of the DevOps journey is the ability for teams to deliver more frequently to be more responsive to their business. This requires that teams understand their delivery value stream bottlenecks and architect their integrated delivery pipeline for speed of delivery.
At the summit of the DevOps journey is the ability for teams to deliver more frequently to be more responsive to their business. This requires that teams, first, understand their delivery value stream including blockers and wait states, to determine what can enable them to deliver more quickly. In order to do this, teams must be given visibility and metrics (e.g. lead time) in order to understand what their constraints are. In addition, the underlying delivery pipeline used by teams must be integrated and architected for speed of delivery.
My experience at companies like Bell Labs and Nationwide through Agile, Lean and now DevOps has taught that in order for an enterprise to apply DevOps concepts at scale and accelerate delivery for the business, it is necessary to create a structure and culture that both allows teams to own their journey and identify areas where they can improve while also applying Systems Thinking which can take these ideas and determine how they can be applied to optimize the enterprise delivery value stream. It also requires treating the delivery pipeline as a product which needs to be architected for speed of delivery. This presentation will describe how this has been done, what we have learned and the challenges that lay ahead of us.
Could be in CI/CD or Culture since both apply. Based on the track, I can tailor the talk.
I am located in the Eastern US time zone.