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

Conclusion

In this chapter, we progressed from the Discovery Loop and Options Pivot and focused on how we deliver features into products using practices on the Delivery Loop. We explored different domains of delivery using the Cynefin framework and saw how Waterfall remains effective for work in the clear domain, whereas Agile is more suitable for work in the complex and complicated domains.

We explored where Agile came from, the Agile Manifesto, and took a detailed look into Scrum and Kanban methods, the practices they use, as well as supporting practices such as the Definition of Ready and the Definition of Done.

Figure 12.31: Adding Delivery Loop practices and more practices to the Foundation to support delivery

We can now see how Agile frameworks and practices help achieve continuous delivery when using platforms such as OpenShift and, when coupled with high-performing teams and an autonomous culture, we can deliver outcomes that matter earlier...