프롬프트 도감 › No.2073
SAFe 개발 팀 상황 설명
SAFe Delivery Context
큰 목표, 기능, 작은 작업의 3단계 구조를 AI에게 알려 줘요. 이후 답변이 이 구조와 SAFe 방식에 맞게 나와요.
이럴 때 개발 일정 계획, 작업 쪼개기, 팀 회의 자료 정리
도구 ChatGPT · Claude · Gemini
프롬프트
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.
팁
- 팀 수와 기간을 내 상황에 맞게 고쳐요
- 첫 대화에 넣고 뒤에 질문을 이어가요
출처
권리: CC0 (f/prompts.chat). 자유 사용. 기여자: YejiaTong.