Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying SAFe® Coaches Handbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
SAFe® Coaches Handbook

SAFe® Coaches Handbook

By : Wilmshurst, Lindy Quick
5 (11)
close
close
SAFe® Coaches Handbook

SAFe® Coaches Handbook

5 (11)
By: 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)
close
close
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

The Team Backlog

The Team Backlog is an ordered list of all the possible work that an Agile Team can undertake to enhance or deliver the solution. It comprises User Stories, Enabler Stories, Improvement Stories, and all other work items. Unlike the Iteration Backlog, the Team Backlog represents a list of wants, allowing for flexibility and ownership by the team in determining the order and timelines for delivery. Although the PO is primarily responsible for the Team Backlog, any team member can contribute an item, help refine it, and prioritize it.

Three primary inputs contribute to the Team Backlog: the ART Backlog, team contributions, and requests from Stakeholders as depicted in Figure 4.1.

Figure 4.1 – Input sources for a Team Backlog (© Scaled Agile Inc.)

Figure 4.1 – Input sources for a Team Backlog (© Scaled Agile Inc.)

The ART Backlog serves as a crucial contributor as its Features are decomposed into User Stories and Enablers Stories for the Team Backlog.

The team also contributes to the Team...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY