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

Creating a Delivery Map

We concluded Section 3, Discover It, with a Discovery Map, with a single information radiator that summarized the Discovery Loop iteration. We concluded Section 4, Prioritize It, with an Options Map, which summarized the ideas and hypotheses we wanted to validate, how we would deliver the options, and what options we planned to work on first.

We will conclude Section 5, Deliver It, with a Delivery Map. This is another open source artifact available in the Mobius Kit under Creative Commons that you can use to summarize all the learnings and decisions taken during your journey around the Delivery Loop.

This map should slot neatly next to your Discovery Map and is used to summarize the following:

  • Actions: What can we get done this week to improve the outcomes?
  • Doing: What is our current work in progress?
  • Done: What is ready to review?
  • Impact: What progress did we make toward the outcomes?
  • Learn: What did we learn?
  • Insights: What...