TEXT

OS2.0 SAFe Delivery Context (Master)

Contributed by YejiaTong

Improved by Laravel Company · 2026-09-07

Improved prompt:

As a SAFe Agile Release Train Engineer (ART) leading a program consisting of four Agile development teams, I require your expertise in defining work items across the three hierarchical levels of our SAFe framework.

Our program operates on a quarterly Planning Interval (PI) cadence, following the PI Planning process to align teams with strategic objectives and coordinate dependencies between teams.

Work items are structured as follows:

  1. Epic: These are strategic initiatives that deliver significant business value or architectural transformations, often spanning multiple PIs. An Epic:

    • Represents a major business or technical objective
    • Can be further broken down into Features
    • Has a clear description of the expected business outcome
    • Typically requires alignment between multiple teams or stakeholders

  2. Feature: A Feature is a cohesive grouping of system functionality aligned to a specific business or architectural domain, designed to be delivered within a single PI. Features:

    • Contain one or more User Stories
    • Have a clear name that reflects the intended functionality
    • Include acceptance criteria
    • Describe the functional behavior of the system

  3. User Story: User Stories are the atomic, executable units of work representing the smallest meaningful product transformation. Each User Story:

    • Describes a single, testable piece of functionality
    • Can be executed manually, interactively, or automatically
    • Has a clear acceptance criteria
    • Is either marked as completed or cancelled during the PI

Your task is to provide examples of work items at each level, adhering strictly to the SAFe hierarchy:

  1. Begin with a high-level Epic that aligns with our program's strategic goals.
  2. Break down the Epic into meaningful Features that could realistically be delivered within a PI.
  3. Further decompose each Feature into a set of User Stories that are small, testable, and executable.

Ensure that the hierarchy is clear, the levels are distinctly separated, and the descriptions are specific enough to guide development teams. Avoid blurring the lines between strategic intent (Epic), functional capability (Feature), and execution detail (User Story).

Original prompt (before our improvements)

I serve as the Chief Solution / Release Train Architect working in a SAFe Agile delivery program. The program consists of 4 Agile delivery teams, operates on PI Planning, and delivers through Planning Intervals (PIs). Work items are structured into three hierarchical levels: Epic: Strategic initiatives delivering significant business or architectural value, which could span multiple PIs, and are broken into Features. Feature: Cohesive groupings of system functionality aligned to business or functional domains, typically deliverable within a PI. User Story: Atomic, executable units of work representing the smallest meaningful product transformation. Each user story is either completed or cancelled and has an execution mode: Manual, Interactive, or Automated. Responses should follow SAFe principles, respect this hierarchy, and maintain clear separation between strategic intent, functional capability, and execution detail.