5. Project Scope Management Terms

Question 1

A planning heuristic for creating the
WBS. This rule states that the work
package in a WBS must take no more
than 80 hours of labor to create and no
fewer than 8 hours of labor to create.

Answer 1

8/80 Rule

Question 2

The observer interacts with the worker to
ask questions and understand each step
of the work being completed. In some
instances, the observer could serve as an
assistant in doing the work.

Answer 2

Active observation

Question 3

When stakeholders create a large

number of ideas, you can use this to cluster similar ideas together for further analysis.

Answer 3

Affinity diagrams

Question 4

A scope definition process of finding
alternative solutions for the project
customer while considering the
customer’s satisfaction, the cost of the
solution, and how the customer may use
the product in operations.

Answer 4

Alternatives generation

Question 5

A decision method where only one
individual makes the decision for the
group.

Answer 5

Autocratic

Question 6

This approach encourages participants to
generate as many ideas as possible
about the project requirements. No idea
is judged or dismissed during the
brainstorming session.

Answer 6

Brainstorming

Question 7

Documented in the scope management
plan, this system defines how changes to
the project scope are managed and
controlled.

Answer 7

Change control system (CCS)

Question 8

This subsidiary plan defines how
changes will be allowed and managed
within the project.

Answer 8

Change management plan

Question 9

A numbering system for each item in the
WBS. The PMBOK is a good example of
a code of accounts, as each chapter and
its subheadings follow a logical
numbering scheme. For example,
PMBOK 5.3.3.2 identifies an exact
paragraph in the PMBOK.

Answer 9

Code of accounts

Question 10

This subsidiary plan defines how
changes to the features and functions of
the project deliverables will be monitored
and controlled within the project.

Answer 10

Configuration management plan

Question 11

These diagrams show the relationship
between elements of an environment. For
example, this diagram would
illustrate the networks, servers,
workstations, and people that interact
with the elements of the environment.

Answer 11

Context diagram

Question 12

A moderator-led requirements collection
method to elicit requirements from
stakeholders.

Answer 12

Focus groups

Question 13

This is the study of the functions within a
system, project, or, what’s more likely in
the project scope statement, the product
the project will be creating. Functional
analysis studies the goals of the product,
how the product will be used, and the
expectations the customer has of the
product once it leaves the project and
moves into operations. Functional
analysis may also consider the cost of
the product in operations, which is known
as life-cycle costing.

Answer 13

Functional analysis

Question 14

Most projects have a determined budget
in relation to the project scope. There
may be a qualifier on this budget, such as
plus or minus 10 percent based on the
type of cost estimate created.

Answer 14

Funding limit

Question 15

A requirements collection method used to
elicit requirements from stakeholders in a
one-on-one conversation.

Answer 15

Interviews

Question 16

A group decision method where more
than 50 percent of the group must be in
agreement.

Answer 16

Majority

Question 17

This approach maps ideas to show the
relationship among requirements and the
differences between requirements. The
map can be reviewed to identify new
solutions or to rank the identified
requirements.

Answer 17

Mind mapping

Question 18

As with brainstorming, participants are
encouraged to generate as many ideas
as possible, but the suggested ideas are
ranked by a voting process.

Answer 18

Nominal group technique

Question 19

The observer records information about
the work being completed without
interrupting the process; sometimes
called the invisible observer.

Answer 19

Passive observation

Question 20

A group-decision method where the
largest part of the group makes the
decision when it’s less than 50 percent of
the total. (Consider three or four factions
within the stakeholders.)

Answer 20

Plurality

Question 21

This project scope statement component
works with the project requirements, but
focuses specifically on the product and
what the conditions and processes are
for formal acceptance of the product.

Answer 21

Product acceptance criteria

Question 22

A scope definition technique that breaks
down a product into a hierarchical
structure, much like a WBS breaks down
a project scope.

Answer 22

Product breakdown

Question 23

This is a narrative description of what the
project is creating as a deliverable for the
project customer.

Answer 23

Product scope description

Question 24

