CAPM Project Scope Management — Questions and Answers

Question 1: What is the primary purpose of Project Scope Management?

To ensure the project is completed on schedule
To define and control what is and is not included in the project (Correct answer)
To manage the project budget
To identify and manage project stakeholders

Correct answer: To define and control what is and is not included in the project

Project Scope Management ensures that the project includes all the work required—and only the work required—to complete the project successfully, preventing both under-delivery and scope creep.

According to the PMBOK Guide, Project Scope Management has two dimensions: product scope (the features and functions of the product, service, or result) and project scope (the work performed to deliver the product/service/result). The processes—Plan Scope Management, Collect Requirements, Define Scope, Create WBS, Validate Scope, and Control Scope—collectively ensure that the project boundary is clearly defined, understood by stakeholders, baselined, and protected from unauthorized changes.

Question 2: What is 'scope creep'?

The gradual increase in project budget over time
The uncontrolled expansion of project scope without corresponding adjustments to time, cost, and resources (Correct answer)
The formal process of adding new features to the project
The process of reviewing scope at each project phase

Correct answer: The uncontrolled expansion of project scope without corresponding adjustments to time, cost, and resources

Scope creep is the uncontrolled expansion of project scope—adding features, requirements, or deliverables without adjusting time, cost, or resources through the formal change control process.

Scope creep is one of the most common causes of project failure. It typically happens when stakeholders add 'small' requests that individually seem harmless but collectively expand the project significantly. The antidote to scope creep is a rigorous change control process (Integrated Change Control), a clearly defined and baselined scope, and a culture of scope discipline.

Question 3: Which document serves as the primary output of the 'Define Scope' process?

Work Breakdown Structure (WBS)
Project scope statement (Correct answer)
Requirements traceability matrix
Project charter

Correct answer: Project scope statement

The project scope statement is the primary output of Define Scope, providing a detailed description of the project and product scope, major deliverables, assumptions, and exclusions.

The project scope statement includes: product scope description, acceptance criteria, deliverables, exclusions, constraints, and assumptions. The explicit listing of exclusions is particularly valuable—it prevents scope creep by documenting what is NOT included. This statement becomes part of the scope baseline (along with the WBS and WBS dictionary) and is the foundation for scope verification and control.

Question 4: What is the Work Breakdown Structure (WBS)?

A Gantt chart showing all project tasks
A hierarchical decomposition of the total scope of work to be carried out by the project team (Correct answer)
A list of all project team members and their responsibilities
A network diagram showing task dependencies

Correct answer: A hierarchical decomposition of the total scope of work to be carried out by the project team

The WBS is a hierarchical decomposition of the total project scope into smaller, manageable components (work packages) that can be planned, estimated, and assigned.

The WBS decomposes the project scope from the project level down through deliverables to work packages. A work package is the lowest level of the WBS—small enough to be estimated and managed, typically 8–80 hours of effort. The WBS is a deliverable-oriented structure (it shows WHAT will be produced, not how or when). The WBS is the foundation for developing the schedule, cost baseline, and resource planning.

Question 5: What is the '100% rule' as it applies to the WBS?

All project costs must be estimated to 100% accuracy
The WBS must capture 100% of the project scope—all deliverables and work, including project management work, at the lowest level of detail (Correct answer)
All WBS work packages must be completed 100% before the next level is started
100% of the project team must agree on the WBS before it is approved

Correct answer: The WBS must capture 100% of the project scope—all deliverables and work, including project management work, at the lowest level of detail

The 100% rule states that the WBS must include 100% of the scope defined in the project scope statement and project charter—all work, no more and no less.

The 100% rule has two components: inclusion (every piece of work required to complete the project must appear somewhere in the WBS) and exclusion (no work outside the defined scope should be in the WBS). Violating the inclusion side risks missing work that must be done. Violating the exclusion side includes unauthorized scope in the plan. The 100% rule is the primary quality criterion for WBS review.

Question 6: What is the purpose of the 'Validate Scope' process?

To ensure the project is on budget
To formally accept completed project deliverables from the customer or sponsor (Correct answer)
To create the project scope statement
To approve the work breakdown structure

Correct answer: To formally accept completed project deliverables from the customer or sponsor

Validate Scope is the process of obtaining formal acceptance of completed project deliverables from the customer or sponsor, confirming that deliverables meet the defined acceptance criteria.

