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

DevOps topologies

With the growing list of tools and technologies available to Dev and Ops, it may be difficult to figure out where the responsibilities lie in moving toward a DevOps approach. Who is responsible for creating the CI/CD pipeline? What do we consider databases? How do we deploy into production?

In 2013, Matthew Skelton initially described three team anti-types to avoid and five possible team structures. Additional contributions have increased the number of anti-types to eight and the number of beneficial team structures to nine. The following list shows the anti-types and they are elaborated here at https://web.devopstopologies.com:

  • Dev and Ops Silos
  • Permanent DevOps Team Silo
  • Dev Doesn’t Need Ops
  • DevOps as the Dev Tools Team
  • Rebranded Sysadmins
  • Ops Embedded in Dev Team
  • Dev and DBA Silos
  • Fake SRE

The 9 DevOps topologies from that site are as follows.

Dev and Ops collaboration

This structure is considered the ideal...