OS2.0 SAFe Delivery Context (Master)
Prompt from prompts.chat: OS2.0 SAFe Delivery Context (Master)
Prompt Content
Copy and paste directly into your model or internal evaluation tool.
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.
Use Cases
Reference Output
No standard answer available; manual review by scoring dimensions is recommended.
Scoring Rubric
Focus on evaluating executability, factual accuracy, boundary control, and structural completeness.
Try & save
Fill variables and copy, or save as a personal template.
This template has no variables and is ready to copy.
User Rating
0 ratingsYour rating
Log in to rate
Comments
0Log in to comment
Related Prompts
Dreamy Slow Shutter Fashion Portrait
Prompt from prompts.chat: Dreamy Slow Shutter Fashion Portrait
Shell Scripting taste
Prompt from prompts.chat: Shell Scripting taste
Web Performance taste
Prompt from prompts.chat: Web Performance taste