Validate Scope (in the Monitoring and Controlling process group) involves reviewing deliverables with the customer/sponsor to obtain formal written acceptance that the deliverable meets the agreed acceptance criteria. If a deliverable is not accepted, change requests or defect repair requests are generated. Validate Scope is distinct from quality control—quality control is internal, while Validate Scope is external (customer acceptance).

Question 7: What is a 'requirements traceability matrix' (RTM)?

A chart tracking the project schedule milestones
A grid that links each requirement to its source and traces it through the project lifecycle to verify it is met (Correct answer)
A financial model tracking budget requirements
A risk matrix correlating requirements to potential risks

Correct answer: A grid that links each requirement to its source and traces it through the project lifecycle to verify it is met

The requirements traceability matrix links each requirement to its source (stakeholder, business need, etc.) and traces it forward through design, development, testing, and delivery to ensure every requirement is addressed.

The RTM serves several purposes: it ensures all stated requirements are designed into the product, tracks requirements through testing and validation, provides traceability for audit purposes, and helps manage scope changes by showing which design elements and test cases are affected by a requirement change. The RTM is a key tool for preventing scope creep because it makes the scope-to-requirement relationship explicit.

Question 8: What is the difference between 'product scope' and 'project scope'?

Product scope refers to cost; project scope refers to schedule
Product scope describes the features and functions of the deliverable; project scope describes all the work required to deliver that product (Correct answer)
They are interchangeable terms
Product scope applies only to manufacturing projects; project scope applies to service projects

Correct answer: Product scope describes the features and functions of the deliverable; project scope describes all the work required to deliver that product

Product scope defines the characteristics and functionality of the product, service, or result to be created; project scope defines the work that must be performed to deliver the product.

Completion of product scope is measured against product requirements (does the product have all the features specified?). Completion of project scope is measured against the project management plan (was all the planned work done?). Both scopes must be fully defined and managed to deliver a successful project. Changes to either type of scope require formal change control.

Question 9: During which process is the scope baseline created?

Define Scope
Collect Requirements
Create WBS (Correct answer)
Plan Scope Management

Correct answer: Create WBS

The scope baseline is created as an output of the Create WBS process and consists of the scope statement, WBS, and WBS dictionary—the approved version of these documents used for comparison throughout the project.

The scope baseline is composed of three components: (1) the project scope statement (from Define Scope), (2) the WBS (from Create WBS), and (3) the WBS dictionary (from Create WBS). This composite baseline is the approved reference against which project scope performance is measured. Changes to the scope baseline require formal change requests through Integrated Change Control.

Question 10: What is a 'WBS dictionary'?

A glossary of project management terms
A document that provides detailed information about each WBS element, including descriptions, acceptance criteria, assumptions, and responsible party (Correct answer)
A list of all project documents
A dictionary of all technical terms related to the project deliverable

Correct answer: A document that provides detailed information about each WBS element, including descriptions, acceptance criteria, assumptions, and responsible party

The WBS dictionary is a companion document to the WBS that provides a detailed description of each WBS component—its scope of work, deliverable descriptions, assumptions, responsible party, schedule milestones, and acceptance criteria.

The WBS dictionary prevents ambiguity in the WBS by providing sufficient detail for each work package to be accurately estimated, assigned, and executed. For each WBS element, the dictionary typically includes: code of account identifier, description of work, assumptions and constraints, schedule milestone(s), resources required, cost estimate, acceptance criteria, and technical references or specifications.

Question 11: What is 'gold plating' in the context of scope management?

Adding extra cost contingency to the budget
Adding features or functionality beyond what the customer requested or approved, typically by the project team (Correct answer)
The process of formally approving project deliverables
Updating the scope statement to reflect approved changes

Correct answer: Adding features or functionality beyond what the customer requested or approved, typically by the project team

Gold plating is when the project team adds unrequested features or functionality beyond the approved scope, believing the customer will appreciate the extras—but doing so without formal approval.

Gold plating is distinct from scope creep in origin: scope creep is usually driven by stakeholder requests; gold plating is driven by the project team. Gold plating is problematic because: (1) the customer may not want or need the extras, (2) it consumes time and resources that could be better used elsewhere, (3) additional features add complexity and testing requirements. Scope management discipline requires delivering exactly what is specified—nothing more, nothing less.

