Brainscape's Knowledge GenomeTM

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


See full index

PMP Exam Prep > Ch 5 Project Scope Management > Flashcards

Ch 5 Project Scope Management Flashcards

1
Q

Create Work Breakdown Structure (WBS)

A

The process of breaking down the deliverables into smaller, more manageable components (decomposition)

The main output is the Scope Baseline

Knowledge Area: Scope

Process Group: Planning

Inputs:

  • Project Scope Statement

Tools:

  • Decomposition

Outputs:

  • Scope Baseline
    • WBS
    • WBS Dictionary
    • Project Scope Statement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Deliverable Life Cycle

A

Deliverables are:

  • Created (Direct and Mangage Project Work)
  • Verified (Control Quality)
  • Accepted (Validate Scope)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Control Scope

A

The process of monitoring the status of the project/product scope as it is executed to ensure that it aligns with the scope baseline, and also managing changes to the scope baseline

Knowledge Area: Scope

Process Group: Monitoring & Controlling

Inputs:

  • Work Performance Data

Tools:

  • Variance Analysis

Outputs:

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

Focus Groups

A

A data gathering method in which SMEs and stakeholders gather to participate in a moderated discussion about their project expectations

A tool used to help execute the Collect Requirements process (Scope/Planning)

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

Requirements Management Plan

A

The management plan that documents how the requirements will be collected, analyzed, documented, and managed

An output of the Plan Scope Management process (Scope/Planning)

An input to the Develop Project Management Plan process (Integration/Planning)

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

Validate Scope

A

The process in which the project deliverables are formally inspected and accepted by the customer or sponsor; if the deliverables are rejected, they return to the team as a defect for repair

This process should be done immedately after (but can be done at the same time as) the Control Quality process (Quality/M&C), where the project manager inspects and verifies the deliverable against the quality requirements

Knowledge Area: Scope

Process Group: Monitoring & Controlling

Inputs:

  • Verified Deliverables

Tools:

  • Inspection

Outputs:

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

Gold Plating

A

Doing extra work that is not in the scope baseline

This should never be done in project management because it can increase risk, cost, schedule problems, and quality problems

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

Requirements Documentation

A

Very detailed documentation of the actual requirements needed to complete the project

An output of the Collect Requirements process (Scope/Planning)

An input to the Define Scope process (Scope/Planning)

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

Project Scope Management

A

Knowledge area regarding management of project scope, aka the work required to complete the project

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

Product Analysis

A

A method of comparing of the product to the stakeholder requirements

A tool used to help execute the Define Scope process (Scope/Planning)

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

Verified Deliverables

A

A deliverable that has been inspected by the project manager to ensure that it meets the quality requirements

An output of the Control Quality process (Quality/M&C)

An input to the Validate Scope process (Scope/M&C)

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

Project Scope

A

The work that is needed to deliver a product, service, or result with specified features and functions

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

Brainstorming

A

A data gathering method that usually allows stakeholders to generate, gather, and document many ideas

A tool used to help execute the Collect Requirements process (Scope/Planning)

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

Variance Analysis

A

A data analysis method of determining if there is a variance between the planned work (project management plan) and the actual work (work performance data).

If so, the PM may need to submit a change request

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

Delphi Technique

A

A technique where requirements are collected anonymously from SMEs so that they cannot influence each other

Benefits of this technique:

  • Different geographical areas
  • Reduce individual bias
  • People may disclose risks they may not want to discuss in front of a group
  • Minimize group thinking

A tool used to help execute the Collect Requirements process (Scope/Planning)

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

Inspection

A

A method by which the project manager and/or team inspects deliverables to ensure that it meets quality requirements

A method by which the customer or sponsor validates that the deliverables meet their requirements

This can include walkthroughs, audits, or visual inspection

A tool (never an input or output) used to help execute the;

  • Control Quality process (Quality/M&C)
  • Validate Scope process (Scope/M&C)
  • Control Procurements process (Procurement/M&C)
17
Q

Facilitation

A

A method of bringing stakeholders together to gather requirements

Examples include:

  • A workshop or interactive discussion designed to quickly define requirements, solve differences, and build trust
    • Quality Function Deployment (QFD) is a requirements workshop used mostly in manufacturing

A tool used to help execute the Collect Requirements process (Scope/Planning)

18
Q

Product Scope

A

Features and functions that characterize a product, service, or result

Requirements for a product

19
Q

Nominal Group Technique

A

A technique that involves ranking and prioritizing the ideas from brainstorming

A tool used to help execute the Collect Requirements process (Scope/Planning)

