Define an epic in SAFe

  • Release version: Zurich
  • Updated July 31, 2025
  • 4 minutes to read

    • Create an epic within SAFe. An epic is the largest unit of work that has one common objective such customer request, or business requirement. An epic is further decomposed into features for implementation and delivery by SAFe agile release trains (ARTs).

    Before you begin

    Role required: safe_art_user or safe_admin

    Procedure

    1. Create an epic using either of the following options.
      OptionSteps
      From the Backlog tab
      1. Navigate to Scaled Agile Framework (SAFe).
      2. From the list, select the ART level.
      3. From the adjacent list, select the required ART value.
      4. Select the Backlog tab.
      5. From the Create list, select Create Epic. The epic is displayed in the Backlog tab with the state as Backlog.
      From the Epics module
      1. Navigate to Scaled Agile Framework (SAFe) > Epics.
      2. Click New. The epic is displayed in the Epics list and Backlog tab with the state as Funnel.
      From the Portfolios module
      1. Navigate to Scaled Agile Framework (SAFe) > Portfolios.
      2. In the SAFe epics related list, click New.
    2. In the form, fill in the fields:
      Table 1. SAFe Epic Form
      Field Description
      Number System-generated number for the epic.
      Enabler Check box identifying the epic as an enabler. Enablers do not add direct business value but help lay a foundation for future work. For example, an enabler epic might be an investigation into the architecture used to build features.
      State State of the epic:
      • Funnel: Created from Scaled Agile Framework (SAFe) > Epic.
      • Review: Under review considering parameters like WSJF score and WIP limited.
      • Analysis: Approved or rejected based on parameters like WSJF score refinement, cost estimation, alternatives, and WIP limited.
      • Backlog: Approved and assigned to an ART. In this state, the ART level user segments the epic into features.
      • Implementation: Epic is being implemented.
      • Done: Implementation is complete.
      Color Color that you attribute to the epic. Epic colours help you visually identify and group features by their epic on the ART's backlog page of the SAFe board.
      WSJF Score Weighted Shortest Job First (WSJF) score is used to prioritize and sequence jobs to produce optimum business value. A job with the highest WSJF score receives the highest priority for implementation. A job can refer to an epic, feature, or any business capability.
      Short description Brief description of the epic.
      Description A more detailed description of the epic.
      Table 2. Weighted shortest job first score section of the Epic form
      Field Description
      User-business Value Business value of the job based on parameters like impact on revenue or other solutions in the market offering similar capabilities.
      Time criticality Impact on the business when deadlines are missed. For example, how projected revenue gains are reduced over time when deadlines are shifted.
      Risk reduction Analyze how much risk this epic can help you avoid by answering questions such as:
      • Does the job add value to the business in other ways?
      • Does the job bring in new business opportunities?
      • Does the job reduce the risk for a future delivery?
      Job size Estimated duration for completion of the job.
      Total story count Number of active stories in the epic.

      This field is not displayed by default. Configure the field in the form layout.
      Completed count Number of stories that have been completed in the epic.

      This field is not displayed by default. Configure the field in the form layout.
      Percent complete by count Percentage of work that has been completed in the epic. Value is calculated by story count.

      This field is not displayed by default. Configure the field in the form layout.
      Total estimate Sum of estimates of all the active stories in the epic.

      This field is not displayed by default. Configure the field in the form layout.
      Completed estimate Sum of estimates of all the completed stories in the epic.

      This field is not displayed by default. Configure the field in the form layout.
      Percent complete by estimate Percentage of work that has been completed in the epic. Value is calculated by points (estimate) of stories in the epic.

      This field is not displayed by default. Configure the field in the form layout.
      Missing estimates Number of stories without estimation points.

      This field is not displayed by default. Configure the field in the form layout.
      Top program Program mapped to the SAFe work enabling top-down hybrid planning. All the active child SAFe features of this epic are automatically associated with the selected program.

      This field is visible in the SAFe view of the epic form if you activate the PPM Standard plugin (com.snc.financial_planning_pmo).
    3. Fill in the Planning section if you want to create benefit plans for the epic.
      This section is available when the Benefit view is selected.
      Table 3. Planning section of the Epic form
      Field Description
      Planned start date Projected start date for the epic. The planned start date can be the current date or a future date.
      Planned end date Projected end date for the epic. The planned end date must be after the planned start date.
      Planned benefit Benefit value that is rolled up from the benefit breakdown.
      Actual start date Actual start date for the epic. The actual start date can be on or before the planned start date.
      Actual end date Actual end date for the epic. The actual end date can be before the planned start date but not before the actual start date.
      Actual benefit Actual benefit value that is rolled up from the actual benefit in the benefit breakdown.
    4. Click Submit.