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

Long Live the Team

From the outset of this book, we have promoted the importance of long-lived, cross-functional teams. In Chapter 1, Introduction – Start with Why, we led with how we want this book to help the I-shaped individual (specialists in one particular skill) to become more T-shaped (multi-functional knowledge and single skill depth), or even M-shaped (multi-functional knowledge and multiple depth skills).

Above, we explored some ways we can improve the technology. Those suggestions weren't really directly improving the tech. They were focused on the people using the technology and improving their abilities to use technology. How can we measure and learn the impact of improving team skills? What are some of the ways we can visualize this?

Visualizing the Transition from I to T to M

A practice we've been improving over recent years has been capturing, measuring, and visualizing skills in a team. When we form a new team, for example, when we...