Plan And manage scope Flashcards

1
Q

Scope Management Plan

A

A component of the project or program management plan that describes how the scope will be defined, developed, monitored. controlled, and validated.

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

Project Requirements

A

The actions, processes, or other conditions the project needs to meet e.g. milestone dates, contractual obligations, constraints, etc.

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

Product Requirements

A

The agreed-upon conditions or capabilities of a product, service, or outcome the project is designed to satisfy.

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

Product Scope

A

The work performed to deliver a product, service or result with the specified features and functions. Project scope may include product scope.

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

Product Scope

A

The features and functions that characterize a product, service, or result.

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

Enterpise Environmental Factors (EEF)

A

Conditions (internal or external) not under the control of the project team, that influence, constrain, or direct the project at organizational, portfolio, program, or project level.

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

Organizatinal Process Assets (OPA)

A

Plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. These assets influence the management of the project.

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

Document Analysis

A

A technique used to gain project requirements from current documentation evaluation.

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

Focus Group

A

An elicitation technique that brings together prequalified stakeholdets and subject matter experts to elatn about their expectations and attitudes about a proposed product, service, or tesult.

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

Questionnaries and Surveys

A

Written format of questions designed to quickly capture Information from many respondents.

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

Benchmarking

A

The comparison of actual or planned products, processes, and practices to those of comparable organizations to identify best practices, generate ideas for improvement and provide a basis for measuring performance.

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

Interviews

A

a form or informal approach to elicit information from stakeholders by talking with them directly.

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

Observations

A

A technique used to gain knowledge of a specific job role, task, or function in order to understand and determine project requirements.

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

Facilitated Worskshops

A

Organized working sessions held by project managers to determine project requirements and to get all stakeholders together to agree on project outcomes.

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

Context Diagrams

A

Visual depiction of product scope showing a business system (process, equipment, computer system, etc.) and how people and other systems interact with it.

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

Storyboarding

A

A prototyping method using visuals or

images to illustrate a process or represent a project outcome.

17
Q

Prototyping

A

Assists in the process of obtaining early feedback on requirements by providing a working model of the expected product before building.

18
Q

Requirements Management Plan

A

A component of the project or program management plan that describes how requirements will be analyzed, documented and managed.

19
Q

Requirements Traceability Matrix

A

Links products requirements drom their origin to the deliverables that satisfy them.

20
Q

Project Scope Statement

A

The description of the project scope, major deliverables, assumptions, and constraints.

21
Q

Product Analysis

A

A tool to define scope by asking questions about a product and forming answers to describe the use, characteristics, and other relevant aspects of the product.

22
Q

Work Breakdown Structure

A

A hierarchical decomposition of a project’s total scope of work to accomplish project objectives and create the required deliverables.

23
Q

Code of Accounts

A

Numbering system tgat uniquely identifies each component of the WBS.

24
Q

WBS Dictionary

A

Provides detailed deliverable, activity, and scheduling ibformation about each component in the WBS.

25
Q

Decomposition

A

A technique of dividing and subdividing the project scope abde deliverables into smaller more manageable parts.

26
Q

Control Account

A

A management control point where scope budget, actual cost, and schedule are integrated and compared to earned value for performance measurement.

27
Q

Planning Package

A

A WBS component below the control account with known work content but without detailed schedule activities.

28
Q

Work Package

A

The work defined at the lowest level of the WBS for which cost and suratiob are estimated and managed.

29
Q

Scope Baseline

A

Approved version of a scope statement, WBS, and its associated WBS dictionary, that can be changed using formal change control procedures and is used as a basis for comparison to actual results.

30
Q

User Stories

A

Short descriptions of required functiobality tild fron user’s point of view.