20
Q

Plan Scope Management

A

The process of creating the scope and requirement management plans, which will document how the project will collect the requirements, as well as define, validate, and control the project scope

Knowledge Area: Scope

Process Group: Planning

Inputs:

  • Project Charter
  • (NOT the Stakeholder Register)

Tools:

  • None

Outputs:

  • Scope Management Plan
  • Require Management Plan
21
Q

Decomposition

A

A technique in which the high-level project deliverables from the scope statement are divided into smaller parts, known as work packages, to estimate time and cost for stakeholder acceptance

A technique used to break down the work packages on the WBS into specific activities that represent the work efforts needed to accomplish the work packages; multiple activities can be assigned to a work package

A tool used to help execute the:

  • Create WBS process (Scope/Planning)
  • Define Activities process (Schedule/Planning)
22
Q

Scope Baseline

A

One of the three baselines in the project management plan, this document has three components:

  • Work Breakdown Structure (WBS): A hierarchical graphic illustrating the work needed to produce the project deliverables (control accounts broken down into one or more work packages); provides a structure for integrating scope, schedule, and cost info
  • WBS Dictionary: A document with details about each work package in the WBS (e.g., detailed description of work, scheduling, cost estimates, assumptions, constraints, acceptance criteria); may be a series of tables, one for each work package
  • Project Scope Statement: the document that was used to create the WBS; an output of the Define Scope process and an input of the Create WBS process

The only output of the Create WBS process (Scope/Planning)

An input to the

  • Define Activities process (Schedule/Planning)
  • Plan Procurement Management process (Procurement/Planning)
23
Q

Scope Creep

A

Unapproved expansion of the scope (without control)

24
Q

Requirements Traceability Matrix

A

A table that is created to link the requirements back to their origin (e.g., who gave the requirement, why it was added to the project)

An output of the Collect Requirements process (Scope/Planning)

25
Q

Define Scope

A

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

Knowledge Area: Scope

Process Group: Planning

Inputs:

  • Project Charter
  • Requirements Documentation

Tools:

  • Data Analysis
  • Product Analysis

Outputs:

  • Project Scope Statement
26
Q

Voting

A

A type of decision making method to acheive one of the following:

  • Unanimity: everyone agrees
  • Majority: more than 50% of the group
  • Plurality: largest segment of a group (40/30/30)

A tool used to help execute the Collect Requirements process (Scope/Planning)

27
Q

Scope Management Plan

A

The management plan that documents how the project manager will write the scope statement, baseline the scope, control the scope, and get the scope accepted (validated)

An output of the Plan Scope Management process (Scope/Planning)

An input to the Develop Project Management Plan process (Integration/Planning)

28
Q

Prototypes

A

Models of a product that stakeholders can interact with to provide feedback regarding requirements

A tool used to help execute the Collect Requirements process (Scope/Planning)

29
Q

Project Scope Statement

A

A very detailed and important planning document that lists and describes all project deliverables and the work that will be required to produce them

  • Description of the product/project scope
  • Detailed list of the deliverables
  • Acceptance criteria
  • Exclusions (what the project will not do)
  • Constraints
  • Assumptions

The only output of the Define Scope process (Scope/Planning)

An input to the Create WBS process (Scope/Planning)

30
Q

Collect Requirements

A

The iterative process of defining and documenting stakeholders needs to meet the project objectives

Knowledge Area: Scope

Process Group: Planning

Inputs:

  • Project Charter
  • Stakeholder Register

Tools:

  • Data Gathering
    • Brainstorming
    • Focus Groups
    • Benchmarking
  • Decision Making
    • Voting Techniques
  • Data Representations
    • Affinity Diagrams
  • Interpersonal & Team Skills
    • Nominal Group Technique
    • Delphi Technique
    • Facilitation
  • Prototypes

Outputs:

  • Requirements Documentation
  • Requirements Traceability Matrix
31
Q

Affinity Diagram

A

A data representation method that allows many ideas to be put into groups

A tool used to help execute the Collect Requirements process (Scope/Planning)

32
Q

Benchmarking

A

A data gathering method that looks outside the project to provide a measurement of performance (e.g., within the organization, within other organizations, industry best practices)

A tool used to help execute the Collect Requirements process (Scope/Planning)

33
Q

Scope

A

The work required and only the work required to complete the project

34
Q

Mind Mapping

A

A data representation technique where ideas are drawn instead of written to help generate new ideas

A tool used to help execute the Collect Requirements process (Scope/Planning)

PMP Exam Prep (12 decks)

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