Scrum interviews go beyond knowing the framework. They want to see how you handle real team dynamics, resistance to change, and the messy situations that textbooks skip over.
Your team has missed the sprint goal for the second consecutive sprint. In the retrospective, the team blames unclear requirements. How should you approach this?