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

Bolster the Foundations

This is where we do not do a copy and paste of that first team's foundation. Teams need to build their own foundations. They also need to regularly nurture and bolster their own foundations. And where they are connected by culture and technology, they all need to contribute to their connected underlying foundation.

When we introduced the Open Practice Library in Chapter 2, Introducing DevOps and Some Tools, we explained that this is a community-driven repository of tools. Throughout the book, we've pulled out around 50 of our favorite tools in the Open Practice Library toolbox and explained how we use them together to deliver metrics-based outcomes that matter.

These are not necessarily the practices that every team should use. Just because a set of practices works so well for one team does not mean they will work equally well for every subsequent team. Practices used to build the foundation and navigate around the Mobius Loop need to emerge...