Question 12: Which of the following is an input to the 'Collect Requirements' process?

Project scope statement
WBS
Project charter and stakeholder register (Correct answer)
Network diagram

Correct answer: Project charter and stakeholder register

The project charter and stakeholder register are key inputs to Collect Requirements—the charter provides the project's high-level requirements, and the stakeholder register identifies who has requirements to contribute.

Key inputs to Collect Requirements include: project charter (provides high-level product and project requirements), stakeholder register (identifies stakeholders who have requirements), stakeholder engagement plan, and assumption log. The process uses techniques like interviews, focus groups, facilitated workshops (JAD sessions), questionnaires, prototyping, and benchmarking to elicit requirements from stakeholders.

Question 13: What is the primary tool used to decompose deliverables into smaller, manageable components in the Create WBS process?

Network diagramming
Rolling wave planning
Decomposition (Correct answer)
Mind mapping

Correct answer: Decomposition

Decomposition is the primary technique for creating a WBS—progressively breaking down project deliverables and project work into smaller, more manageable components (work packages).

Decomposition in WBS creation works top-down: starting with the project itself at level 1, then major deliverables or phases at level 2, then sub-deliverables at level 3, and continuing down until work packages (estimable, assignable units of work) are reached. The test for a work package is: can it be realistically estimated? Can it be assigned to a responsible party? Can its completion be measured?

Question 14: What does it mean to 'baseline' the project scope?

To formally approve the scope documents and use them as the reference point against which actual performance will be measured (Correct answer)
To submit the scope documents for stakeholder review
To create the first draft of the scope statement
To place all scope documents in the project archive

Correct answer: To formally approve the scope documents and use them as the reference point against which actual performance will be measured

Baselining means formally approving the scope statement, WBS, and WBS dictionary through Integrated Change Control, establishing them as the approved reference standard against which scope performance is measured.

Before a scope baseline exists, documents are drafts subject to revision without formal process. Once baselined, changes require formal change requests evaluated through Integrated Change Control. The scope baseline (scope statement + WBS + WBS dictionary) serves as: the reference for measuring scope variance, the authorization document for scope-related expenditures, and the input to earned value calculations.

Question 15: How does 'Control Scope' differ from 'Validate Scope'?

Control Scope is done once at project close; Validate Scope happens throughout the project
Control Scope manages the current approved scope and processes change requests; Validate Scope obtains customer acceptance of completed deliverables (Correct answer)
They are the same process with different names
Validate Scope is an internal process; Control Scope involves external stakeholders

Correct answer: Control Scope manages the current approved scope and processes change requests; Validate Scope obtains customer acceptance of completed deliverables

Control Scope monitors the project scope for changes and manages unauthorized changes through the change control process; Validate Scope is about getting formal acceptance of completed deliverables from the customer.

Control Scope (Monitoring and Controlling) involves: monitoring scope performance, detecting unauthorized changes (scope creep), analyzing variance between actual and planned scope, and processing formal change requests. Validate Scope (also Monitoring and Controlling) involves: reviewing completed deliverables against acceptance criteria with the customer and obtaining formal sign-off.

Question 16: What is 'rolling wave planning' and how does it relate to scope management?

A risk management technique for volatile projects
A planning approach where near-term work is planned in detail while future work is planned at a higher level, with detail added as more information becomes available (Correct answer)
A technique for accelerating the project schedule
A method for decomposing the WBS all at once at project start

Correct answer: A planning approach where near-term work is planned in detail while future work is planned at a higher level, with detail added as more information becomes available

Rolling wave planning progressively elaborates the WBS—near-term work packages are fully detailed, while future work remains at a higher WBS level until sufficient information is available to decompose it further.

Rolling wave planning acknowledges that not all project work can be fully defined at project start—especially in complex, innovative, or long-duration projects. Early phases are decomposed to the work package level because the work is well-understood. Later phases are planned at a summary level until the work becomes better defined. This approach prevents both over-planning and under-planning.

Question 17: What is the primary purpose of the 'Plan Scope Management' process?

To define the project scope
To create the WBS
To create a scope management plan that describes how scope will be defined, validated, and controlled (Correct answer)
To collect requirements from stakeholders

