PMP Scope Management — Practice Quiz

Explanation — Correct answer: A No change, regardless of its size, should be implemented without going through the integrated change control process. The project manager must evaluate the impact on all constraints (scope, schedule, cost, quality, risk, resources) before accepting or rejecting a change. Gold plating is also forbidden — even helpful additions must follow the change process.

Explanation — Correct answer: B Validate Scope is the process of obtaining formal customer acceptance of completed deliverables. It occurs during monitoring and controlling throughout the project. Control Quality (A) is internal — the team checks work before presenting it to the customer. Key rule: Control Quality checks conformance internally; Validate Scope gets the customer's signature.

Explanation — Correct answer: A The WBS is the foundation of project planning. It ensures no deliverables are missed, provides the basis for estimating time and costs, helps assign work, and is the primary tool for controlling scope creep. B is partially true but misses the full value. C is incorrect — the WBS supports EVM indirectly but does not contain the schedule baseline itself.

Explanation — Correct answer: D Gold plating refers to adding extras beyond what was requested — even if well-intentioned. It is always forbidden because it consumes resources, may introduce risk, and bypasses the change control process. Scope creep (C) also refers to unapproved scope growth, but gold plating specifically describes the team adding unrequested enhancements on their own initiative.

Explanation — Correct answer: C The scope management plan describes the process — how scope will be defined, how the WBS will be created, how scope will be validated, and how changes will be controlled. It does not contain the actual scope (A), the WBS (D), or elicitation techniques (B — those belong to the requirements management plan).

Explanation — Correct answer: B In agile, scope is flexible but change is not free. Adding new high-priority stories means the product owner reprioritizes the backlog — lower-priority items may be pushed to a future release to preserve cost and schedule baselines. Agile does not automatically expand budget (A). The current iteration's scope is locked (C). Formal CCBs (D) are more typical of predictive projects.

Explanation — Correct answer: A On large projects with many stakeholders, no single technique works for all. Surveys efficiently reach large groups; workshops and targeted interviews ensure depth for key stakeholders. Interviewing all 200 individually (B) is impractical. A single session with 200 participants (C) is unmanageable. Observation and prototyping (D) cannot replace direct stakeholder input at this scale.

Explanation — Correct answer: C Before any action on a scope change, the project manager must analyze the impact on all constraints: schedule, cost, quality, risk, and resources. This assessment feeds the formal change request process. Updating the WBS (A) or requesting budget (B) before the impact analysis skips a critical step. Option D violates the principle that all scope must be visible and controlled.

Explanation — Correct answer: D The RTM links each requirement to the project objectives it supports, ensuring strategic goals are reflected in the project work. While tracking status (C) and recording who submitted requirements (A) are also part of requirements management, they are not the primary purpose. The visual breakdown of deliverables (B) describes the WBS, not the RTM.

Explanation — Correct answer: B Product scope describes the features and functions of what is being produced. Project scope includes the product scope plus all the work required to manage and deliver it. Project scope always contains the product scope, but it is broader. This distinction is fundamental and frequently tested on the PMP exam.

Explanation — Correct answer: A When requirements are emerging, the product backlog is the right tool. It is a living, prioritized list flexible enough to accommodate change while keeping the team focused on highest-value work. A detailed scope statement (B) and WBS (C) require well-defined scope upfront. The RTM (D) is more useful in predictive contexts.

Explanation — Correct answer: C The WBS dictionary details each work package: description, acceptance criteria, assigned resources, duration, cost, milestones, and interdependencies. The full project activity sequence (network diagram) is an output of schedule management — not the WBS dictionary. The WBS dictionary documents what to do per package; the schedule determines the project-wide order.

Explanation — Correct answer: D The scenario describes gold plating — the team adds work beyond what was approved, causing schedule slippage. This is a scope control failure: the project manager should have enforced the WBS as the authority for what work is to be done. Options A and B may be contributing factors but the root cause as described is unauthorized scope expansion.

Explanation — Correct answer: B The definition of done and acceptance criteria must be established before the team begins building a story. When these criteria are clear upfront, the team knows exactly what done means. While D is a good practice, it does not replace clear upfront acceptance criteria.

Explanation — Correct answer: A Work not in the WBS is not part of the project. The PM must stop it, evaluate whether it is genuinely needed, and if so, submit a formal change request. Continuing (B) perpetuates scope creep. Updating the WBS without a change request (C) bypasses integrated change control. Waiting for the sponsor (D) delays necessary action — the PM must assess the situation first.

Explanation — Correct answer: C Some conflicts exceed the project manager's authority and require sponsor or management intervention. Adding both without prioritization (B) risks scope creep. Unilateral decisions (A) and automatic prioritization (D) bypass the stakeholder process and can damage trust.

Explanation — Correct answer: D In a hybrid project, the predictive component uses predictive tools — the WBS and WBS dictionary are mandatory for plan-driven work. Agile tools (A, B, C) are appropriate for the iterative software component. On the exam, always match the scope management tool to the delivery approach described in the scenario.

Explanation — Correct answer: B In agile, the backlog accommodates new requirements. The product owner adds the story and reprioritizes — lower-priority items may shift to later releases. Scope is not fixed in agile (D), and the current iteration scope should not be disrupted mid-sprint (A). Formal CCBs (C) are more typical of predictive projects.

Explanation — Correct answer: A The RTM links requirements from multiple stakeholder groups to project objectives and deliverables, enabling validation at project completion. The scope statement (B) summarizes scope but is not a tracking tool. The WBS dictionary (C) details work packages. The stakeholder register (D) identifies stakeholders but does not track requirements.

Explanation — Correct answer: D A verbal mention at a kickoff meeting is not an approved scope change. Any work not in the WBS is unauthorized. The PM must stop it, assess its impact, and if genuinely needed, submit a formal change request. Retroactively adding to the WBS (A) or letting the team finish (B) normalizes scope creep. Reporting to the sponsor (C) may come later — but the PM must assess the situation first.