Skip to content
Preptima
mediumScenarioMidSeniorLead

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?

6 min readUpdated 2026-08-15Target archetype: Big Tech, Enterprise Captive, Product Startup

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