What systemic impediments cause 'Zombie Scrum' in an organization?
This tests your ability to diagnose organizational dysfunction beyond team-level issues. A great answer identifies systemic impediments like a lack of stakeholder involvement, low team autonomy, and a focus on output over value.
What's really being asked
Your ability to think systemically. The interviewer wants to see if you can look past team-level symptoms (like poor stand-ups or missed story points) and identify the root organizational structures that create 'Zombie Scrum.' It tests your senior-level perspective: can you connect engineering practices to business value and diagnose problems at the enterprise level, not just within your own team's bubble?
The full answer
A structured investigation into four key areas of organizational dysfunction. First, the relationship with value and stakeholders: are teams building for real users or just for a proxy product owner who isn't empowered? Second, team autonomy: do teams have control over their process, tools, and architecture, or is everything mandated from above? Third, the definition of 'done': is the goal to ship working software frequently (e.g., every 1-2 sprints) or just to close tickets? Fourth, continuous improvement: is there genuine time and psychological safety for retrospectives that lead to real change, or is it just a ceremony?
The mistakes people make
A major red flag is focusing only on team-level solutions. For example, suggesting 'better backlog grooming,' 'stricter stand-ups,' or 'enforcing story points.' These are symptoms, not causes. Another wrong answer is blaming the engineers for being 'lazy' or 'not motivated.' This shows a lack of senior perspective and an inability to see how the system influences behavior. A junior answer diagnoses the team; a senior answer diagnoses the organization that created the team.
What usually comes next
'Okay, you've identified that teams have no autonomy. What's the first small, concrete experiment you would propose to start changing that?' or 'You mentioned a disconnect from stakeholders. As an engineer, how would you find the 'real' stakeholders and involve them?' or 'How would you measure if any of your proposed changes are actually working?'
A concrete example
'In a previous role, we saw sprint goals being missed by 50% sprint-over-sprint. It looked like an estimation problem. But digging in, we found the 'impediment' was the central architecture review board, which had a 3-week SLA. Teams couldn't get feedback in a 2-week sprint. The systemic issue wasn't the team; it was a governance model incompatible with agile timelines. We proposed embedding an architect with the teams for a quarter, which solved the bottleneck and proved the value of decentralized decision-making.'
Interview question
An organization observes several teams exhibiting 'Zombie Scrum'. Which finding most strongly indicates a systemic root cause rather than just a team-level symptom?
- a.The team's velocity is unpredictable and story point estimates are often inaccurate.
- b.The designated Product Owner cannot approve a feature without consulting a separate committee.Correct
- c.Retrospectives often result in no actionable items to improve the team's process.
- d.Daily stand-ups consistently run over the 15-minute timebox and feel like status reports.
Why? this is the answer
A disempowered Product Owner is a classic systemic impediment, indicating a problem with organizational structure and value streams. The other options are symptoms that often result from systemic issues but are themselves confined to the team's direct process.
Just read this? Test yourself on what you have been reading.
Read the original → zombiescrum.org
- #agile
- #scrum
- #leadership
- #organizational design
- #systems thinking
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles