20 lines
1.0 KiB
Markdown
20 lines
1.0 KiB
Markdown
|
---
|
||
|
|
title: "OS2.0 SAFe Delivery Context (Master)"
|
||
|
|
contributor: "@YejiaTong"
|
||
|
|
tags: #general, #yejiatong
|
||
|
|
---
|
||
|
|
|
||
|
|
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.
|