Scope Terminology Flashcards Preview

PMP > Scope Terminology > Flashcards

Flashcards in Scope Terminology Deck (41):
1

Acceptance

The process of formally receiving the work of the project: the work should be complete and fulfill the needs for which it was created.

2

Acceptance Criteria

Requirements that are defined to be completed before the work can be accepted

3

Affinity Diagram

Diagram that sorts and groups large numbers of brainstorming ideas for review and analysis

4

Analogy Approach

An approach in which a previous project of similar characteristic is used to obtain the values (duration, resources, budget, etc.) for the current project being planned

5

Bottom-up Approach

An approach in which the team or at least the project manager is involved in deciding on and estimating the individual pieces of the project to create the summary estimate

6

Brainstorming

A technique used with groups to generate a large number of ideas

7

Collect Requirements

The process of documenting the needs of the stakeholders that align with the project objectives

8

Control Scope

The process of maintaining and adjusting the scope of the project as approved

9

Create WBS

The process of dividing deliverables and work into smaller components for easier management

10

Decomposition (Technique)

The process of breaking down the work of the project into smaller more controllable pieces

11

Define Scope

The process of developing a project scope statement

12

Deliverable (Output/Input)

A key piece of work for the project; can be physical work, a process, a document, or other measurable result of work

13

Delphi Technique

A technique to attain consensus within a group of experts; typically used to gain vision about future direction or development

14

Dictatorship

Decision is made via one individual

15

Idea/Mind Mapping

A single map consolidating ideas created through individual brainstorming sessions

16

Majority

Decision is made via the consensus of more than 50% of group members

17

Milestone

A major achievement on a project; usually occurs after a series of activities leading up to its completion; has zero-days duration and could be related to a "deliverable"

18

Nominal Group Technique

Ranks the most useful brainstorming ideas for prioritization or further brainstorming

19

Planning Package

A component of the work breakdown structure that has known work but no detailed activities

20

Plurality

Decision is made via the consensus of the largest block of group members

21

Product

The measurable, definable work of the project

22

Project Scope

The work required to create the products, services, and or results of the project

23

Project Scope Management

Processes associated with determining and controlling what a project includes or does not include

24

Requirement

A need that must be completed to attain project goals; could be business or technical

25

Requirements Management Plan

Documents that help the project manager and team analyze, document, and manage the project requirements

26

Requirements Traceability Matrix

A matrix that shows the origin of project requirements and tracks them throughout the project life cycle

27

Scope

The desired outcome of the project; the work that will be encompassed in the project and the final product or service

28

Scope Baseline

Original (or approved revised) definition of the scope the project should create; can include project scope statement, work breakdown structure (WBS), and WBS dictionary

29

Scope Change

An approved change to the scope of the project

30

Scope Creep

Unauthorized request for change that usually occurs in a project as time evolves

31

Scope Management Plan

Document that explains how to establish a scope statement and requirements, create the WBS, validate that deliverables were built correctly, and address scope-related changes to the project

32

Top-down Approach

The point at which a WBS is created with the major (or bigger) pieces, then they are broken down into the smaller pieces

33

Unanimity

Decision is made via the consensus of all group members

34

User

The person, division, or company that will be the user or owner of the product when the project is complete

35

Validation (Technique)

The process of evaluating something that was created in the project to ensure that it meets the needed requirements for formal acceptance

36

Verification (Technique)

The process of evaluating something that was created in the project to ensure that it meets the specified conditions

37

Verify Scope

Gaining approval of the project scope deliverables as they are completed

38

WBS Dictionary

A tool that works with the WBS to ensure that the right work occurs in the right order by the correct resources ; helps improve the quality of work by verifying that the needed conditions have been met before future work begins

39

Work Breakdown Structure (WBS)

An organized breakdown of the total work scope of the project, with each level of descent providing a greater level of detail and the deliverable being a key focus

40

Work Breakdown Structure Component

A unit of work that makes up the work breakdown structure

41

Work Package

A deliverable at the smallest level of the WBS; represents the completed piece of the project from the culmination of a series of activities being complete