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

More Teams, More Application Products

When we are ready to unleash that infectious enthusiasm and enable more Application Product Teams to work in the same mode as the first one has, what does that look like?

We've seen throughout this book how a team built its own foundation—cultural foundation, enabled by leadership, and a technical foundation. We've seen how that team journeyed around the Discovery Loop through the Options Pivot and onto the Delivery Loop, and based on learning either looped around Delivery again, returned to the Discovery Loop, or returned to the Options Pivot. This journey continues forever.

This is what five Application Product Teams' approaches would look like, as seen in Figure 18.6. Each of them is an autonomous team with mastery and purpose, focused on their individual product (or product area if they're delivering into a larger product). So, they each have their own Mobius Loop to journey around. They each have their own...