All-In-One Chapter 5 - Managing the Project Scope Flashcards Preview

PMP Exam > All-In-One Chapter 5 - Managing the Project Scope > Flashcards

Flashcards in All-In-One Chapter 5 - Managing the Project Scope Deck (51):
1

8/80 Rule

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

2

Active observation

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.

3

Affinity diagrams

when stakeholders create a large number of ideas, you can use an affinity diagram to cluster similar ideas together

4

Alternatives generation

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

5

Brainstorming

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.

6

Change control system (CCS)

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

7

Change management plan

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

8

Code of accounts

a numbering system for each item in the WBS

9

Configuration management plan

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

10

Context diagram

these diagrams show the relationship between elements of an environment

11

Delphi technique

this approach uses rounds of anonymous surveys to build consensus. because the surveys are anonymous, participants are more likely to be honest with their requirements, opinions, and statements

12

Dictatorship

a decision method where only one individual makes the decision for the group

13

Focus group

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

14

Functional analysis

the study of the functions within a system, project, or 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

15

Funding limit

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

16

Initial project organization

the project scope statement identifies the project team and the key stakeholders

17

Interviews

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

18

Majority

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

19

Mind mapping

this approach maps ideas to show the relationship among requirements and the differences between requirements

20

Nominal group technique

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

21

Passive observation

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

22

Plurality

a group-decision method where the largest part of the group makes the decision when its less than 50 percent of the total

23

Product acceptance criteria

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

24

Product breakdown

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

25

Product scope description

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

26

Product scope

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

27

Project assumption

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

28

Project boundaries

clearly states what is included with the project and what's excluded from the project

29

Project constraints

anything that limits the project manager's options

30

Project objective

measurable goals that determine a project's acceptability to the project customer and the overall success of the project

31

Project requirements

the demands set by the customer, regulations, or the performing organization that mus exist for the project deliverables to be acceptable

32

Project scope

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

33

Project scope management plan

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

34

Prototype

a model of the finished deliverable that allows the stakeholder to see how the final project deliverable may operate

35

Requirements documentation

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

36

Requirements management plan

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

37

Requirements traceability matrix (RTM)

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

38

Schedule milestones

the project customer may have specific dates when phases of the project should be completed

39

Scope creep

undocumented, unapproved changes to the project scope

40

Scope validation

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

41

Stakeholder analysis

a scope definition process where the project management team interviews the stakeholders and categorizes, prioritizes, and documents what the project customer wants and needs

42

Systems analysis

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

43

Systems engineering

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

44

Unanimity

a group decision method where everyone must be in agreement

45

Value analysis

this approach examines the functions of the projects product in relation to the cost of the features and functions

46

Value engineering

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

47

WBS dictionary

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

48

WBS template

a prepopulated WBS for repetitive projects. Previous projects' WBSs are often used as templates for current similar projects

49

Work Breakdown Structure (WBS)

a deliverables-oriented breakdown of the project scope

50

Work package

the smallest item in the WBS

51

Work performance information

status of the deliverables: the work that's been started, finished or has yet to begin