Book Image

SAFe® Coaches Handbook

By : Darren Wilmshurst, Lindy Quick
Book Image

SAFe® Coaches Handbook

By: Darren Wilmshurst, Lindy Quick

Overview of this book

The Scaled Agile Framework (SAFe®) is widely recognized as an eff ective methodology for implementing Agile practices at the Enterprise level. However, the complexity of SAFe® can make it challenging for Teams and organizations to determine which practices can be safely adapted to their unique needs. Although SAFe® is a framework rather than a set of rules, promoting adaptation, it’s crucial to understand why SAFe® practices are designed the way they are along with the consequences of modifying them. The SAFe® Coaches Handbook is a comprehensive resource that goes beyond a how-to guide, providing a deep understanding of SAFe® principles and practices. The chapters are designed in a way to teach you how to successfully implement SAFe® in your organization and eff ectively manage the Team’s Backlog while avoiding common pitfalls. You’ll discover optimal ways to create SAFe® Teams and run successful Events. You’ll also learn how to plan Agile Release Trains (ARTs), manage the ART Backlog, conduct PI Planning, and grasp the importance of Value Stream Identifi cation in driving value delivery. By the end of this book, you’ll be armed with practical tips and advice to help you successfully customize the Scaled Agile Framework to your Enterprise’s needs while preserving the aspects that make it work successfully.
Table of Contents (26 chapters)
Free Chapter
2
Part 1: Agile Teams
7
Part 2: Agile Release Trains
13
Part 3: Portfolio
20
Chapter 17: Embracing Agility and Nurturing Transformation
21
Glossary
Appendix A

Why do we have different types of Stories?

We often get asked this question, or “why do I care if it is an Enabler Story, a User Story, or Technical Debt?” This simple answer is Capacity Allocation. Capacity Allocation is the allocation of work by the type of work. While we typically begin to think about Capacity Allocation for the ART Backlog, we want to understand how it impacts the Team Backlog as well.

By looking at the different types of stories in our Team Backlog (or Iteration Backlogs), we can ensure that we maintain a balance between delivering customer value and improving the system architecture.

If we are only focused on new functionality, then we might not be considering the long-term sustainability of the solution, which can lead to decreased velocity over time. Whereas if we are focused on delivering infrastructure, our customers may go elsewhere if they don’t get new Features and functionality.

Pro tip

As a Coach, when I first launch...