Prompts to accelerate PI Planning preparation and output — from PI Objectives to dependency maps, risk summaries, and ART Sync facilitation.
Use when: You have team inputs and need to draft SMART PI Objectives before or during PI Planning.
You are a Release Train Engineer (RTE) or Scrum Master drafting PI Objectives.
CONTEXT:
- Team: [team name]
- PI number: [e.g., PI 5]
- PI dates: [start date] to [end date]
- Strategic themes for this PI: [paste from Business Owners or RTE]
- Team's planned features / epics for this PI: [list]
- Known dependencies: [list cross-team or external dependencies]
- Team capacity notes: [any known absences, reduced sprints]
TASK:
Draft 4–6 PI Objectives for this team.
Requirements:
- Mix of committed (high confidence) and stretch (aspirational) objectives
- Each objective should be outcome-oriented, not task-oriented
- Each should connect to at least one strategic theme
- Flag which are committed vs. stretch
FORMAT:
For each objective:
- Objective statement (clear, one sentence)
- Type: Committed / Stretch
- Connected strategic theme
- Key features/stories that deliver this objective
- Business value score (1–10 — for Business Owner planning poker)
- Risks or dependencies
TONE: Professional, outcome-focused, suitable for Business Owner review.
Use when: You need to identify and articulate cross-team dependencies from team discussions or notes.
You are an RTE or Scrum Master mapping PI Planning dependencies.
CONTEXT:
- ART teams: [list all teams on the ART]
- Team providing this input: [team name]
- Planned features for this PI: [list]
- Known needs from other teams: [paste notes / discussion outputs]
- Known requests from other teams: [paste notes / discussion outputs]
TASK:
1. Identify all cross-team dependencies from the inputs provided
2. Classify each dependency (feature dependency, timing dependency, API/integration, shared resource)
3. Flag high-risk dependencies (late, unclear, or with no confirmed owner)
4. Suggest mitigation or conversation starters for high-risk dependencies
FORMAT:
- Dependency table:
| From Team | To Team | Dependency | Type | Sprint Needed | Status | Risk |
- High-risk dependency flags (bullet list with recommended action)
- Dependencies needing immediate RTE attention (if any)
TONE: Clear, factual. Suitable for the Program Board or ART Sync.
Use when: Teams have surfaced risks during PI Planning and you need a clean ROAM summary.
You are an RTE facilitating PI Planning risk management.
CONTEXT:
- PI: [PI number and dates]
- Raw risks identified by teams: [paste all risks raised]
- ART context: [brief description of the programme / product being built]
TASK:
1. Consolidate and deduplicate the risks
2. Apply the ROAM framework to each risk:
- Resolved: risk is no longer a concern
- Owned: someone has accepted the risk and will manage it
- Accepted: risk is understood and accepted by the team/ART
- Mitigated: action has been taken to reduce likelihood or impact
3. Flag any risks that require Business Owner or leadership attention
FORMAT:
- ROAM table:
| Risk | Category | ROAM Status | Owner | Mitigation/Notes |
- Risks needing leadership attention (brief bullet list)
- Overall risk posture summary (2–3 sentences)
TONE: Factual, actionable. Suitable for the PI Planning readout.
Use when: ART Sync is complete and you need a concise record of decisions and actions.
You are an RTE writing an ART Sync summary.
CONTEXT:
- ART Sync date: [date]
- PI: [PI number], Sprint: [sprint number]
- Teams represented: [list]
- Topics discussed: [paste agenda or discussion notes]
- Decisions made: [list]
- Actions agreed: [list with owners]
- Impediments raised: [list]
- Dependencies updated: [any changes to the Program Board]
TASK:
Write a concise ART Sync summary for distribution to ART teams and stakeholders.
FORMAT:
- ART Sync at a Glance (date, PI/sprint, attendance)
- Key Decisions (bullet list)
- Actions (table: action / owner / due date)
- Impediments (table: impediment / owner / status)
- Program Board Updates (brief description of any changes)
- Next ART Sync: [date]
TONE: Clear, brief, action-oriented. Suitable for a Teams post or Confluence page.
Use when: You’re the Scrum Master or RTE preparing the team for PI Planning.
You are a Scrum Master preparing your team for an upcoming PI Planning event.
CONTEXT:
- Team: [team name]
- PI Planning dates: [dates]
- PI Planning format: [in-person / hybrid / fully remote]
- Days until PI Planning: [number]
- Team's current backlog state: [brief description — refined / partially refined / needs work]
- Strategic themes or Vision shared so far: [yes/no and brief description]
TASK:
Generate a PI Planning preparation plan for this team covering the next [X] days.
Include:
1. Backlog readiness actions (what needs to be refined, estimated, or clarified)
2. Team capacity planning (who will attend, who is on leave, adjusted capacity)
3. Pre-reading and context to share with the team
4. Technical setup if remote/hybrid (Miro boards, virtual Program Board, breakout rooms)
5. Day-of facilitation checklist (what the Scrum Master should prepare / bring)
FORMAT:
- Preparation timeline (table: task / owner / due date / status)
- Backlog readiness checklist
- Remote/hybrid setup checklist (if applicable)
- Day-of Scrum Master checklist
TONE: Practical, actionable. Written for a Scrum Master to use directly.
Use when: You’re facilitating the PI confidence vote and want to capture discussion meaningfully.
You are an RTE facilitating the PI confidence vote at the end of PI Planning.
CONTEXT:
- PI: [PI number]
- Vote result: [e.g., "Average 3.8 out of 5 — 2 fists of five, 8 fours, 6 threes, 1 two"]
- Concerns raised during the vote: [paste comments from team members who raised concerns]
- Actions taken to address concerns before the final vote: [list]
- Final vote result after adjustments: [if a second vote was held]
TASK:
1. Summarise the confidence vote outcome for the PI Planning readout
2. Document the concerns raised and how they were addressed
3. Identify any unresolved concerns that carry into the PI as risks
FORMAT:
- Confidence vote summary (1 paragraph — suitable for Business Owner readout)
- Concerns and resolutions table (concern / raised by / resolution / status)
- Carry-forward risks (bullet list)
TONE: Transparent, professional. Suitable for Business Owner and leadership audience.
Use when: The PI is complete and you’re preparing inputs for the Inspect & Adapt (I&A) workshop.
You are a Release Train Engineer (RTE) or Scrum Master preparing for the Inspect & Adapt workshop at the end of a PI.
CONTEXT:
- PI: [PI number and dates]
- ART teams: [list teams]
- PI Objectives and outcomes:
[For each team: list their committed objectives and whether each was Met / Partially Met / Not Met]
- PI metrics:
- Planned velocity: [points]
- Actual velocity: [points]
- Predictability (Programme Predictability Measure): [%]
- Features completed: [number] of [number] planned
- Defects or quality metrics: [if available]
- Key events or disruptions this PI: [e.g., team changes, scope changes, dependency failures, external factors]
- Stakeholder feedback received during the PI: [brief notes]
TASK:
Produce a structured Inspect & Adapt input document covering:
1. PI Performance Summary — what the ART achieved vs. planned
2. Predictability analysis — what drove the gap (if any) between planned and actual
3. Top 3 ART-level impediments that affected delivery this PI
4. Top 3 things that went well (to protect and reinforce)
5. Draft problem statement for the I&A Problem-Solving Workshop — the single biggest systemic issue to address
FORMAT:
- PI Performance table (team / committed objectives / met / PPM score)
- Metrics summary (planned vs. actual: velocity, features, quality)
- Impediments table (impediment / impact / teams affected / resolved? Y/N)
- What went well (bullet list — 3 items with brief explanation)
- Draft Problem Statement (2–3 sentences: what is the problem, who is affected, what is the measurable impact)
TONE: Factual, balanced, focused on systemic improvement — not individual blame. Suitable for Business Owner and leadership audience.
Follow-up prompts: