Project Scope Management 

(Chapter 5 of the
PMBOK® Guide)
01. All of the following are true about the project scope
management plan EXCEPT:
A. It provides guidance on how project scope will be defined, documented, managed, and controlled.
B. It provides guidance on how project scope will be verified.
C. It may be formal or informal, highly detailed, or broadly framed, based upon the needs of the project.
D. It is separate from the project management plan.

02. Collect Requirements is the process of defining and

documenting stakeholders’ needs to meet the project
objectives. All of the following are true about this process
EXCEPT:
A. The project’s success is directly influenced by the care taken in capturing and managing project and
product requirements.
B. Requirements include the quantified and documented needs and expectations of the sponsor,
customer, and other stakeholders.
C. Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built
upon these requirements.
D. The development of requirements begins with an analysis of the information
contained in the risk register.

03. All of the following are true about the project scope

statement EXCEPT:
A. It is an output of the Verify Scope process.
B. It describes, in detail, the project’s deliverables and the work required to create those deliverables.
C. It provides a common understanding of the project scope among project stakeholders.
D. It may contain explicit scope exclusions that can assist in managing stakeholder expectations.

04. All of the following are true about the Control Scope

process EXCEPT:
A. Control Scope is the process of monitoring the status of the project and product scope and managing
changes to the scope baseline.
B. Project scope control is used to manage the actual changes when they occur and is integrated with
the other control processes.
C. Scope changes can be avoided by developing clear and concise specifications
and enforcing strict adherence to them.
D. Scope control includes determining the cause and degree of variance relative to the scope baseline
and deciding whether corrective or preventive action is required.

05. Which of the following statements is true about the work

breakdown structure (WBS)?
A. The WBS is a deliverable-oriented hierarchical decomposition of the work to
be executed by the project team to accomplish the project objectives and create the required
deliverables.
B. The WBS is an unstructured list of project activities in chart form.
C. The WBS is the same as the organizational breakdown structure (OBS).
D. The WBS is the bill of materials (BOM) needed to accomplish the project objectives and create the
required deliverables.

06. The following is an example of a constraint associated with

the project scope that limits the team’s options in scope
definition:
A. A predefined budget.
B. The threat of a strike by a subcontractor.
C. Existing relationships with sellers, suppliers, or others in the supply chain.
D. The method used to measure project performance.

07. An input to the Define Scope process is:

A. The type of contract detail language.
B. Project Charter.
C. Work breakdown structure (WBS).
D. Decomposition.

08. What is the WBS typically used for?

A. To organize and define the total scope of the project.
B. To identify the logical person to be project sponsor.
C. To define the level of reporting that the seller provides the buyer.
D. As a record of when work elements are assigned to individuals.

09. The following is true about the WBS:

A. The WBS is another term for the bar (Gantt) chart.
B. Each descending level of the WBS represents an increasingly detailed
definition of the project work.
C. Work not in the WBS is usually defined in the scope statement of the project.
D. The WBS shows only the critical path activities.

10. An output of the Define Scope process is:

A. Work breakdown structure (WBS).
B. Resource breakdown structure (RBS).
C. Project scope statement.
D. Scope and schedule delays control plan.

11. Which of the following is true about the Verify Scope

process?
A. It is the process of formalizing acceptance of the completed project
deliverables.
B. Is not necessary if the project completes on time and within budget.
C. Occurs primarily when revisions or changes are made to project scope.
D. Scope verification is primarily concerned with correctness of the deliverables, while quality control is
primarily concerned with acceptance of the deliverables and meeting the quality requirements specified
for the deliverables.

12. Which of the following is not an output of the Control

Scope process?
A. Work performance measurements.
B. Change requests.
C. Project document updates.
D. Accepted deliverables.

Result Time..! 

01. Answer: D. PMBOKâ  Guide, page 104, Introduction; and page 126, Section 5.5.1.1

