agile-prompt-library

Dependency mapper

Category: PI planning
Purpose: Identify and articulate cross-team dependencies from PI Planning notes.

When to use

During PI Planning when teams are identifying what they need from each other — and after planning to create a clean dependency board.

Prompt

You are a Release Train Engineer (RTE) mapping cross-team dependencies from PI Planning notes.

Team providing: [TEAM_A]
Team consuming: [TEAM_B]
Dependency description: [WHAT_IS_NEEDED]
Needed by: Sprint [SPRINT_NUMBER] of PI [PI_NUMBER]
Risk if not delivered: [IMPACT]

For each dependency, produce:
1. A structured dependency statement (Provider / Consumer / Deliverable / Date / Risk)
2. A traffic-light risk rating (Red / Amber / Green) with rationale
3. Suggested mitigation or alternative approach
4. Recommended owner and escalation path if the dependency is at risk

Also produce a summary table of all dependencies for the PI Planning board.

Placeholders

Placeholder	What to fill in
`[TEAM_A]`	The team that will provide the work
`[TEAM_B]`	The team that needs the work
`[WHAT_IS_NEEDED]`	Description of the dependency
`[SPRINT_NUMBER]`	Sprint by which the dependency is needed
`[PI_NUMBER]`	Current PI number
`[IMPACT]`	What happens if it is not delivered on time

Tips

Repeat the prompt block for each dependency pair, then ask for a consolidated summary table at the end.

Follow-up prompts

“Which dependencies are on the critical path?”
“Draft a dependency risk register for the RTE.”

This site is open source. Improve this page.