10 - Project Scope Management Terminology Flashcards

1
Q

Acceptance

A

The process of formally receiving the work of the project, which should be complete and fulfill the objectives of the project.

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

Acceptance Criteria

A

The contingencies that must be satisfied prior to acceptance of work.

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

Accepted Deliverables

A

Products, results or capabilities that have been accepted by the customer as meeting requirements.

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

Affinity Diagram

A

A tool used to gather ideas and organize them into groupings so they can be reviewed and analyzed; typically used for ideas generated from brainstorming sessions.

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

Alternative Analysis

A

A technique used to evaluate project execution approaches.

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

Alternatives Generation

A

A technique used to create as many project execution approaches as possible.

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

Analogy Approach

A

A methodology for establishing values for the current project based on those from a previous project with similar characteristics; values obtained from this method include activity duration, required resources, and estimated costs.

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

Brainstorming

A

A creative technique used to gather a large amount of information from team members and/or subject matter experts; applicable to ideas, risk identification, and solutions.

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

Collect Requirements

A

The process of arranging for, determining, and documenting the needs of the stakeholders to align with project objectives.

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

Context Diagrams

A

A graphical representation of the scope of a business system that includes processes, equipment, and computer systems and indicates the manner in which people and other systems interact with the business system.

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

Control Scope

A

The process of observing project status and scope in order to administer scope baseline revisions.

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

Create WBS

A

The process of breaking down the work of the project into minimal components for more effective management.

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

Decomposition

A

The process of breaking down the work of the project into smaller, more controllable components.

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

Define Scope

A

The process of developing the project scope statement, the document that details the expected results of the project.

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

Delphi Technique

A

A technique used to gain concurrence from a group of experts about a specific issue; the technique is effected by using a questionnaire to solicit ideas from the experts, having the ideas summarized, having the experts add comments to the summaries, and repeating the process until a consensus is reached.

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

Diagramming Technique

A

A method that indicates the logical links between data.

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

Facilitated Workshop

A

A focused session involving cross-functional stakeholders and a designated leader that is conducted to achieve a specific goal, such as the creation of project requirements.

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

Focus Group

A

A focused session involving prequalified stakeholders, subject matter experts (SMEs), and a designated leader that is conducted to determine expectations and views regarding a potential product, service, or result.

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

Group Creativity Technique

A

A focused session involving stakeholders and a designated leader that is conducted to develop ideas.

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

Group Decision-Making Technique

A

A focused session involving stakeholders and a designated leader that is conducted to review decision methods available for use with specific activities such as generating, classifying, and prioritizing requirements.

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

Interviews

A

A focused session involving individual stakeholders and a designated leader that is conducted to elicit specific information.

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

Management by Objectives (MBO)

A

An administration method that aligns, or realigns, projects to strategic objectives.

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

Mind-mapping

A

A technique used to integrate ideas created through individual brainstorming sessions into a single map in order to highlight similarities and differences in understanding and generate new ideas.

24
Q

Nominal Group Technique

A

A technique, effected by a voting process, that is used to prioritize ideas by utility for further brainstorming.

25
Q

Plan Scope Management

A

The process of creating a document that designates how the project scope will be defined, validated, and controlled; the document may also offer guidance for requirements and include the scope statement, the work breakdown structure (WBS), and the scope baseline.

26
Q

Planning Package

A

A WBS component that has no detailed scheduled activities even though it is known to have work content.

27
Q

Plurality

A

The votes of the largest block in a group when a majority is not required, typically used to denote agreement with a decision.

28
Q

Product

A

An output of the project that is quantifiable and can be described as material and goods.

29
Q

Product Analysis

A

An approach used to convert a business-defined product into project deliverables; typically involves asking business representatives questions about the intended uses and characteristics of the product.

30
Q

Product Life Cycle

A

The phases of product development, typically defined as conception through delivery, expansion, maturity, and disengagement.

31
Q

Product Scope

A

The features and functions of a project’s product, service, or result.

32
Q

Product Scope Description

A

The documented depiction of the features and functions of a project’s product, service, or result.

33
Q

Project Scope

A

The work executed to deliver a product, service, or result that satisfies the specified features and functions.

34
Q

Project Scope Management

A

The processes required to ensure that all the work needed to complete the project, and only that work, is included in the project.

35
Q

Project Scope Statement

A

The document that describes the major deliverables, assumptions, constraints, and scope of the project.

36
Q

Prototype

A

A working model of the product created to obtain detailed stakeholder feedback.

37
Q

Questionnaires

A

Written surveys designed to quickly gather information from a large number of respondents.

38
Q

Requirement

A

A condition or capability that must be made available through a product, service, or result in order to fulfill a contract or formal specification.

39
Q

Requirements Documentation

A

A document that describes requirements for creating a product or a feature of the product.

40
Q

Requirements Management Plan

A

The document, part of the project or program management plan, used to describe the evaluation, recording, and administration of project requirements.

41
Q

Requirements Traceability Matrix

A

A graphical representation that illustrates the relationships between the origins of the product requirements to the deliverables that fulfill the requirements.

42
Q

Scope

A

The products, services, and results expected to be provided by the project.

43
Q

Scope Baseline

A

The authorized scope statement, WBS, and WBS dictionary that contain only those modifications authorized through a formal change control process; used as a basis for comparison.

44
Q

Scope Change

A

A change to the product or product scope accompanied by the appropriate modifications to the budget or schedule.

45
Q

Scope Creep

A

A change to the product or product scope not accompanied by the appropriate modifications to the budget or schedule.

46
Q

Scope Management Plan

A

The document, part of the project or program management plan, used to define the manner in which the project scope will be delineated, elaborated, monitored, controlled, and authenticated.

47
Q

Statement of Work (SOW)

A

A detailed description of the products, services, or results expected from a project or other initiative.

48
Q

Unanimity

A

A decision with which all group members concurred.

49
Q

User

A

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

50
Q

Validate Scope

A

The process in which the customer or sponsor reviews and accepts project deliverables as being complete and correct in accordance with the requirements.

51
Q

Validation

A

The process of determining that the results of the project are in compliance with requirements imposed by the customer and appropriate stakeholders and typically involving acceptance by them.

52
Q

WBS Dictionary

A

A document that itemizes deliverable, activity, and scheduling information for each WBS component.

53
Q

Work Breakdown Structure (WBS)

A

A decomposition of the work of the project.

54
Q

Work Breakdown Structure Component

A

Any unit of work defined in the WBS.

55
Q

Work Package

A

The smallest level of WBS work for which cost and schedule can be assessed and administered.