So your teams have implemented an Agile framework and now you’re ready to take things to the next level—to start scaling up. If you’ve decided to go with Scaled Agile Framework (SAFe) but are feeling a little overwhelmed, you may be wondering if you’re ready to make the leap. That’s why we created “The on-ramp to Scaled Agile Framework (SAFe): 3 must-haves for starting your journey.”

Download “The on-ramp to Scaled Agile Framework (SAFe)”

You’ll learn:

• Why teams must be firmly rooted in the Agile framework before scaling up

• Why SAFe-specific training is imperative, starting with leadership

• The first step in defining Agile release trains (ARTs)

• Key leadership roles that must be defined

• How to prepare for your first Program Increment (PI) planning session

Excerpt from “The on-ramp to Scaled Agile Framework (SAFe)”

A lot of companies falter in adopting SAFe because they get confused about which SAFe configuration (Essential, Large Solution, Portfolio, or Full) to follow. SAFe provides guidelines on which configurations are best suited to which kinds of organizations. Identifying the right configuration is imperative, but no matter the choice, organizations should remember that the “Essential SAFe” guidelines need to be followed, as they form the basic component of all four configurations. As an example, if a company is conducting solution-level Program Increment (PI) planning, it must not forget to include ART (Agile release train)-level PI planning, which is imperative for enabling teams to view, change, and ultimately commit to a multi-sprint plan.

Like what you see?