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

What Is an Outcome?

As described in Section 1, Practices Make Perfect, the Mobius Loop encourages an iterative, experimental approach to achieving outcomes through a continuous flow of innovation using continuous discovery and continuous delivery. An outcome is a result that occurs from doing something. In our case, the outcome is a change in human behavior that drives change in the culture, impacting long-term business results.

The Target Outcomes practice helps teams discover, write, align on, and share the desired behavioral change they would like to see achieved by application products. Sharing Target Outcomes helps the team deliver measurable results and align with stakeholders and team members. Referring to Target Outcomes can help prioritize and filter work so that we are always focused on delivering measurable impact.

The Target Outcomes practice involves creating a canvas that summarizes anticipated and hopeful measurable change captured by the team and stakeholders...