PMP · Question #633
A project manager is working on a large IT project. During a review for one of the deliverables. a stakeholder raised a concern about the final product. What should the project manager do first?
The correct answer is C. Discuss this with the team and review the project requirements documentation.. When a stakeholder raises a concern about a deliverable, the project manager should first discuss it with the team and cross-reference the concern against the documented project requirements to understand the discrepancy.
Question
Options
- ADiscuss this with the team and put the stakeholder's concern in the issue log.
- BSet up a meeting with the sponsor to discuss the details of the deliverable.
- CDiscuss this with the team and review the project requirements documentation.
- DSet up a meeting with the product owner to discuss the stakeholder's concern.
How the community answered
(14 responses)- A7% (1)
- B14% (2)
- C71% (10)
- D7% (1)
Why each option
When a stakeholder raises a concern about a deliverable, the project manager should first discuss it with the team and cross-reference the concern against the documented project requirements to understand the discrepancy.
While discussing with the team is good, simply logging it as an issue without first verifying against requirements is premature and doesn't provide the necessary context for resolution.
Escalating to the sponsor before understanding the root cause and verifying against requirements is premature and may unnecessarily involve senior management without sufficient information.
The first step when a stakeholder raises a concern about a deliverable is to understand the nature of the concern and its validity against agreed-upon criteria. By discussing it with the team and reviewing the project requirements documentation, the project manager can determine if the deliverable deviates from the specified requirements, if the requirements themselves are unclear, or if the stakeholder's concern is outside the agreed scope, providing a factual basis for further action.
While a product owner can be involved, the immediate action should be to consult the team who built the deliverable and the foundational requirements documentation to understand the concern's basis.
Concept tested: Requirements validation and issue analysis
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
6
Fatima Z.Apr 22, 2026C is the winner, and my memory hook is C = Check the Contract (aka your requirements docs). Before you log an issue or drag the sponsor into it, you always verify the concern against what was originally agreed upon, so remember CRD: Concern Raised, Dig into requirements.
Yuki V.Apr 3, 2026C is the move here because before you log anything as an issue you need to check whether the concern is actually valid against what was agreed upon in the requirements. The issue log in A is tempting but thats premature if the deliverable already meets spec, so has anyone noticed how PMP questions love testing whether you investigate before you act?
Imani T.Apr 15, 2026Leaned toward A at first since logging the concern sounded like the safe PM move, but the question says the stakeholder raised a concern about the final product during a review, so before you go logging anything you need to verify against the actual requirements documentation. C is the move because you check whether the concern is even valid before treating it as an issue.
Wei W.Apr 11, 2026C is correct. Go back to requirements before logging anything as an issue.
Fatima Z.Apr 12, 2026C is right but remember my handy PASS trick: Prerequisites, Assumptions, Scope, and Standards, because if the requirement itself is fuzzy then your issue log is just a complaint box.
Samuel O.Apr 20, 2026I first leaned toward A because logging the concern felt like the natural reflex after twenty years of dealing with stakeholder complaints, but the key word in the stem is "review" - you need to verify against requirements documentation before you treat it as an issue. C is correct because the concern might just be a misunderstanding of what was already agreed to, and you check the requirements before escalating or logging anything.