Dependencies: agree them, see them, act early

Watch

You will be able to

• Record a dependency between two items
• Agree or decline dependencies at planning
• Read the dependency map and register

Step by step

1. Link the items Item › Links › blocks
   The blocker “blocks” the item that waits on it. Within one team it is agreed at once.
2. Across teams it is requested Team › Work › Sprints › Dependencies to agree
   The other team agrees it at Sprint Planning, with the date it is needed by, or declines it with a reason.
3. See it on the card Board › card
   A chain chip shows what an item waits on: amber while requested, red if declined or at risk.
4. The map and register Work › Dependencies
   Boxes for items, grouped by team and product, with arrows from each blocker. The register lists every dependency, its date and its state.

Try it yourself

Practise as Priya Shah in the demo.
View as Priya Shah. Open the Digital portfolio › Work › Dependencies. Which dependency is still waiting for another team, and which one is at risk?

Open the demo as Priya Shah Password pulse-demo-2026. The demo resets every night.

The examples use a made-up healthcare organisation. DelPulse is not only for healthcare: it can be set up for any industry, with your own names for every portfolio, programme, product and team.

Part of

Delivery team members · Product Managers and Product Owners · Network leads