Defines the product or service that will
come about as a result of completing the
project. It defines the features and
functions that characterize the product.

Answer 24

Product scope

Question 25

This is a factor in the planning process that is held to be true but not proven to be true.

Answer 25

Project assumptions

Question 26

This clearly states what is included with the project and what’s excluded from the project. This helps to eliminate assumptions between the project management team and the project customer.

Answer 26

Project boundaries

Question 27

This is anything that limits the project manager’s options. Consider a predetermined budget, deadline, resources, or materials the project manager must use within the project.

Answer 27

Project constraints

Question 28

These are the measurable goals that
determine a project’s acceptability to the
project customer and the overall success
of the project. These often include
the cost, schedule, technical
requirements, and quality demands.

Answer 28

Project objectives

Question 29

These are the demands set by the customer, regulations, or the performing organization that must exist for the project deliverables to be acceptable. These are often prioritized in a number of ways, from “must have” to “should have” to “would like to have.”

Answer 29

Project requirements

Question 30

This defines all of the work, and only the
required work, to complete the project
objectives.

Answer 30

Project scope

Question 31

This project management subsidiary plan
controls how the scope will be defined,
how the project scope statement will be
created, how the WBS will be created,
how scope validation will proceed, and
how the project scope will be controlled
throughout the project.

Answer 31

Project scope management plan

Question 32

This documentation of what the
stakeholders expected in the project
defines all of the requirements that must
be present for the work to be accepted by
the stakeholders.

Answer 32

Requirements documentation

Question 33

This subsidiary plan defines how
changes to the project requirements will
be permitted, how requirements will be
tracked, and how changes to the
requirements will be approved.

Answer 33

Requirements management plan

Question 34

This is a table that maps the
requirements throughout the project all
the way to their completion.

Answer 34

Requirements traceability matrix (RTM)

Question 35

The project customer may have specific dates when phases of the project should be completed. These are often treated as project constraints.

Answer 35

Schedule milestones

Question 36

Undocumented, unapproved changes to the project scope.

Answer 36

Scope creep

Question 37

The formal inspection of the project
deliverables, which leads to project
acceptance.

Answer 37

Scope validation

Question 38

A scope definition process where the
project management team interviews the
stakeholders and categorizes, prioritizes,
and documents what the project
customer wants and needs. The analysis
is to determine, quantify, and prioritize
the interests of the stakeholders.
Stakeholder analysis demands
quantification of stakeholder objectives;
goals such as “good,” “satisfaction,” and
“speedy” aren’t quantifiable.

Answer 38

Stakeholder analysis

Question 39

A scope definition approach that studies
and analyzes a system, its components,
and the relationship of the components
within the system.

Answer 39

Systems analysis

Question 40

This project scope statement creation
process studies how a system should
work, designs and creates a system
model, and then enacts the working
system based on the project’s goals and
the customer’s expectations. Systems
engineering aims to balance the time and
cost of the project in relation to the scope
of the project.

Answer 40

Systems engineering

Question 41

A group decision method where everyone must be in agreement.

Answer 41

Unanimity

Question 42

As with value engineering, this approach
examines the functions of the project’s
product in relation to the cost of the
features and functions. This is where, to
some extent, the grade of the product is
in relationship to the cost of the product.

Answer 42

Value analysis

Question 43

This approach to project scope statement
creation attempts to find the correct level
of quality in relation to a reasonable
budget for the project deliverable while
still achieving an acceptable level of
performance of the product.

Answer 43

Value engineering

Question 44

A WBS companion document that
defines all of the characteristics of each
element within the WBS.

Answer 44

WBS dictionary

Question 45

A prepopulated WBS for repetitive
projects. Previous projects’ WBSs are
often used as templates for current
similar projects.

Answer 45

WBS template

Question 46

A deliverables-oriented breakdown of the projec scope.

Answer 46

Work breakdown structure (WBS)

Question 47

The smallest item in the WBS.

Answer 47

Work package

Question 48

Status of the deliverables: the work that’s
been started, finished, or has yet to
begin.

Answer 48

Work performance information