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

Team Backlog preparation for PI Planning

Having a Team Backlog that is ready for PI Planning is important in that it allows the team to focus on dependencies, ensuring alignment with the Vision, architecture, and Roadmap. They have the time and space to collaborate with other teams, create plans with high confidence, and draft PI Objectives at the event.

Each team will be different in the amount of preparation needed for PI Planning. We have found success when the teams have identified and roughly estimated the stories for the next PI ahead of PI Planning. These stories (except those that will likely be worked on in the first iteration) aren’t well refined and wouldn’t meet the DoR.

You will want to ensure that your teams don’t go into PI Planning with a fully refined and planned backlog, knowing what stories will go into which iterations and then spend the event staring at each other. You may even find that they become overly attached to their plans and...