Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

CAPM 6th Edition > Chapter 5 > Flashcards

Chapter 5 Flashcards

1
Q

process of creating a scope management plan that documents how the project and project scope will be defined, validated, and controlled

A

Plan Scope Management

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

process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives

A

Collect Requirements

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

The process of developing a detailed description of the project and product

A

Define Scope

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

Process of subdividing project deliverables and project work into smaller, more manageable components

A

Create WBS

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

process of formalizing acceptance of the completed project deliverables

A

Validate Scope

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

process of monitoring the status of the project and product scope and managing changes to the scope baseline.

A

Control Scope

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

The features and functions that characterize a product, service, or results

A

Product Scope

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

the work performed to deliver a product, service, or result the specified feature and functions.

A

Project Scope

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

_______ define deliverables at the beginning while ________ are defined over multiple iterations.

A

1) Predictive

2) Adaptive/Agile

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

Scope: Three processes repeated at each iteration.

A

1) Collect requirements
2) Define Scope
3) Create WBS.

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

validate scope and control scope repeated at each iteration

A

Adaptive/Agile

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

Validate scope occurs at each deliverable or phase review and control scope is ongoing

A

Predictive

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

Scope Baseline Predictive has:

A
  • approved version of the project scope statement.
  • work break down structure (WBS)
  • Its associated WBS Dictionary
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.

A

WBS (Work Break-Down Structure)

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

lowest level of WBS component that contains planned work and used to group activities where work is scheduled, estimated, monitored, and controlled.

A

Work Packages

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

contains highest level of info. Includes the purpose, measurable objectives.

A

Project Charter

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

contains detailed description of the scope component. Includes project scope description, deliverables, acceptance criteria, and project exclusions.

A

Project Scope Statement

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

Uses decision matrix to provide a systematic analytical approach for establishing criteria in order to refine the project and product scope for the project

A

Multicriteria decision analysis

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

defines product and services; describes use, characteristics, and other relevant aspects of what is going to be delivered. Involves: Product Breakdown, Required Analysis, System Analysis, System Engineering, Value analysis, value engineering.

A

Product Analysis

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

1) Starts with needs assessment;
2) Then collaborating with business analysis for determining problems/business needs, identify viable solutions; elicit, document, and manage stakeholder requirements; facilitate successful implementation.
3) Requirements closure- transitions the product/service/result to the recipient to measure, monitor, sustain, and realize benefits over time.

A

Requirements Management Process

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

Quality policies, methodologies, and standards are implemented on the project

A

Quality Management Plan

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

Determines the series of phases that a project passes through from its inception to the end of the project

A

Project Life Cycle Description

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

Defines whether waterfall, iterative, adaptive, agile, or hybrid approach will be used.

A

Development Approach

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

Component of the PM Plan that describes how a project and product required will be analyzed, documented, and managed. *How requirement activities will be planned, tracked, and reported.

A

Requirements Management Plan (Business Analysis Plan)

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

the process of determining, documenting, and managing stakeholder needs and requirements to meet objectives.
* Provides basis for defining the product scope and project scope.

A

Collect Requirements

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

Contains info on how the project scope will be defined and developed.

A

Scope management plan

27
Q

info on how the project requirements will be collected, analyzed, and documented.

A

Requirements plan

28
Q

Used for understanding stakeholder communication requirements and level of stakeholder engagement and assess how to adapt level of stakeholder participation in required activities.

A

Stakeholder engagement plan

29
Q

can describe required, desired, and optional criteria for meeting the business needs.

A

Business case

30
Q
  • organizational culture
  • infrastructure
  • personnel administration
  • Marketplace conditions
A

Collection Requirement- Enterprise Environmental factors

31
Q

Policies, procedures, historical info and lessons learned repository.

A

Organizational Process Assets

32
Q

Data Gathering

A 
Brainstorming
interviews
focus groups
questionnaires and surveys
benchmarking
33
Q

decision reached whereby the largest block decides, even if majority is not achieved. Used when more than two options.

A

Plurality

34
Q

Sole Source decision

A

Autocratic Decision making

35
Q

Decision making using decision matrix providing systematic analytical approach for establishing criteria

A

multicriteria decision making

36
Q

Allow large numbers of ideas to be classified into groups

A

Affinity diagram

37
Q

consolidates ideas created through individual brainstorming session

A

Mind Mapping

38
Q

enhances brainstorming with the voting process used to rank the most useful ideas for further brainstorming and prioritization.

A

Nominal Group Technique

39
Q

define cross functional requirements and reconcile stakeholder differences

A

Workshops

40
Q

Facilitation Skill (JAD)

A

Joint application design/development- business subject matter experts and dev team to gather requirements and improv software dev processes.

41
Q

Facilitation Skill (QFD)

A

Helps Determine critical characteristics for new product development

42
Q

short/textual descriptions of required functionality often dev during required workshops. Describe stakeholder roles, who benefits from features (role), what stakeholders need to accomplish (Goal), and benefit to stakeholder (Motivation)

A

User Stories

43
Q

Visually depicts the product scope by showing a business system (process, equipment, computer system, etc.) and how people and other systems (actors) interact with it.

A

Context Diagram

44
Q

Two categories of Requirement Types

A

business solutions

technical solutions

45
Q

describe features, functions, characteristics of the product/service/result that will meet the business and stakeholder requirements

A

Solutions Requirements

46
Q

describes the behaviors of a product, actions, processes, data, and interactions that the product should execute.

A

Functional Requirement

47
Q

supplement functional requirement and describe the environment conditions or qualities required for the product to be effective.

A

nonfunctional Requirements

48
Q

describe temporary capabilities, such as data conversion and training requirements needed to transition from the current state as-is state to the desired future state.

A

Transition and readiness requirements

49
Q

describes actions, processes, or other conditions the project needs to meet: milestone dates, contractual obligations, constraints, etc.

A

Project requirements

50
Q

capture any condition or criteria needed to validate the successful completion of project deliverables or fulfill other project requirements: Tests, certifications, validations, etc.

A

Quality Requirements

51
Q

Grid that links product requirements to their origin to the delivery that satisfy them.

A

Requirements Traceability Matrix

52
Q

Detailed Project Scope statement includes:

A
  • Product scope statement
  • acceptance criteria
  • deliverables
  • project exclusions
53
Q

WBS Structure Methods:

A
  • Top-down approach
  • Organization specific guidelines
  • WBS Template
  • Bottom-up approach- used to group subcomponents
54
Q

Represent verifiable products/services/results

A

WBS Components

55
Q

WBS Structures

A
  • Outlined, organizational chart, or other methods identifying hierarchical breakdown.
56
Q

Project Management team agrees on deliverables and subcomponents before the details of the WBS can be delivered.

A

Rolling Wave Planning

57
Q

WBS represents

A

All product and project work including PM work

58
Q

Total of work at lowest level should roll up to the higher levels so that nothing is left out nd no extra work is performed.

A

100 percent rule

59
Q

the approved version of a scope statement, WBS, and its associated WBS Dictionary, which can be changes only through formal change control procedures and used as a basis for comparison

A

Scope Baseline

60
Q

A work break-down structure component below the control account and above the work package with known work content but without detailed scheduled activities.

A

Planning Package

61
Q

a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS

A

WBS Dictionary

62
Q

the uncontrolled expansion to product or project scope without adjust to time, cost, resources.

A

Scope Creep

63
Q

Correlated and contextual information on how the project/product scope are performed compared to scope baseline. Include:

  • Categories of change received
  • Identified scope variances
  • impacts to schedule or cost
  • forecast of future scope performance.
A

Work Performance Information

CAPM 6th Edition (11 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions