For three sprints running your team has lost most of a week waiting for a shared test environment another group controls. What do you do about it?
Answer
Short answer
Price the delay in developer-days from the board's own timestamps, then escalate with a specific ask, an owner and a date rather than a complaint. Decide honestly whether this is an impediment somebody can remove or a constraint to design around, and watch for the workaround that hides the cost.
The interviewer is listening for how you handle impediments without turning them into blame. Serious impediments need visibility, ownership, and a decision path; they do not disappear because the team mentions them again in stand-up. A strong answer separates impediments the team can remove from impediments that need escalation, then shows how you keep delivery honest while the dependency is unresolved. The weak answer treats impediments as background noise and lets the sprint plan stay fictional.
Was this answer helpful?
Likely follow-ups
- The platform team agrees it is a problem and says it is on their roadmap for next quarter. What now?
- Your team has started testing in production behind flags to get around it. Is that a fix or a new impediment?
- How would you decide whether to build your own environment rather than wait for theirs?
- Nothing changes after two escalations. Who do you go to, with what, and what do you stop doing?
Related questions
- Two developers on your team are in open conflict and the rest of the team has started working around them. How do you handle it?hardAlso on impediments and escalation4 min
- Tell me about a time another team was blocking you and you had no authority over them.mediumAlso on dependencies and escalation6 min
- Tell me about a decision you had to make in minutes, with information you knew was incomplete.mediumAlso on escalation6 min
- Every test passed and the release broke in production anyway. How do you work out what your suite was never going to catch?hardAlso on test-environments6 min