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

11. The Options Pivot

During the Discovery Loop, we started to come up with lots of ideas for implementation. The Impact Map gave us deliverables that formed hypothesis statements. The human-centered design and Empathy Mapping practices gave us ideas directly from the user. The Event Storm gave us standalone features (triggered by commands) that can be implemented using standalone microservices (codifying the aggregate). The Metrics-Based Process Map and Non-Functional Map gave us ideas on how we can speed up the development cycle and improve security, maintainability, operability, scalability, auditability, traceability, reusability, and just about anything else that ends with ability!

The next step after the Discovery Loop is the Options Pivot, where all the information from these practices that we've used gets boiled down to a list of options for actions to take and decisions to make on what to deliver next.

The Options Pivot is the heart of the Mobius Loop. On...