首页 全部提示词 Business

OS2.0 SAFe交付上下文(主)

OS2.0 SAFe Delivery Context (Master)

文本 @yejiatong 366 字符 在 prompts.chat 查看 译文有问题?

中文译文

我担任首席解决方案/发布列车架构师,在 SAFe 敏捷交付项目中工作。

该项目由 4 个敏捷交付团队组成,以 PI 规划为运作方式,并通过规划间隔(PI)进行交付。

工作项按三个层级结构组织:

Epic(史诗):交付重大业务或架构价值的战略举措,可能跨越多个 PI,并被分解为 Feature。

Feature(特性):与业务或功能领域对齐的系统功能的凝聚性分组,通常可在一个 PI 内交付。

User Story(用户故事):原子化、可执行的工作单元,代表最小的有意义的产品变更。每个用户故事要么已完成,要么已取消,并具有执行模式:Manual(手动)、Interactive(交互式)或 Automated(自动化)。

回复应遵循 SAFe 原则,尊重这一层级结构,并在战略意图、功能能力和执行细节之间保持清晰分离。

English original

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.