Scaled Agile Framework:  Rahmenwerk für agile Skalierung

SAFe provides a coherent framework for agility at scale.

• SAFe connects the most important agile frameworks (such as Scrum, Kanban, Design Thinking, Lean Startup, etc.) with each other to form an overall system. This allows you to use the different agile frameworks together.

• Using SAFe's patterns, you can quickly create a picture of an agile organization - for a program, for an area, or for an entire organization.

• All levels of an agile organization (team, multiple teams or the Agile Release Train (ART), the Large Solution level and the Portfolio level are consistently thought through and documented.

• SAFe contains many well-documented techniques, roles, meetings, and artifacts.

• SAFe uses familiar terms that make it easier for organizations to make the transition while still being designed in an agile way.
  

Agile organized collaboration

The Scaled Agile Framework's solution for multi-team collaboration is to "pull in" a cycle at a higher level of abstraction: planning interval. This solution addresses the complexity of large programs, in which

• Requirements are handled at different levels of abstraction;

• meetings - similar to Scrum - can also be used at higher levels;

• Planning is implemented at the various levels with interlocking backlogs.

Thus, SAFe provides clear guidance on how to implement agile at scale and with multiple teams.

Coordinated cycles for a common result

Agile teams working on a common solution ("Solution") proceed in iterations. These have a common beat so that teams can synchronize their work and deliver a common result together. Around these iterations there is the larger takt, the Planning Interval (PI). This takt is a multiple of the team-level iterations. For example, if the team iterations are 3 weeks long, the Planning Interval could be 12 weeks. Thus, 4 iterations on team level run in one Planning Interval.

The Planning Interval has - analogous to the iteration or sprint of a team - a PDCA cycle (Plan-Do-Check-Act) on a higher level of abstraction:

• PI Planning: This is the joint planning of several teams on the level of "larger" requirements ("features") for the next planning interval of 8-12 weeks. Such a planning interval consists of several sprints/iterations.

• ART Backlog Refinements: During the Planning Interval (PI), the ART Backlog is jointly maintained. ART stands for Agile Release Train, the group of teams that are coordinated together during the interval. The ART Backlog is like the Team Backlog, only one abstraction level higher. It contains features.

• System Demo: Here, the common solution created by all teams together is tested. This happens in every iteration, but of course also at the end of a planning interval.

• Inspect & Adapt Workshop: Here, all teams look together at how the work worked in the last PI and how it can be improved together. This is the joint retrospective of several teams, so to speak.