Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SAFe® for DevOps Practitioners

You're reading from   SAFe® for DevOps Practitioners Implement robust, secure, and scaled Agile solutions with the Continuous Delivery Pipeline

Arrow left icon
Product type Paperback
Published in Dec 2022
Publisher Packt
ISBN-13 9781803231426
Length 330 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Robert Wen Robert Wen
Author Profile Icon Robert Wen
Robert Wen
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Chapter 1: Introducing SAFe® and DevOps 2. Part 1 Approach – A Look at DevOps and SAFe® through CALMR FREE CHAPTER
3. Chapter 2: Culture of Shared Responsibility 4. Chapter 3: Automation for Efficiency and Quality 5. Chapter 4: Leveraging Lean Flow to Keep the Work Moving 6. Chapter 5: Measuring the Process and Solution 7. Chapter 6: Recovering from Production Failures 8. Part 2:Implement – Moving Toward Value Streams
9. Chapter 7: Mapping Your Value Streams 10. Chapter 8: Measuring Value Stream Performance 11. Chapter 9: Moving to the Future with Continuous Learning 12. Part 3:Optimize – Enabling a Continuous Delivery Pipeline
13. Chapter 10: Continuous Exploration and Finding New Features 14. Chapter 11: Continuous Integration of Solution Development 15. Chapter 12: Continuous Deployment to Production 16. Chapter 13: Releasing on Demand to Realize Value 17. Chapter 14: Avoiding Pitfalls and Diving into the Future 18. Assessment Answers 19. Index 20. Other Books You May Enjoy

Summary

In this chapter, we looked at Lean flow as part of the CALMR model. We know that achieving a Lean flow of work where the progression of work is steady and teams are neither overburdened nor underburdened allows for the success of the other parts of the model. To that end, we took a close look at Lean practices that allow teams to achieve Lean flow.

The first practice we investigated was to make sure that all the work a team commits to and its progress are visible. To ensure this visibility, we looked at the types of work a team could do. We then mapped that work to a Kanban board, highlighting the features of the board that allow us to see the progress for any one piece of work and where urgent work could go. We saw how we can visualize WIP on the Kanban board and how to keep WIP in check using WIP limits.

From there, we took a look at the size of the work or batch size. We strove to understand the importance of making sure the batch size was as small as possible. We...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime