PMPRocket
PMP Practice QuestionsScope Management
Process Domain

Scope Management PMP Practice Questions

Test yourself with 15 free, scenario-based PMP practice questions on scope management, drawn from the Process domain of the exam and aligned to PMBOK 8. Work through each scenario before revealing the answer — every question includes an explanation of why the correct choice is right. For randomized, interactive practice across all topics, use the practice question tool.

Question 1 of 15

Halfway through a predictive project, a stakeholder requests a significant new feature not included in the project charter. The feature would add three weeks to the schedule. What should you do FIRST?

  1. A.Submit the request through the integrated change control process for evaluation
  2. B.Add the feature now to keep the stakeholder satisfied
  3. C.Reject the request because the scope was already agreed upon
  4. D.Add the feature and compress the remaining schedule to absorb the impact
Show answer and explanation

Correct answer: A

All scope changes on a predictive project must go through integrated change control. This ensures the impact on schedule, cost, risk, and quality is formally evaluated before a decision is made. Adding without process is scope creep. Outright rejection ignores the stakeholder's legitimate request and bypasses the proper process.

Question 2 of 15

A project manager is creating a WBS for a new software system. At what level should WBS decomposition STOP?

  1. A.When each work package can be assigned to a single team member who has clear ownership and accountability for delivering the defined deliverable.
  2. B.When every task is broken down to individual hours of effort — maximum decomposition granularity ensures comprehensive effort capture and eliminates unplanned work from the project schedule.
  3. C.When the WBS reaches exactly five levels of decomposition — a consistent hierarchical depth creates uniform granularity across all project branches and comparable work package sizing.
  4. D.When each work package can be reliably estimated, assigned, and monitored — typically 8-80 hours of effort
Show answer and explanation

Correct answer: D

WBS decomposition should stop at the work package level — the point at which work can be reliably scheduled, budgeted, monitored, and controlled. The '8/80 rule' (8 to 80 hours) is a common guideline, though it varies by project. Over-decomposition wastes planning time and creates excessive overhead. The WBS does not mandate a fixed number of levels or require assignment to a single person. Individual task hours are captured in the activity list, not the WBS.

Question 3 of 15

Which of the following BEST describes the 100% rule in WBS development?

  1. A.The WBS must capture 100% of the project scope — no more, no less — at every level of decomposition
  2. B.All WBS work packages must be completed 100% before moving to the next phase
  3. C.All team members must agree 100% on the WBS structure before it is baselined
  4. D.The WBS must have a 100% accuracy rating in the project management plan
Show answer and explanation

Correct answer: A

The 100% rule states that the WBS captures ALL deliverables — internal, external, and interim — and that the sum of child elements at each level equals the parent element in total scope. This prevents both scope gaps (missing deliverables) and scope duplication. It applies at every decomposition level. Completion order, consensus, and accuracy ratings are not related to the 100% rule.

Question 4 of 15

On a hybrid project, the project manager creates a high-level WBS for the predictive phases and uses a product backlog for the agile delivery phase. A team member argues the WBS should decompose all the way to individual user stories. What should the project manager explain?

  1. A.The team member is correct — all deliverables including every user story must appear as individual work packages in the WBS to satisfy the 100% rule and avoid unaccounted project scope.
  2. B.The WBS can include a backlog-level work package representing the agile delivery scope; user stories are managed within the agile framework and not individually listed in the WBS.
  3. C.Hybrid projects do not use a WBS at all — the product backlog replaces the WBS as the single planning artifact, and maintaining both creates unnecessary duplication of scope management effort.
  4. D.The team member should build a separate WBS for the agile phase with user stories as individual work packages — separate structures for each phase maintain methodological consistency across the hybrid project.
Show answer and explanation

Correct answer: B

On hybrid projects, the WBS can represent agile scope at a higher level (e.g., 'Product Increment' or 'Sprint Deliverables') while the agile framework manages detailed story-level decomposition. This balances predictive governance with agile flexibility. The WBS does not need to decompose to story level — doing so would be excessive and undermine the agile iterative approach. The 100% rule is satisfied by including the backlog as a WBS element.

Question 5 of 15

Which of the following are characteristics of a well-constructed WBS? (Select THREE)

Select all that apply.

  1. A.The WBS is decomposed to the same number of levels in every branch
  2. B.Work packages are sequenced in the order they will be performed
  3. C.The sum of child elements equals 100% of the parent element's scope
  4. D.Every work package has a unique WBS code (WBS dictionary entry)
  5. E.Each work package is defined by deliverables, not activities
