Book Image

DevOps Culture and Practice with OpenShift

By : Tim Beattie, Mike Hepburn, Noel O'Connor, Donal Spring, Ilaria Doria
Book Image

DevOps Culture and Practice with OpenShift

By: Tim Beattie, Mike Hepburn, Noel O'Connor, Donal Spring, Ilaria Doria

Overview of this book

DevOps Culture and Practice with OpenShift features many different real-world practices - some people-related, some process-related, some technology-related - to facilitate successful DevOps, and in turn OpenShift, adoption within your organization. It introduces many DevOps concepts and tools to connect culture and practice through a continuous loop of discovery, pivots, and delivery underpinned by a foundation of collaboration and software engineering. Containers and container-centric application lifecycle management are now an industry standard, and OpenShift has a leading position in a flourishing market of enterprise Kubernetes-based product offerings. DevOps Culture and Practice with OpenShift provides a roadmap for building empowered product teams within your organization. This guide brings together lean, agile, design thinking, DevOps, culture, facilitation, and hands-on technical enablement all in one book. Through a combination of real-world stories, a practical case study, facilitation guides, and technical implementation details, DevOps Culture and Practice with OpenShift provides tools and techniques to build a DevOps culture within your organization on Red Hat's OpenShift Container Platform.
Table of Contents (30 chapters)
Free Chapter
2
Section 1: Practices Make Perfect
6
Section 2: Establishing the Foundation
11
Section 3: Discover It
15
Section 4: Prioritize It
17
Section 5: Deliver It
20
Section 6: Build It, Run It, Own It
24
Section 7: Improve It, Sustain It
27
Index
Appendix B – Additional Learning Resources

Where to Measure and Learn

In Chapter 10, Setting Outcomes, we introduced the practice of setting Target Outcomes based on all of the learning that came out of the practices on the Discovery Loop. We showed how to make these measurable and how to visualize them as an information radiator so everyone can inspect them. Using metrics, we can inspect where we are now in quantifiable terms, where we've been, and where we want to get to for each measurable outcome.

We explained the difference between primary (business-focused) outcomes and supporting enabling outcomes, which are non-functional-based outcomes. Since then, we have organized all of our work around those Target Outcomes and have radiated them in other practice artifacts, including the Value Slice on the Options Pivot and Scrum boards in the Delivery Loop. Those outcomes should be our starting point for measurement, and re-visualizing them will allow us to measure the progress we have made (or not) toward the target value...