Book Image

SAFe® for DevOps Practitioners

By : Robert Wen
Book Image

SAFe® for DevOps Practitioners

By: Robert Wen

Overview of this book

Product development and release faces overlapping challenges due to the combined pressure of delivering high-quality products in shorter time-to-market cycles, along with maintaining proper operation and ensuring security in a complex high-tech environment. This calls for new ways of overcoming these challenges from design to development, to release, and beyond. SAFe® for DevOps Practitioners helps you use a DevOps approach with the Scaled Agile Framework and details how value streams help you resolve these challenges using examples and use cases. The book begins by explaining how the CALMR approach makes DevOps effective in resolving product development roadblocks. Next, you’ll learn to apply value stream management to establish a value stream that enables product development flow, measure its effectiveness through appropriate feedback loops, and find ways of improving it. Finally, you’ll get to grips with implementing a continuous delivery pipeline that optimizes the value stream through four phases during release on demand. This book complements the latest SAFe DevOps courses, and you’ll find it useful while studying for the SAFe DevOps Practitioner (SDP) certification. By the end of this DevOps book, you’ll have gained a clear understanding of how to achieve continuous execution and release on demand using DevOps and SAFe.
Table of Contents (21 chapters)
Free Chapter
2
Part 1 Approach – A Look at DevOps and SAFe® through CALMR
8
Part 2:Implement – Moving Toward Value Streams
12
Part 3:Optimize – Enabling a Continuous Delivery Pipeline

Summary

In this chapter, we started our examination of the Culture, Automation, Lean Flow, Measurement, and Recovery (CALMR) approach by looking at the first and most important factor: culture. We examined the work of Ron Westrum, which talked about three types of organizational cultures: pathological, bureaucratic, and generative. After looking at the characteristics of each of these cultures, we found that the one that really empowered our teams was a generative culture.

Once we settled on the ideal organizational culture, we then looked at how to move to that ideal culture. To help on this journey, we looked at the eight steps of the Change model created by John Kotter. We also saw these steps in action with examples from Ford Motor Company under Alan Mulally.

We identified the mindset that drives the behaviors we want to exhibit in our generative culture. The sources of this mindset come from both bodies of knowledge regarding Lean thinking the Agile Manifesto, and the SAFe...