Show answer and explanation

Correct answers: C and D and E

A well-constructed WBS is deliverable-oriented, not activity-based, follows the 100% rule at every level (the child elements add up to all of the parent's scope), and gives every work package a unique identifier that links to the WBS dictionary for cost and schedule tracking. The WBS does not sequence work: that is the schedule's job. Branches are decomposed only as far as needed to manage the work, so different branches often have different numbers of levels.

Question 6 of 15

A requirements traceability matrix links requirements to which project artifacts to ensure completeness and traceability?

  1. A.Risk register and change log only
  2. B.Stakeholder register and communication management plan
  3. C.Business needs, project objectives, WBS deliverables, test cases, and final product
  4. D.Project charter and project management plan only
Show answer and explanation

Correct answer: C

A requirements traceability matrix (RTM) provides a bidirectional link from each requirement to its source (business need, stakeholder request) through design, development, testing, and delivery. This ensures every requirement is tested and that every test case traces back to a requirement. The RTM helps prevent scope creep (tracing new requirements to approved business needs) and validates completeness (every requirement has been addressed). It is a critical quality and scope management tool.

Question 7 of 15

What is the scope baseline, and what three documents does it comprise?

  1. A.The project charter, stakeholder register, and requirements documentation — these three documents define the project's authorization, stakeholder commitments, and formally agreed deliverables.
  2. B.The project management plan, scope management plan, and requirements traceability matrix — these integrated planning documents together define how scope will be planned, managed, and verified.
  3. C.The WBS, activity list, and project schedule baseline — these three documents together define the decomposed project scope, all required activities, and the planned delivery timeline.
  4. D.The approved scope statement, WBS, and WBS dictionary — used as the reference for measuring and controlling scope performance.
Show answer and explanation

Correct answer: D

The scope baseline consists of three documents: (1) the approved project scope statement — describing what is and is not included; (2) the WBS — hierarchical decomposition of all project deliverables; and (3) the WBS dictionary — detailed descriptions of each WBS component including acceptance criteria. Together these define and control what the project will produce. Changes to the scope baseline require formal change control. The scope baseline is one of three performance baselines, along with the schedule and cost baselines.

Question 8 of 15

On an agile project, how is scope defined and managed differently compared to a predictive project?

  1. A.In agile, scope emerges progressively through the product backlog — the overall feature set is defined at a high level initially and elaborated sprint by sprint, with the product owner continuously prioritizing.
  2. B.Scope is fixed and detailed upfront in both agile and predictive projects — the difference is only in how work is sequenced and delivered, not in how comprehensively scope is defined at the outset.
  3. C.Agile projects have no formal scope management since the core principle of welcoming change means that scope boundaries are intentionally left open and any request can be prioritized at any time.
  4. D.In agile, the scope baseline is locked at the start of each sprint and cannot change mid-sprint; new requests are added to the backlog and prioritized for a future sprint by the product owner.
Show answer and explanation

Correct answer: A

Agile manages scope progressively. High-level epics and features are defined at the start, but detailed requirements (user stories) are elaborated 'just in time' through backlog refinement. The product backlog serves as the living scope document — it can grow, shrink, and reprioritize. Within a sprint, the sprint scope (selected stories) is stabilized. Agile does welcome scope changes — but through the backlog prioritization process, not without governance. The product owner actively manages scope to maximize value delivered.

Question 9 of 15

A project manager is conducting scope validation. A deliverable meets all technical specifications but the customer refuses to formally accept it. What should the project manager do FIRST?

  1. A.Invoke the contract clause requiring acceptance upon technical specification compliance — the contract terms establish the legal obligation to accept, and the customer's refusal is a contractual breach.
  2. B.Understand why the customer will not accept the deliverable — clarify expectations and determine if there is a gap between specifications and actual business needs.
  3. C.Escalate to senior management to compel the customer to accept the deliverable — executive-level intervention from the buyer's organization can override objections and enforce contractual compliance.
  4. D.Issue a formal change request to modify the deliverable to satisfy the customer — customer acceptance is the ultimate success criterion, and adjusting the deliverable to meet actual needs is the right outcome.
Show answer and explanation

Correct answer: B

Before escalating or invoking contract clauses, the project manager should understand the customer's concerns. There may be a legitimate gap: the deliverable meets technical specs but fails to meet unstated or poorly documented business needs — a classic requirements elicitation failure. Understanding the rejection reason informs the correct path forward: modify requirements, negotiate acceptance, or pursue dispute resolution. Immediately issuing a change request assumes modifications are needed before understanding the problem.

Question 10 of 15

Which of the following are components of the requirements documentation? (Select THREE)

Select all that apply.

  1. A.Business requirements — the higher-order business need being addressed
  2. B.Stakeholder requirements — needs and expectations of stakeholder groups
  3. C.Resource assignments — who will work on each requirement
  4. D.Solution requirements — functional and nonfunctional requirements for the product
  5. E.Activity duration estimates — how long each requirement will take to build
Show answer and explanation

Correct answers: A and B and D

Requirements documentation covers business requirements (the organizational need the project addresses), stakeholder requirements (what stakeholders need from the solution) and solution requirements, both functional (what the system does) and nonfunctional (how well it does it). It can also include transition, project and quality requirements. Resource assignments belong to resource management, and activity duration estimates belong to schedule management, not to requirements documentation.

Question 11 of 15

A scope statement is being developed for a new IT infrastructure project. Which element is MOST important to include to prevent disputes later?

  1. A.A detailed resource list of who will work on the project
  2. B.Project exclusions — explicit statements of what is NOT included in the project scope
  3. C.The project sponsor's biography and decision-making authority
  4. D.A preliminary project schedule with milestone dates
Show answer and explanation

Correct answer: B

Project exclusions are one of the most valuable elements of a scope statement for preventing future disputes. By explicitly stating what is NOT in scope (e.g., 'This project does not include end-user training,' 'Network security is managed by the InfoSec team'), the project manager sets clear boundaries. Without explicit exclusions, stakeholders may assume unlisted items are included, leading to scope creep and conflicts. Exclusions document mutual agreement about boundaries — preventing scope arguments later.

Question 12 of 15

A team believes a deliverable is complete, but the customer has never formally reviewed or accepted it. What process concern exists?

  1. A.Internal completion establishes scope acceptance — once the team confirms the work meets their quality standard, the deliverable is ready for formal documentation and work package closure.
  2. B.The discrepancy is a quality control issue, not a scope issue — QC is responsible for verifying delivered outputs against specifications and owns the resolution of this type of discrepancy.
  3. C.Close the work package and let operations resolve the discrepancy during handover — minor specification gaps are routinely absorbed by operational teams without requiring formal project intervention.
  4. D.Scope has not been validated; formal acceptance should occur against agreed criteria before the deliverable is treated as accepted.
Show answer and explanation

Correct answer: D

Validate Scope is about formal acceptance of completed deliverables. Internal completion and quality checks do not replace customer or authorized stakeholder acceptance.

Question 13 of 15

A sponsor says the team has a scope statement but still struggles to organize work logically for estimating, assignment, and control. What is the BEST next step?

  1. A.Develop a scope structure such as a WBS that decomposes deliverables into manageable work packages
  2. B.Jump directly into scheduling because structure can emerge later
  3. C.Ask each lead to define their own tasks without a shared structure
  4. D.Freeze the scope statement and avoid further decomposition to prevent complexity
Show answer and explanation

Correct answer: A

A scope structure turns approved scope into something manageable. Decomposition into work packages supports estimation, ownership, sequencing, and control.

Question 14 of 15

A stakeholder says, "The deliverable meets the technical specification, but it still is not what we expected." What should the project manager examine FIRST?

  1. A.Whether formal acceptance criteria and validation steps were clear and used with the stakeholder
  2. B.Whether the team invested sufficient hours — hours worked is the most objective indicator of whether the team delivered adequate effort on their project commitment.
  3. C.Whether the cost baseline should be revised — if validation difficulties caused cost overruns, the baseline needs updating to reflect the true project cost more accurately.
  4. D.Whether the risk register was updated recently — regular risk documentation is a delivery obligation, and gaps indicate process compliance failures that could affect future sprints.
Show answer and explanation

Correct answer: A

This is a classic scope validation issue. A deliverable can pass technical checks and still fail stakeholder acceptance if validation criteria and engagement were weak.

Question 15 of 15

A team decomposes deliverables until they can estimate and assign ownership clearly. What are they most likely creating?

  1. A.A stakeholder register
  2. B.A risk breakdown structure only
  3. C.A scope structure or WBS down to manageable work packages
  4. D.A benefits register
Show answer and explanation

Correct answer: C

This describes the purpose of decomposing scope into manageable work packages.

Ready for exam conditions?

Practice these questions with randomized answer order and instant scoring, or take a full domain-weighted mock exam with a real exam timer.

More Process practice questions