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 artifacts

There are several key artifacts that we wanted to make sure we didn’t overlook. You may have others that you regularly incorporate into your teams as well; just keep in mind the Agile Manifesto Value in that we find Working Systems to be more important than Comprehensive Documentation.

Definition of Done

The Definition of Done (DoD) is the team’s checklist to ensure that the work can be considered complete. Team DoDs evolve over the life of the team and often with the maturity of the Continuous Delivery Pipeline.

We encourage the team to regularly review the DoD (the Retrospective is a prime opportunity) and ensure that the DoD is accessible, visible, and used by the team for the stories they complete.

Pro tip

Too often I see new teams have a DoD that includes something to the effect that the story is deployed to production. This leads to teams ignoring the DoD and subsequently, we see quality issues creep into the system. Leverage the Scalable...