SAFe 프레임워크에 맞춘 OS2.0 프로젝트 납품 맥락과 기준을 안내합니다.
원제 · 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.
출처 · prompts.chat 공개 프롬프트 모음 · 작성 Noah Y. Tong — CC0(저작권 포기)로 공개된 원문을 그대로 싣습니다. 한국어 제목 · 설명은 AI 번역이며, 실행 결과는 아직 없습니다.