PMP · Question #831
In a project progress review meeting, the end user raises concern about the quality of the construction of the project. What should the project manager do next?
The correct answer is B. Refer to the requirements document. When an end user raises a quality concern, the project manager should first refer to the requirements document to verify the expected quality standards and specifications.
Question
In a project progress review meeting, the end user raises concern about the quality of the construction of the project. What should the project manager do next?
Options
- ARequest a special technical meeting.
- BRefer to the requirements document.
- CReview the risk management plan.
- DReview all implementation checklists.
How the community answered
(61 responses)- A3% (2)
- B79% (48)
- C7% (4)
- D11% (7)
Why each option
When an end user raises a quality concern, the project manager should first refer to the requirements document to verify the expected quality standards and specifications.
Requesting a special technical meeting without first understanding the specific deviation from requirements is premature.
The requirements document serves as the baseline for all project deliverables, including quality expectations. By referring to it, the project manager can objectively assess if the 'quality of construction' concern aligns with the agreed-upon criteria and determine if a deviation exists. This ensures that any concerns are evaluated against the established scope and quality standards.
Reviewing the risk management plan is reactive and doesn't directly address the immediate concern about current quality against defined standards.
Reviewing implementation checklists might show adherence to process, but doesn't confirm if the resulting quality meets the user's expectations or documented requirements.
Concept tested: Validating project quality against requirements
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/current
Topics
Community Discussion
5
Samuel O.May 26, 2026B is correct. When a stakeholder raises a quality concern, you go back to the requirements documentation to see what was actually agreed upon, since quality is defined as conformance to those requirements. In my experience, getting everyone looking at the same baseline spec clears up about half of these disputes before you ever need to escalate to a technical review.
Olusegun A.May 27, 2026B is correct because when a stakeholder raises a quality concern you go straight to the requirements documentation to verify what was actually agreed upon as the acceptance criteria. Saw this exact scenario on my exam back in 2019 and picked D at first, then caught myself because the PMBOK wants you to validate the concern against the documented requirements before chasing checklists or spinning up extra meetings.
Hiroshi T.Jun 7, 2026Picked D first too. The PMBOK Guide makes it clear that when a stakeholder raises a quality concern, the first step is to consult the project documents to verify what the agreed-upon acceptance criteria actually are. Option B points directly to the requirements documentation, which is where those quality standards and specifications live. D is something you do after confirming the baseline, not before.
Mateus R.May 24, 2026B is correct. Like checking the home blueprint before arguing with the builder, you refer to the agreed requirements document.
Zlatan X.Jun 17, 2026B is correct because the PM needs to establish whether the concern reflects a gap against agreed-upon specifications or a subjective opinion before escalating or triggering rework. At the program level I coach my PMs to anchor every quality dispute in the approved requirements documentation so component decisions stay traceable and defensible. Reviewing checklists or the risk plan prematurely burns cycle time without confirming the baseline expectation. Saw this almost verbatim on my exam sitting, picked B because the stem pointed to a quality concern rather than a risk trigger, and it held up.