Although not shown here as a discrete process, the work involved in performing the five processes of
Project Scope Management is preceded by a planning effort by the project management team. This
planning effort is part of the Develop Project Management Plan process (Section 4.2), which produces a
scope management plan that provides guidance on how project scope will be defined, documented,
verified, managed, and controlled. The scope management plan may be formal or informal, highly
detailed, or broadly framed, based upon the needs of the project.
02. Answer: D. PMBOKâ  Guide, page 105, Section 5.1

Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the
project objectives. The project’s success is directly influenced by the care taken in capturing and
managing project and product requirements. Requirements include the quantified and documented
needs and expectations of the sponsor, customer, and other stakeholders. These requirements need to
be elicited, analyzed, and recorded in enough detail to be measured once project execution begins.
Collecting requirements is defining and managing customer expectations. Requirements become the
foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements. The
development of requirements begins with an analysis of the information contained in the project
charter (Section 4.1.3.1) and the stakeholder register (Section 10.1.3.1).

03. Answer: A. PMBOKâ  Guide, page 115, Section 5.2.3.1

The project scope statement describes, in detail, the project’s deliverables and the work required to
create those deliverables. The project scope statement also provides a common understanding of the
project scope among project stakeholders. It may contain explicit scope exclusions that can assist in
managing stakeholder expectations. It enables the project team to perform more detailed planning,
guides the project team’s work during execution, and provides the baseline for evaluating whether
requests for changes or additional work are contained within or outside the project’s boundaries.

04. Answer: C. PMBOKâ  Guide, page 125, Section 5.5; and page 127, Section 5.5.2.1

Control Scope: Control Scope is the process of monitoring the status of the project and product scope
and managing changes to the scope baseline. Controlling the project scope ensures all requested
changes and recommended corrective or preventive actions are processed through the Perform
Integrated Change Control process (see Section 4.5). Project scope control is also used to manage the
actual changes when they occur and is integrated with the other control processes. Uncontrolled
changes are often referred to as project scope creep. Change is inevitable, thereby mandating some
type of change control process.

Variance Analysis: Project performance measurements are used to assess the magnitude of variation
from the original scope baseline. Important aspects of project scope control include determining the
cause and degree of variance relative to the scope baseline (Section 5.3.3.3) and deciding whether
corrective or preventive action is required.

05. Answer: A. PMBOKâ  Guide, page 116, Section 5.3

Create WBS is the process of subdividing project deliverables and project work into smaller, more
manageable components. The work breakdown structure (WBS) is a deliverable-oriented hierarchical
decomposition of the work to be executed by the project team to accomplish the project objectives and
create the required deliverables, with each descending level of the WBS representing an increasingly
detailed definition of the project work. The WBS organizes and defines the total scope of the project,
and represents the work specified in the current approved project scope statement.

06. Answer: A. PMBOKâ  Guide, page 115, Section 5.2.3.1

Lists and describes the specific project constraints associated with the project scope that limits the
team’s options, for example, a predefined budget or any imposed dates or schedule milestones that are
issued by the customer or performing organization. When a project is performed under contract,
contractual provisions will generally be constraints. Information on constraints may be listed in the
project scope statement or in a separate log.

07. Answer: B. PMBOKâ  Guide, page 112, Figure 5-4; and page 112, Section 5.2.1

Project Charter, Requirements Documentation , Organizational Process Assets

08. Answer: A. PMBOKâ  Guide, page 116, Section 5.3

Refer Answer 05.

09. Answer: B. PMBOKâ  Guide, page 116, Section 5.3

Refer Answer 05.

10. Answer: C. PMBOKâ  Guide  page 112, Figure 5-4; and pages 115–116, Section 5.2.3

Project Scope Statement, Project Document Updates

11. Answer: A. PMBOKâ  Guide, page 123, Section 5.4

Verify Scope is the process of formalizing acceptance of the completed project deliverables. Verifying
scope includes reviewing deliverables with the customer or sponsor to ensure that they are completed
satisfactorily and obtaining formal acceptance of deliverables by the customer or sponsor. Scope
verification differs from quality control in that scope verification is primarily concerned with acceptance
of the deliverables, while quality control is primarily concerned with correctness of the deliverables and
meeting the quality requirements specified for the deliverables. Quality control is generally performed
before scope verification, but these two processes can be performed in parallel.

12. Answer: D. PMBOKâ  Guide, page 125, Figure 5-13; page 128, Section 5.5.3; page 123, Figure 5-11;
and page 125, Section 5.4.3

Control Scope: Outputs: Work Performance Measurements, Organizational Process Assets

Updates , Change Requests, Project Management Plan Updates, Project Document Updates