OS2.0 SAFe Delivery Context (Master)
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.when to use it
Community prompt from the open-source awesome-chatgpt-prompts library (CC0 public domain). A proven "OS2.0 SAFe Delivery Context (Master)" starting point — swap in your own specifics and constraints. Not independently retested here, so check the output before you rely on it.
tags
businesscommunitygeneral
source
awesome-chatgpt-prompts · CC0 1.0 (public domain)