PMP · Question #1360
An organization is transitioning to an agile approach. At the project's first sprint review, the product owner did not accept the result of the sprint and has some concerns. What should the project ma
The correct answer is D. Organize a sprint retrospective and discuss the issues and how they can be avoided in the next. The product owner has concerns and did not accept the sprint results, indicating issues with the sprint increment or process.
Question
Options
- AAsk the project team to address the product owner's issues since the product owner is
- BCreate a record in the issue register and escalate the issue to the project steering committee.
- CAsk the product owner to accept the outcome since the team delivered what was agreed in the
- DOrganize a sprint retrospective and discuss the issues and how they can be avoided in the next
How the community answered
(39 responses)- A10% (4)
- B5% (2)
- C3% (1)
- D82% (32)
Why each option
The product owner has concerns and did not accept the sprint results, indicating issues with the sprint increment or process.
Simply telling the team to address issues without a structured discussion undermines the collaborative nature of agile and misses an opportunity for process improvement.
Escalating immediately to a steering committee is premature and bypasses the team's ability to self-organize and resolve issues collaboratively within the agile framework.
Forcing acceptance is antithetical to agile principles, where the Product Owner has the authority to accept or reject sprint increments based on defined criteria.
A sprint retrospective is the designated Scrum event for the team and Product Owner to inspect the sprint, identify what went well, what went wrong, and plan improvements for the next sprint. It provides a structured forum to discuss the Product Owner's concerns, understand the root causes, and agree on actionable changes to improve effectiveness and quality in future sprints.
Concept tested: Agile sprint retrospective purpose
Source: https://scrumguides.org/scrum-guide.html#sprint-retrospective
Topics
Community Discussion
4
Grace U.Feb 8, 2026D is the right call here. The sprint retrospective is exactly where this conversation belongs, since the whole point of it is to look at what went wrong and figure out how to avoid it next time - and that applies even if the issue is a disconnect between the product owner and the team rather than something purely technical.
Orla P.Feb 26, 2026D is the right call here. The sprint review is where the product owner sees the working increment, and if they are not satisfied, the retrospective is exactly where the team figures out what went wrong and how to prevent it next time. Option A pushes blame onto the team without a structured conversation, and option C undermines the product owner's authority to accept or reject work. Option B is pure waterfall thinking and has no place in a healthy agile process. One thing I keep wondering about on these agile transition questions is whether the exam expects you to always default to the retrospective for any sprint-level problem, or
Toby R.Mar 8, 2026Got D on my exam last month. I almost picked A because it made sense to have the team fix the PO's concerns right away, but the key was the sprint review context where the PO didn't accept the work, and the PM should route it to the retrospective so the team can inspect and adapt on what went wrong.
Ingrid P.Feb 13, 2026D. A is tempting but agile teams self-organize in the retrospective, not via PM direction.