MidScenarioScrum
A dependency on another team blocks the sprint goal. What do you do?
Try answering first
Model answer
I treat it as an impediment, and the Scrum Master's job is to help remove it quickly.
- Make it visible. Confirm the facts: what exactly is needed, from whom, by when, and what happens to the Sprint Goal if it does not arrive. Raise it at the Daily Scrum.
- Talk directly. Contact the other team's Scrum Master or Product Owner to understand their priorities and agree on a date. A conversation usually beats a ticket.
- Escalate when needed. If the teams cannot resolve it, bring the product owners or management together with a clear description of the impact.
- Find a workaround. Can the team mock the dependency, work on another item, or reshape the work so part of the goal is still met? The Developers may renegotiate the scope with the Product Owner, while keeping the Sprint Goal.
- Prevent it next time. Find dependencies in refinement and planning, and consider a Scrum of Scrums or a shared cadence.
I would also record the pattern for the retrospective.
Key points
- Make the impediment visible and quantify its impact on the Sprint Goal
- Talk directly with the other team, then escalate if needed
- Look for workarounds and renegotiate scope with the Product Owner
- Surface dependencies earlier in refinement and planning
Likely follow-ups
- When would you cancel the Sprint?
- How do you reduce cross-team dependencies structurally?
Common mistakes
- Waiting silently until the end of the Sprint to report the problem
- Only sending a ticket to the other team and not following up