An organization is moving to agile. At the first sprint review, the product owner did not accept the sprint outcome and raised concerns. What should the project manager do?

The correct answer is to organize a sprint retrospective. A sprint retrospective is a key agile event designed for the team to inspect itself and create a plan for improvements to be enacted during the next sprint. This is the appropriate forum to discuss why the product owner did not accept the sprint outcome and collaboratively identify solutions to prevent similar issues in future sprints. Asking the team to resolve the issues (option A) is insufficient; the problem likely involves process or communication, not just execution. Logging the concern and escalating (option B) is premature and bypasses the agile team's self-organizing principles. Asking the product owner to accept the outcome (option C) ignores valid concerns and undermines the collaborative nature of agile.