After a few iterations the project manager shows the product to a key stakeholder, who reports many features missed the mark. What should the project manager do to prevent this from happening again?

The correct answer is to schedule adequate sprint demos to gather early feedback from stakeholders and adapt the plan accordingly. In an agile environment, frequent feedback loops are crucial to ensure the product meets stakeholder expectations. Sprint demos provide a structured opportunity for stakeholders to review increments and offer feedback, allowing the team to make necessary adjustments early and avoid significant rework later. Setting up requirements-gathering sessions to reassess scope and reprioritize the backlog might be necessary if the initial requirements were severely flawed, but it's a more reactive and potentially time-consuming solution than proactive feedback. Incorporating design thinking practices is valuable for understanding user needs but is a broader, more foundational change that doesn't directly address the immediate need for ongoing feedback on developed features. Evaluating the team's skills and assigning someone to rebuild the interface is premature and doesn't address the root cause of missed expectations, which is a lack of continuous stakeholder validation.