Target Process for Full SAFe
Full SAFe
Full SAFe is the most extensive configuration and supports the development of very large and complex systems for which hundreds of people work together. At this level, the 5 core competencies of SAFe come together:
- Lean Agile Leadership
- Team and Technical Agility
- DevOps and Release On Demand
- Business Solutions and Lean Systems
- Lean Portfolio Management
Team
The team level contains the roles, activities, ceremonies and processes of Agile teams to deliver customer value in the context of an Agile Release Train (ART).
Program
Large Solution
The Large Solution level contains the roles, activities, methods, techniques and processes needed to develop large, complex systems.
Portfolio
The Portfolio level includes the roles, activities, methods, techniques, and processes needed to initiate and control a set of development Value Streams.
Full SAFe support in Targetprocess
Targetprocess supports the creation of iteration plans for teams by Scrum Masters. The Kanban board visualizes the status and progress of the team’s work. Using the Cumulative Flow Diagram (CFD) you have insight into the amount of work of the different Kanban stages. Scrum Masters can choose both Burn-down and Burn-up charts to see the team’s progress.
The Program level in Targetprocess supports the PI Planning for the Teams. A visual Program Board makes all the dependencies between the teams clearly visible to the RTE. The dashboard provides insight into the Program Predictability Measure. Features can be prioritized according to the WSJF method. The RTE can visually manage the cadance and milestones.
The Large Solution level in Targetprocess provides support to the STE for defining Solution Trains, ART’s and Teams. In the Capability backlog, the Capabilities are prioritized and the connection is made with Features. With the Priority Compliance report, Targetprocess shows whether the teams are working on the right priorities.
The portfolio level in Targetprocess provides support for defining Strategic Themes. This results in Epics being prioritized in the Epic backlog, while the Portfolio Kanban board displays the status and progress of the Epics. The Portfolio Dashboard gives an overview of the quality and progress both in its entirety and by team.
