Your teams have implemented an Agile framework and 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.”
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
Download “The on-ramp to Scaled Agile Framework (SAFe)”
Excerpt from “The on-ramp to Scaled Agile Framework (SAFe)”: 3 must-have elements for starting your SAFe journey
1. SAFe training for all team members
Although based on existing Scrum and Agile principles, the SAFe framework does introduce different terms and concepts as it takes on the charter of implementing an organization-wide Agile movement.
2. Selection of a SAFe configuration, definition of ARTs, and identification of product management/leadership teams
This is where the rubber begins to meet the road in terms of SAFe principles being applied to your organization. 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.
3. Build a plan for the first PI planning session
Program Increment planning is an important event, usually two days long, in which all teams in an ART come together to look at their shared goals and plan to deliver those goals in the next Program Increment. The organization must already have defined the length of their PI and determined whether the release dates of the PI would be aligned to enterprise release dates.
Download the eBook to read all the details in each section, plus additional information on Scaled Agile Framework.
Authors
-
Your additional text goes here
-
