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

Questions

Test your knowledge of the concepts in this chapter by answering these questions.

  1. Which of these are types of enablers in SAFe (pick two)?
    1. Exploration
    2. Measurement
    3. Visualization
    4. Compliance
    5. Actual
  2. Which feature of a Kanban board can be used to visualize work that is urgent?
    1. WIP limits
    2. An expedite lane
    3. Column policy
    4. Expanded workflow columns
  3. What is a consequence of too much WIP?
    1. Too much multitasking
    2. Reduced cycle times
    3. Newer work gets started after older work is completed
    4. Short queues
  4. What results from large batch sizes?
    1. Low WIP
    2. Decreased risk
    3. High cycle times
    4. High performance
  5. According to Reinertsen, long queues lead to which problems (pick two)?
    1. Shorter cycle times
    2. Higher overhead
    3. Less risk
    4. Higher quality
    5. More variability
  6. Which of these is a method for managing variability?
    1. Larger batch sizes
    2. Establishing buffers
    3. One-off” processes
    4. Increasing WIP
  7. According to Mik Kersten, which of these is present in product-based development?
    1. Moving the people to the...