Dependency register and map
Every “blocks” link between items, across teams, products and suppliers: requested until the other team agrees it, then agreed, met, or declined. Shown as a map with arrows and a register, with those at risk in red.
Why it matters
Work that waits on another team, product or supplier is where plans quietly fail. Agreeing each dependency, and seeing it, stops surprises.
- Owner
- Product Manager
Led or owned by
In the resource library
Ready-to-use resources in the DelPulse workspace (sign in to open them):
- Feature preview call · Playbooks
- Planning readiness by week and role · Playbooks
- Ways of working playbook: how work flows · Playbooks
- Backlog refinement runbook · Runbooks
- Daily stand-up runbook · Runbooks
- Product-level events overview · Runbooks
- Risk and issue management · Runbooks
- Sprint planning runbook · Runbooks
- Sprint review runbook · Runbooks
- After Pulse Cycle planning: checklist and activities · Checklists
- Pulse Cycle planning: coordinator and facilitator checklists · Checklists
- Cross-product dependency and risk registers, and capacity calculator · Templates
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps