Scaled Agile Framework (SAFe) process template

Use this template when following the Scaled Agile Framework (SAFe) methodology. SAFe is characterized by a program team that steers incremental delivery of a system by multiple agile development teams.


The SAFe process template has one top-level Agile Release Train (ART) iteration, which consists of multiple Program Increment (PI) iterations. Each PI iteration is further broken down into multiple sprint iterations.


The SAFe process defines the following program level and team level user roles:
Table 1. SAFe process roles: Program level
Role Description
Product Manager Defines and prioritizes the program backlog, develops the vision and roadmap, works with product owners to optimize feature delivery to the customers, and sets PI Objectives. This person has content authority.
Business Analyst Defines initiatives (business epics) and determines the impact on the internal and external value streams of the enterprise.
UX Designer Works with stakeholders to understand the specific business targets of the user-system interaction. Responsibilities include UI design, UX guidelines, design elements, and the validation of user experience through user-experience testing.
System Architect Defines a technological vision and implementation scenarios with architectural epics that support the business strategy. This person maintains a high-level understanding of user needs, system requirements, and business benefits for a release train.
Release Train Engineer Facilitates the agile release train processes and program execution, escalates impediments, manages risk, and drives continuous, program-level improvement. This person also facilitates program events, such as release planning, inspect and adapt, and the scrum of scrums.
Business Owner Responsible for the value delivered by a specific ART. This person understands the strategic themes that influence the train, knows about the current business context, has decision-making influence on epics moving through the Kanban systems, is involved in driving or reviewing the program vision and road map, and has a significant role in release planning.
Table 2. SAFe process roles: Team level
Role Description
Product Owner Defines and prioritizes the requirements backlog, helps to elaborate those requirements with the team, and accepts completed stories into the baseline. A team has only one product owner, who might be dedicated to one or two teams.
Scrum Master Facilitates team interactions and meetings, enforces the rules in a scrum, and helps drive the team's efforts to continuously improve. A team member or a scrum master might have a full- or part-time role that is shared across two or three teams.
Team Member Usually a developer or tester, but this role might include other roles as well, such as a technical lead, a system architect, or a technical writer. A team normally has five to nine members.

Work item types

The SAFe process defines the following work item types:

Project area initialization

When you create and initialize a project area based on the SAFe process template, a work item with the Summary of Post-Project Initialization Tasks is created. The Description in the new work item describes tasks that the program manager or release train engineer should perform to get started working in the new project area.

Work item templates

Project areas that are based on the SAFe process template include the following templates that you can use to create work items:

Work item calculated values script

Project areas that are based on the SAFe process template include the Weighted Shortest Job First (WSJF) calculated values script, which you can use to customize work item attributes. For details about the WSJF algorithm, see . For details about using calculated values scripts, see Configuring calculated value attribute customizations.

For additional details about the SAFe process template, navigate to the Templates tab in the web client. Click the Edit Process Description (Edit Process Description icon) icon in the Actions column for SAFe Process (Program) Template. For guidance on working on a team that uses the SAFe process, see Scaled Agile Framework.

video icon Watch videos

CLM playlist channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog