Chapter 5 Managing The Project Scope

Question 1

Affinity diagram

Answer 1

Clusters similar ideas together and allows for decomposition of ideas to compare and contrast project requirements.

Question 2

Brain storming

Answer 2

A group creativity technique to express as many ideas as possible about project requirements.

Question 3

Decomposition

Answer 3

The breakdown of the project scope statement into the project’s work breakdown structure. The smallest item of the project’s decomposition into the WBS is called the work package.

Question 4

Delphi technique

Answer 4

A consensus-building group creativity technique that uses rounds of anonymous surveys during requirements elicitation. The Delphi Technique may also be used during risk assessment.

Question 5

Dictatorship

Answer 5

A group decision process where the person with the most power forces the decision, even though the rest of the group may oppose the decision.

Question 6

Facilitated workshop

Answer 6

A collection of stakeholders from around the organization that come together to analyze, discuss, and determine the project requirements.

Question 7

Focus group

Answer 7

A conversation of stakeholders led by a moderator to elicit project requirements.

Question 8

Function analysis

Answer 8

Related to value engineering, this allows team input to the problem, institutes a search for a logical solution, and tests the functions of the product so the results can be graphed.

Question 9

Interviews

Answer 9

A requirements elicitation process to collect requirements from the project stakeholders.

Question 10

Majority

Answer 10

A group decision process where a vote is offered and the majority wins.

Question 11

Mind mapping

Answer 11

A visual representation of like and opposing ideas, thoughts, and project requirements.

Question 12

Nominal group technique

Answer 12

A group creativity technique that follows the brainstorming model but ranks each brainstorm idea.

Question 13

Observation

Answer 13

A requirements elicitation process where the observer shadows a person to understand how she completes a process. An observer may be a participant observer or an invisible observer.

Question 14

Plularity

Answer 14

A group decision process approach that allows the biggest section of a group to win even if a majority doesn’t exist.

Question 15

Product scope

Answer 15

The attributes and characteristics of the deliverables the project is creating.

Question 16

Project scope statement

Answer 16

The definition of what the project will create for the project stakeholders. The project scope statement includes the product scope description, product acceptance criteria, project deliverables, project exclusions, project assumptions, and project constrains.

Question 17

Prototype

Answer 17

A mockup of the project deliverable to confirm, adapt, or develop the project requirements.

Question 18

Quality function

Answer 18

A philosophy and a practice to fully understand customer needs–both spoken and implied–without gold-plating the project deliverables.

Question 19

Requirements documentation

Answer 19

A clearly defined explanation of the project requirements. The requirements must be measurable, complete, accurate, and signed off by the project stakeholders.

Question 20

Requirements management plan

Answer 20

Defines how requirements will be managed throughout the phases of the project. This plan also defines how any changes to the requirements will be allowed, documented, and tracked through project execution.

Question 21

Requirements traceability matrix

Answer 21

A table that helps the project team identify the characteristics and delivery of each requirement in the project scope.

Question 22

Scope baseline

Answer 22

Comprised of the project scope statement, the work breakdown structure, and the WBS dictionary.

Question 23

Scope management plan

Answer 23

Explains how the project scope will be managed and how scope changes will be factored into the project plan. Based o the conditions of the project, the project work, and the confidence of the project scope, the scope management plan should also define the likelihood of changes to the scope, how often the scope may change, and how much the scope can change.

Question 24

Scope verification

Answer 24

An inspection-driven process led by the project customer to determine the exactness of the project deliverables. Scope verification is a process that leads to customer acceptance of the project deliverables.

Question 25

Systems engineering

Answer 25

Focuses on satisfying the customers’ needs, cost requirements, and quality demands through the design and creation of the product. There is an entire science devoted to systems engineering in various industries.

Question 26

Unanimity

Answer 26

A group decision process where all participants are in agreement.

Question 27

Value analysis

Answer 27

Similar to value engineering, this focuses on the cost/quality ratio of the product. Value analysis focuses on the expected quality against the acceptable cost.

Question 28

Value engineering

Answer 28

Deals with reducing costs and increasing profits, all while improving quality. Its focus is on solving problems, realizing opportunities, and maintaining quality improvement.

Question 29

Voice of the customer

Answer 29

The initial collection of customer requirements that serves as part of quality function deployment in a facilitated workshop.

Question 30

Work breakdown structure

Answer 30

A decomposition of the project scope statement into work packages. The WBS is an input to seven project management processes; developing the project management plan, defining the project activities, estimating the project costs, determining the project budget, planning the project quality, identifying the project risks, and planning the project procurement needs.

Question 31

Work breakdown structure dictionary

Answer 31

A companion to the WBS, this document defines all of the characteristics of each element of the WBS.

Question 32

Work breakdown structure templates

Answer 32

Based on historical information, this is a WBS from a past project that has been adapted to the current project.