Ask a room of Scrum Masters why their last sprint missed and you’ll rarely hear “the work was too hard.” You’ll hear that a story was waiting on another team, a shared service, or a ticket that wasn’t finished. Among the Scrum challenges that derail delivery, hidden dependencies are the quietest and the most expensive. Managing dependencies in Scrum well comes down to one principle: make them visible before you commit, not at the review.

Why dependencies hide

A backlog is a flat list. Dependencies are a network. When you plan from a flat list, the relationships between items — “this blocks that,” “this needs the API first” — simply aren’t in your field of view. The team commits in good faith, then discovers mid-sprint that half the board is waiting on something outside its control. The impediment was always there; it just wasn’t visible until it bit. This is a version of the failure pattern we described years ago in the hidden failure point of Scrum.

Surface dependencies before planning

The fix is procedural and visual. Procedurally, refinement should explicitly ask of every candidate story: what must be true before this can start, and who owns it? Visually, those answers need to live somewhere the whole team can see during planning. A dependency that’s drawn on a map gets discussed; one buried in a comment thread gets forgotten. Three habits make the difference:

• Tag relationships as you refine — blocks, is-blocked-by, and cross-team links, not just sub-tasks.
• Review the dependency map in planning so commitments account for what’s external.
• Watch blockers daily so an impediment is escalated the moment it appears, not the day before the demo.

Do it in Jira

Dependency Manager & Map for Jira turns issue links into a visual map of blockers and relationships, so the network behind your backlog is finally something the team can see and reason about. Cross-team dependencies, blocked chains, and the riskiest items surface during planning — which is the only time you can still do something about them. That’s the whole point of managing dependencies in Scrum: convert invisible risk into a visible decision.

Dependencies aren’t a sign of a bad team — they’re a fact of building anything non-trivial. The teams that deliver predictably simply refuse to let them stay hidden. For the rest of the playbook, see our guide to the biggest Scrum challenges and how to solve them.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio