Scaled Agile Framework (SAFe) 5.0 Full process template

The Scaled Agile Framework (SAFe) methodology is an industry standard framework for helping organizations scale agile and lean practices to an enterprise level. Use this template to establish a Portfolio tooling environment with the Large Solution layer for the Full SAFe 5.0 configuration. This environment is associated with one or more Essential SAFe Program or Team tooling environments.


The template assumes a single cadence for all Solutions that are associated with Value Streams. This implies a single Portfolio Roadmap.

The template creates a category for the Portfolio, and categories for two Large Solution/Value Stream teams. Add or remove Large Solutions, Value Streams, and categories as required for your Portfolio.


Table 1. SAFe 5.0 Full process roles: Portfolio level
Role Description
Portfolio Manager Leads the Portfolio Management Team, moving large programs from development to deployment and providing status and financial reporting.
Business Analyst Defines initiatives (business epics) and determines the impact on the internal and external value streams of the enterprise. SAFe refers to business analysts as Epic Owners.
IT Director The executive in charge of the portfolio.
Stakeholder A member of the portfolio management team that contributes to the generation of new ideas into the system.
Enterprise Architect Defines a technological vision and implementation scenarios that support the business strategy. This role typically articulates Architectural Epics and works with Program-level System Architects.
Table 2. SAFe 5.0 Full process roles: Solution level
Role Description
Systems Engineer The Systems Engineer is similar to a Business Analyst but is focused on defining the vision and behavior for the overall system. That system might include hardware, embedded software, and related components.
Solution Train Engineer Facilitates solution processes and execution; escalates impediments; manages risk; and helps ensure value delivery and continuous improvement.
Solution Architect Responsible for the overall architectural and engineering design of the solution; aligns the Solution Train and the Agile Release Trains to a common technological and architectural vision.
Solution Manager Responsible for development and prioritization of the Solution Backlog. Works with stakeholders to understand their needs; creates the vision and roadmap; defines requirements; and guides work through the Solution Kanban.
Table 3. SAFe 5.0 Full process roles: Program level
Role Description
Program Lead The role defined in a portfolio to allow the Product Manager, Release Train Engineer, and Business Owner roles in a Program to participate in Portfolio Planning.

Work item types

The SAFe 5.0 Full process defines the following work item types:
  • Portfolio Epic: Portfolio Epics are enterprise initiatives that affect multiple organizations and program increments. A Portfolio Epic affects multiple release trains.
  • Solution Epic: Solution Epics are initiatives that are large enough to warrant analysis and a Lean Business Case but are constrained to a single Solution (Value Stream).
  • Capability: Capabilities are similar to features, but account for higher-level behaviors of the solution. They often span multiple Agile Release Trains (ARTs). They are maintained in the value stream backlog and are sized to fit in a Program Increment (PI), so that each PI delivers solution value.
  • Milestone: Learning milestones mark specific progress points on the timeline and can be invaluable in measuring and monitoring the progress and risk of a program.
  • PI Objective: Describes a specific goal with planned and assessed business value for Capabilities, Features or Stories delivered in a specified Program Increment or Iteration. The PI Objective can be at the program, team, or value stream level.
  • Task: Defines a unit of work planned for a program increment and is estimated in hours.
  • Defect: Defines a bug, error, or flaw in the solution.
  • Risk: A risk is a potential event or future situation that could affect, prevent, or limit a project's success. Project risks might be seen as threats or opportunities.
  • Retrospective: A Retrospective is an event to discuss what went well and what did not go well, and to define improvement for the upcoming period. Use a Retrospective work item type to ensure that this event occurs and to track the team's comments and plans.

Project area initialization

When you create and initialize a project area based on the SAFe 5.0 Full process template, a work item with the Summary of Post-Project Initialization is created. The Description in the new work item includes a link to a web page that describes how to configure your project area.

Work item templates

Project areas that are based on the SAFe 5.0 Full process template include the following templates that you can use to create work items:
  • Portfolio Management: Use this work item template to create typical SAFe portfolio management tasks.
  • Solution Increment: Use this work item template at the start of each Solution Increment to create work items for typical events.
  • Solution Release: Use this work item template to create typical SAFe Solution Release tasks.
  • Solution Initiation: Use this work item template when initiating a new solution.

Work item calculated values script

Project areas that are based on the SAFe 5.0 Full process template include the Weighted Shortest Job First (WSJF) calculated values script, which is used to calculate the WSJF attribute value in Portfolio Epics, Value Stream Epics and Capabilities. The template also includes Calculated Achieved Value and Exposure Provider calculated value scripts. For details about using calculated values scripts, see Configuring calculated value attribute customizations.

For additional details about the SAFe 5.0 Full 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 5.0 Full Template. For guidance on working on a team that uses the SAFe process, see Scaled Agile Framework.