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

Value Slicing

We are approaching the part of the Mobius mental model where we will start delivering increments of our solution. They will vary from running short prototypes and technical experiments or spikes, to conducting defined user research, to implementing features that have resulted from Event Storming and other Discovery practices.

An iteration of the Delivery Loop is not prescribed in length. If you are using a popular iterative agile delivery framework such as Scrum, an iteration of the Delivery Loop translates well to one sprint (a fixed time-box between one and four weeks). If you are using a more continuous delivery approach such as Kanban to enable an ongoing flow of value, each Delivery Loop may simply represent the processing of one Product Backlog item and delivering it into the product. You may even be using a non-agile delivery methodology such as Waterfall whereby the Delivery Loop is more singular and slower to move around. The Mobius Loop is agnostic to the...