Chapter 5

Question 1

8/80 Rule

Answer 1

A plannning heuristic for creating the WBS. Min of 8 hours, max of 80 per work package.

Question 2

Active observation

Answer 2

Asks questions during job shadowing

Question 3

Affinity Diagrams

Answer 3

diagram that clusters a large number of similar ideas together for further analysis

Question 4

alternatives generation

Answer 4

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

Question 5

autocratic

Answer 5

one individual makes the decision

Question 6

brainstorming

Answer 6

duh

Question 7

Change control system (CCS)

Answer 7

defines how changes to the project scope are managed and controlled (documented in scope mgmt plan)

Question 8

change management plan

Answer 8

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

Question 9

code of accounts

Answer 9

numbering system for each item in the WBS. ex. Deliverable 1.1.1

Question 10

configuration management plan

Answer 10

A subsidiary plan that defines how changes to the features and functions of the project deliverable will be monitored and controlled within the project.

Question 11

context diagram

Answer 11

diagrams that 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.

Question 12

Focus groups

Answer 12

duh

Question 13

functional analysis

Answer 13

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

Question 14

funding limit

Answer 14

A feature of most projects, in which a budget is determined in relation to the project scope. The budget may include a qualifier, such as plus or minus 10 percent based on the type of cost estimate created.

Question 15

interviews

Answer 15

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

Question 16

Majority

Answer 16

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

Question 17

Mind Mapping

Answer 17

An approach that 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.

Question 18

nominal group technique

Answer 18

A technique similar to brainstorming, in which participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process.

Question 19

passive observation

Answer 19

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

Question 20

pluarility

Answer 20

group-decision method - largest part of group makes decision, when less than 50% available.

Question 21

product acceptance criteria

Answer 21

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

Question 22

product breakdown

Answer 22

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

Question 23

Product scope

Answer 23

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

Question 24

product scope description

Answer 24

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

Question 25

project assumptions

Answer 25

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

Question 26

Project Boundary

Answer 26

States what is included within the project and what’s excluded from the project. This helps to eliminate assumption between the project management team and the project customer.

Question 27

Project constraints

Answer 27

anything that limits the project manager’s options

Question 28

Project objectives

Answer 28

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.

Question 29

project requirements

Answer 29

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

Question 30

Project scope

Answer 30

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

Question 31

Project scope management plan

Answer 31

A project management subsidiary plan that 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.

Question 32

requirements documentation

Answer 32

Documentation of what the stakeholders expect in the project that defines all of the requirements that must be present for the work to be accepted by the stakeholders.

Question 33

requirements management plan

Answer 33

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

Question 34

Requirements traceability matrix (RTM)

Answer 34

A table that maps the requirements throughout the project all the way to their completion.

Question 35

schedule milestones

Answer 35

Specific dates established by the customer that set when phases of the project should be completed. Milestones are often treated as the project constraints.

Question 36

scope creep

Answer 36

Undocumented, unapproved changes to the project scope.

Question 37

scope validation

Answer 37

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

Question 38

stakeholders analysis

Answer 38

A scope definition process in which the project management team interviews the stakeholders and categorizes, prioritizes, and documents what the project customer wants and needs. The analysis determines, quantifies, and prioritizes the interests of the stakeholders. Stakeholder analysis demands quantification of stakeholder objectives; goals such as “good,” “satisfactory,” and “speedy” aren’t quantifiable.

Question 39

systems analysis

Answer 39

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

Question 40

systems engineering

Answer 40

A project scope statement creation process that 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.

Question 41

unanimity

Answer 41

A group decision method in which everyone must be in agreement.

Question 42

value analysis

Answer 42

Similar to 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.

Question 43

value engineering

Answer 43

An approach to project scope statement creation that 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.

Question 44

WBS dictionary

Answer 44

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

Question 45

WBS Template

Answer 45

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

Question 46

work breakdown structure (WBS)

Answer 46

A deliverables-oriented breakdown of the project scope.

Question 47

work package

Answer 47

The smallest item in the WBS.

Question 48

work performance information

Answer 48

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