Team Delivers 'Done' Work, But No Stakeholder Value

WHAT THIS TESTS: This question probes your understanding of Scrum as a value-delivery framework, not just a work-management process. The interviewer is testing your ability to diagnose a 'feature factory' anti-pattern, where a team is efficient at producing output but ineffective at delivering outcomes. It specifically assesses whether you can identify the failure points in Scrum's empirical feedback loops (transparency, inspection, adaptation) and propose solutions from within the framework.

A GOOD ANSWER COVERS: A strong answer avoids blame and focuses on process improvement. First, frame the issue as a failure of inspection and adaptation, not just execution. Second, pinpoint the Sprint Review as the most likely broken event. Are the right stakeholders attending? Is it a passive demo or an active, collaborative session to inspect the Increment and adapt the Product Backlog? Third, scrutinize the Sprint Goal. Is it a true, outcome-oriented objective (e.g., 'Allow users to find past orders') or just a list of tasks to complete (e.g., 'Finish JIRA-123 and JIRA-456')? Fourth, propose concrete actions: advocate for restructuring the Sprint Review into a hands-on workshop, collaborate with the Product Owner to write outcome-based Sprint Goals, and suggest developers participate more in backlog refinement to ask clarifying 'why' questions before a Sprint begins.

COMMON WRONG ANSWERS: A major red flag is immediately and exclusively blaming the Product Owner. While the PO is accountable for value, a senior candidate recognizes this as a systemic problem the whole Scrum Team owns. Another weak answer is focusing on irrelevant metrics like velocity or story points; the problem is about value, not speed. Suggesting a radical change, like abandoning Scrum for Kanban, without first attempting to fix the existing process, shows a superficial understanding. Finally, offering vague advice like 'we need better communication' is a hallmark of a junior answer; be specific about which events and artifacts need to change.

LIKELY FOLLOW-UPS: What if key stakeholders refuse to attend the Sprint Review? (This is an organizational impediment the Scrum Master should address. The team can mitigate by bringing qualitative data, user recordings, or a proxy user to the review). How would you propose changing the Definition of 'Done' to help? (By adding a criterion like 'Validated by at least one target-persona user' or 'Stakeholder review completed'). What is the Scrum Master's role in fixing this? (Coaching the PO on value, facilitating a more effective Sprint Review, and removing impediments like stakeholder availability).

ONE CONCRETE EXAMPLE: In a previous role, our team had a high velocity but a survey revealed that over 50% of features shipped in the last quarter had low or no usage. We diagnosed a broken Sprint Review. We changed it from a 30-minute slide demo to a 90-minute working session where stakeholders used the actual increment in a staging environment. The direct feedback from the first new-style review caused us to scrap a planned epic, saving an estimated 6 Sprints of development on a feature our users confirmed they didn't need.