What structural impediments drive Zombie Scrum in agile transformations?

WHAT THIS TESTS: This question tests whether you can see organizational anti-patterns beneath surface-level process complaints. A senior engineer is expected to diagnose structural blockers like funding models, architecture, and HR incentives rather than blame teams for lazy standups. The interviewer wants evidence of systems thinking and the courage to name power structures that prevent shipping, learning, and autonomy.

A GOOD ANSWER COVERS: First, funding and governance by project rather than by product, which forces teams to chase deadlines instead of outcomes, destroys long-term ownership, and starves teams of the ability to respond to emerging needs. Second, component-team structures where no single team can build and ship an end-to-end increment, creating dependency gridlock and fake Scrum. Third, missing real stakeholders with budget or decision authority in Sprint Reviews, reducing feedback to polite applause and hiding the fact that nobody with power sees the work. Fourth, HR and performance systems that reward individual utilization, heroics, and hierarchical escalation instead of team collaboration and psychological safety. Fifth, technical architecture and delivery infrastructure that prevent continuous integration and deployment, making fast feedback physically impossible regardless of team intent. Sixth, management culture that treats estimates as commitments and loads teams to one hundred percent capacity, leaving no slack for improvement experiments.

COMMON WRONG ANSWERS: Blaming teams for not trying hard enough or for skipping story points. Suggesting more Scrum training, stricter ceremonies, or additional velocity tracking. Ignoring the technical system and proposing process fixes for a monolithic codebase with quarterly release windows. Framing the problem as a lack of Jira discipline rather than a lack of autonomy and stakeholder intimacy.

LIKELY FOLLOW-UPS: How would you create transparency about these impediments without formal authority? What experiments would you run first if leadership refuses to change the funding model? How do you distinguish between a team that needs coaching and a system that prevents any team from succeeding? What would you measure to prove that structural change is working?

ONE CONCRETE EXAMPLE: You notice every Sprint Review is attended only by internal proxies who cannot approve features. The real budget holders meet quarterly in a steering committee. You invite one budget holder to a Review, show working software, and ask for a go-no-go decision on the spot. The resulting tension reveals that the organization is optimized for control, not flow, and creates data to challenge the steering-committee model.