Correct answer: To create a scope management plan that describes how scope will be defined, validated, and controlled

Plan Scope Management creates the scope management plan—the document describing how project scope will be defined, developed, monitored, controlled, and validated throughout the project.

The Plan Scope Management process (Planning process group) produces two key outputs: the scope management plan (describes scope definition, WBS development, acceptance processes, and change control procedures) and the requirements management plan (describes how requirements will be collected, documented, prioritized, and traced). These plans provide guidance for all subsequent scope management processes.

Question 18: Which technique is commonly used to collect requirements from a large number of geographically dispersed stakeholders?

Focus groups
Joint Application Development (JAD) workshops
Questionnaires and surveys (Correct answer)
Prototyping

Correct answer: Questionnaires and surveys

Questionnaires and surveys are effective for collecting requirements from large numbers of dispersed stakeholders efficiently, though they sacrifice the interactive dialogue of workshops.

Each requirements collection technique has tradeoffs: Interviews are deep but time-consuming; Focus groups gather qualitative input from a small group; JAD workshops are collaborative and efficient for co-located stakeholders; Questionnaires scale to large, dispersed groups but lack interactivity. For large dispersed groups, questionnaires provide broad coverage at low cost. Often, multiple techniques are used in combination—surveys for breadth, interviews for depth.

Question 19: What does it mean for a requirement to be 'testable' or 'verifiable'?

The requirement can be implemented quickly
The requirement can be objectively evaluated to determine whether it has been met (Correct answer)
The requirement can be tested on multiple platforms
The requirement can be revised during project execution

Correct answer: The requirement can be objectively evaluated to determine whether it has been met

A testable or verifiable requirement can be objectively evaluated—through inspection, testing, demonstration, or analysis—to determine unambiguously whether it has been satisfied.

'The system shall be user-friendly' is not testable (how do you measure 'user-friendly'?). 'The system shall respond to search queries in under 3 seconds for 95% of requests under normal load conditions' is testable. During requirements collection, project managers work to make vague stakeholder desires into specific, testable requirements. Untestable requirements create scope disputes at Validate Scope because there is no objective measure of completion.

Question 20: What is the role of a project sponsor in scope management?

The sponsor executes all scope changes personally
The sponsor has no role in scope management once the project charter is signed
The sponsor approves the scope baseline, authorizes scope changes above the project manager's authority, and serves as the final arbiter of scope disputes (Correct answer)
The sponsor creates the WBS

Correct answer: The sponsor approves the scope baseline, authorizes scope changes above the project manager's authority, and serves as the final arbiter of scope disputes

The project sponsor approves the scope baseline, authorizes significant scope changes, provides funding adjustments when scope changes affect budget, and resolves scope disputes that exceed the project manager's authority.

The sponsor's scope management role includes: approving the initial project charter (which defines the project's purpose and high-level scope), approving the project scope statement and WBS baseline, sitting on the Change Control Board (CCB) for major scope changes, providing additional resources when authorized scope changes expand the project, and resolving escalated disputes between stakeholders about what is or is not in scope.

Question 21: How does scope management relate to the project's 'triple constraint'?

Scope management is independent of time and cost
Scope is one vertex of the triple constraint; changes to scope directly impact time and cost, requiring adjustment to maintain balance (Correct answer)
Scope management only affects cost, not schedule
The triple constraint applies only to schedule management

Correct answer: Scope is one vertex of the triple constraint; changes to scope directly impact time and cost, requiring adjustment to maintain balance

Scope is one of the three primary project constraints (scope-time-cost); expanding scope without adjusting time or cost creates an imbalanced project, so scope changes must always be evaluated for their time and cost impacts.

The traditional triple constraint (iron triangle) positions scope, time, and cost as the three dimensions of project delivery. These dimensions are interdependent: expanding scope requires more time and/or cost; compressing the schedule with the same scope requires more cost or reduced scope/quality; cutting the budget with fixed scope and schedule forces quality reductions. This is why scope change requests must include impact assessments on schedule and cost before approval.

Question 22: What does 'progressive elaboration' mean in the context of project scope?

Adding unnecessary work to the project over time
The continuous improvement and detailing of a project plan as more information becomes available and as the project characteristics become better defined (Correct answer)
Eliminating low-priority requirements from the scope
The process of formally closing the project scope

