Project Scope Management Terms Flashcards

1
Q

8/80 Rule

A
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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Active observation

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Affinity diagrams

A

When stakeholders create a large
number of ideas, you can use an affinity
diagram to cluster similar ideas together
for further analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Alternatives generation

A
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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Autocratic

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Brainstorming

A
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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Change control system (CCS)

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Change management plan

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Code of accounts

A
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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Configuration management plan

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Context diagram

A
These diagrams show the relationship
between elements of an environment. For
example, a context diagram would
illustrate the networks, servers,
workstations, and people that interact
with the elements of the environment.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Focus groups

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Functional analysis

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Funding limit

A
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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Interviews

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Majority

A

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

17
Q

Mind mapping

A
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.
18
Q

Nominal group technique

A

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

19
Q

Passive observation

A

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

20
Q

Plurality

A

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.)

21
Q

Product acceptance criteria

A
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
22
Q

Product breakdown

A

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

23
Q

Product scope description

A

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

24
Q

Product scope

A

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

25
Q

Project assumptions

A

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

26
Q

Project boundaries

A
A project boundary 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.
27
Q

Project constraints

A
A constraint 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—
these are all examples of project
constraints.
28
Q

Project objectives

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

Project requirements

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

Project scope

A

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

31
Q

Project scope management plan

A
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
32
Q

Requirements documentation

A

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.

33
Q

Requirements management plan

A
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
34
Q

Requirements traceability matrix (RTM)

A

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

35
Q

Schedule milestones

A

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

36
Q

Scope creep

A

Undocumented, unapproved changes to

the project scope.

37
Q

Scope validation

A

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