An Agile Team discovers during a Iteration Review that they cannot complete a critical user story because an external supplier failed to deliver a required API interface. What is the most effective immediate action for the Scrum Master to take?
Trap 1: Extend the current iteration boundary to accommodate the late…
Iteration boundaries are fixed in Scrum; extending one to absorb a supplier delay destroys the cadence and hides the impediment rather than removing it. It is tempting because accommodating a late dependency feels pragmatic, and schedule buffers are valid at programme level, not inside an iteration.
Trap 2: Reassign the blocked team members to unrelated backlog items until…
Reassigning members sidesteps the dependency without resolving it, leaving the critical story blocked and the supplier issue unaddressed. It is tempting because protecting flow by pulling other backlog items is legitimate when a blocker is genuinely outside the team's control and no escalation path exists.
Trap 3: Escalate the vendor delay directly to enterprise executive…
Escalating directly to executives bypasses the Agile Release Train mechanisms and erodes collaborative supplier relationships. Dependency coordination should first be addressed at the Agile Release Train level through Program Increment planning and Scrum of Scrums.
- A
Extend the current iteration boundary to accommodate the late delivery from the external supplier.
Why it fails: Iteration boundaries are fixed in Scrum; extending one to absorb a supplier delay destroys the cadence and hides the impediment rather than removing it. It is tempting because accommodating a late dependency feels pragmatic, and schedule buffers are valid at programme level, not inside an iteration.
- B
Reassign the blocked team members to unrelated backlog items until the external API becomes available.
Why it fails: Reassigning members sidesteps the dependency without resolving it, leaving the critical story blocked and the supplier issue unaddressed. It is tempting because protecting flow by pulling other backlog items is legitimate when a blocker is genuinely outside the team's control and no escalation path exists.
- C
Work with the Product Owner and developers to create a temporary mock interface so internal integration can proceed.
A mock interface lets the team continue integrating and testing their own components despite the supplier's missing API, preserving iteration progress. This unblocks internal work immediately while the dependency is escalated, rather than idling the team.
- D
Escalate the vendor delay directly to enterprise executive management to demand contractual penalties.
Why it fails: Escalating directly to executives bypasses the Agile Release Train mechanisms and erodes collaborative supplier relationships. Dependency coordination should first be addressed at the Agile Release Train level through Program Increment planning and Scrum of Scrums.