Correct answer: The continuous improvement and detailing of a project plan as more information becomes available and as the project characteristics become better defined

Progressive elaboration is the iterative process of continually increasing the level of detail in a project plan as more specific information becomes available throughout the project lifecycle.

Progressive elaboration reflects the reality that projects often begin with broad, high-level requirements and become increasingly defined as the project progresses. The project charter may describe the project in paragraphs; the scope statement describes it in pages; the WBS decomposes it into hundreds of work packages. Each iteration adds definition and precision. This concept also applies to risk management, scheduling (rolling wave planning), and cost estimating.

Question 23: What is a 'deliverable' in the context of project scope management?

Any action taken by the project team
A unique and verifiable product, result, or capability produced as an outcome of a project process, phase, or project (Correct answer)
The financial output of the project
Any meeting held during the project

Correct answer: A unique and verifiable product, result, or capability produced as an outcome of a project process, phase, or project

A deliverable is a unique, verifiable output produced by the project—a product, service, capability, or document that represents a tangible result of project work.

Deliverables are the fundamental unit of the WBS—each WBS branch ultimately traces down to specific deliverables that are produced by work packages. Deliverables have defined acceptance criteria that determine when they are complete. The Validate Scope process is specifically about getting formal stakeholder acceptance of completed deliverables. Clear definition of deliverables upfront prevents scope disputes at project close.

Question 24: Why is documenting 'exclusions' in the project scope statement significant?

Exclusions are only documented for legal purposes
Documenting exclusions explicitly prevents scope creep by making clear what the project will NOT deliver, reducing stakeholder assumptions (Correct answer)
Exclusions are only relevant for cost management
Exclusions do not need to be documented because they are implied

Correct answer: Documenting exclusions explicitly prevents scope creep by making clear what the project will NOT deliver, reducing stakeholder assumptions

Explicitly documenting scope exclusions prevents scope creep by making clear what is NOT in the project, eliminating stakeholder assumptions that certain work is included when it is not.

Exclusions are as important as inclusions in scope definition. Stakeholders often assume that adjacent or related work is part of the project without ever stating it explicitly. By documenting specific exclusions, the project manager creates an explicit reference point. When stakeholders later request excluded work, the project manager can reference the documented exclusion and process it through formal change control rather than absorbing it informally.

Question 25: What is the scope management plan's key output regarding change control?

It assigns budgets for scope changes
It defines the process for submitting, reviewing, and approving scope changes through Integrated Change Control (Correct answer)
It eliminates the possibility of scope changes after baseline
It only applies to changes requested by the sponsor

Correct answer: It defines the process for submitting, reviewing, and approving scope changes through Integrated Change Control

The scope management plan defines the process for how scope changes will be submitted, reviewed, and approved through Integrated Change Control, providing the governance framework for managing scope.

One of the key elements of the scope management plan is the description of the change control process for scope—specifically: how to submit change requests, who reviews them, what criteria are used, and what authority levels are required. This section of the scope management plan directly feeds into the Integrated Change Control process, ensuring that all scope changes are handled consistently and formally throughout the project lifecycle.

Question 26: What is the relationship between requirements documents and the WBS?

They are the same document with different names
Requirements documents define what is needed; the WBS defines the work to be done to meet those requirements—each WBS work package should be traceable to one or more requirements (Correct answer)
Requirements documents replace the WBS in agile projects
The WBS is created before requirements are collected

Correct answer: Requirements documents define what is needed; the WBS defines the work to be done to meet those requirements—each WBS work package should be traceable to one or more requirements

Requirements documents define the 'what' (stakeholder needs); the WBS defines the 'how' (the work needed to meet those requirements)—with the requirements traceability matrix linking both.

The relationship flows: Collect Requirements → requirements documentation and RTM, then Define Scope uses requirements to write the scope statement, then Create WBS decomposes the scope statement into work packages. Each work package in the WBS should be traceable back to one or more requirements in the requirements documentation. This traceability is maintained in the RTM and ensures that all approved requirements are reflected in the WBS and ultimately delivered by the project.

CAPM Project Scope Management

What is the primary purpose of Project Scope Management?

🃏 CAPM Flashcards — Study This Quiz as Flip Cards →

📚 Want to go deeper? Read the Full CAPM Study Guide →