PMP · Question #1324
A project manager is assigned to a dental equipment development project that is in the middle of its design phase. After reviewing the project prototype, it is identified that a couple of requirements
The correct answer is C. Meet with the development team to review and assess the requirements specifications.. When missing requirements are identified during the design phase, the project manager should immediately meet with the development team to review and assess the specifics of these requirements.
Question
Options
- AAsk the team to wait until they are able to update the requirements specifications.
- BDiscuss with the team and build a workaround plan to immediately deliver the pending
- CMeet with the development team to review and assess the requirements specifications.
- DPrepare a change request for the change control board (CCB) to remove the missing
How the community answered
(33 responses)- A3% (1)
- B12% (4)
- C79% (26)
- D6% (2)
Why each option
When missing requirements are identified during the design phase, the project manager should immediately meet with the development team to review and assess the specifics of these requirements.
Asking the team to wait is a passive approach that delays resolution and can lead to further issues or rework, especially during the design phase.
Building a workaround plan without first fully understanding the missing requirements and their implications is premature and could lead to an ineffective or risky solution.
Discovering missing requirements specifications necessitates an immediate assessment to understand their impact, scope, and urgency. Meeting with the development team allows for a technical review to determine what exactly is missing, why it was missed, and how it affects the design and overall project, which is the necessary first step before making any decisions.
Preparing a change request to *remove* missing requirements is inappropriate; the goal should be to incorporate critical missing requirements, not to simply discard them, unless a thorough assessment determines they are not essential.
Concept tested: Requirements management and scope validation
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/requirements-management
Topics
Community Discussion
7
Zlatan X.Jan 18, 2026C is correct. At the program level, unresolved component-level gaps in requirements traceability threaten downstream benefits realization, so the project manager must first meet with the development team to assess the missing specifications and understand the interdependency impact before any change request or workaround is initiated.
Carlos M.Jan 6, 2026C is the right call here. You're mid-design and find gaps in the requirements, so the first move is to sit down with the team and assess what's actually missing before doing anything else. B jumps straight to a workaround without understanding the scope of the gap, and A just wastes time. D makes no sense because you don't remove requirements just because they're missing from the docs. Quick question though: if the assessment reveals that the missing specs are actually needed and will impact scope or schedule, does the PM then go straight to a change request, or does the team update the requirements documentation
Luis F.Jan 7, 2026Good catch on C, Carlos, and to answer your question the team updates the requirements documentation first to capture what was missing, then the PM takes that updated info into a change request if there's scope or schedule impact.
Luis F.Jan 27, 2026Had this on my exam last month, C is right, you assess before fixing.
Carlos M.Jan 27, 2026C is right but the keyword to look for in the stem is actually "identify" not just "assess", since some questions use similar wording but ask you to mitigate instead.
Orla P.Feb 3, 2026B. You are mid-design, so talk to the team and build a workaround to keep moving.
Zlatan X.Feb 6, 2026C is correct here because mid-design issues at the program level go through the change request process, not informal workarounds. Orla's B approach is single-project thinking and bypasses the governance framework that keeps component interdependencies aligned across the program.