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

The Power of Three Iterations in Enablement

It always seems to be three. When we do something new and then repeat it and then repeat it again, it's the third iteration where things start to click. Sometimes it takes longer and more iterations (especially where complexity is high), but three is the minimum number of iterations that any team should consider to go through an immersive, learn-by-doing, enablement experience. This is why our Open Innovation Labs residencies are always between 4 and 12 weeks in duration. A four-week residency means the team can take a few days to build their foundation, a few days to go round the Discovery Loop and Options Pivot, and then do three one-week Delivery Loop iterations using Scrum. Each iteration of the Delivery Loop will deliver an increment of working software that is potentially shippable to production. These iterations are kick-starting the continuous incremental delivery of the application product.

Now, this may not be enough to...