Scope Management Knowledge Area

Question 1

Project vs Product Scope

Answer 1

product scope is the features and functions the final product must have or be; project scope is the work required to deliver the final product

Question 2

Define Scope Completion

Answer 2

project scope is measured against the project management plan while product scope is measured against project requirements

Question 3

Agile/Adaptive Environments

Answer 3

adaptive life cycles use backlogs (represented as product requirements and user stories) whereas predictive projects would use a WBS and WBS dictionary; scope may not be clear or may dynamically change and therefore backlogs, releases and prototypes are used as requirement emerge over time

Question 4

Define Value Engineering

Answer 4

an approach used to optimize project life cycle costs, save time, increase profits, improve quality, expand market share, solve problems, and/or use resources more efficiently

Question 5

Data Gathering Techniques

Answer 5

Brainstorming, Focus Groups, Benchmarking, Document Analysis, Observation/Conservation

Question 6

Group Decision Making Techniques

Answer 6

Unanimity (all agree)
Majority (over 50%)
Plurality (largest block)
Aristocratic (one person decides)
Consensus (all agree to go along, even if its not their first choice)
Delphi Technique (blind, anonymous)

Question 7

Define Project Scope Statement

Answer 7

Describes in detail the project’s deliverables and the work required to create those deliverables; it contains explicit project inclusions and exclusions, acceptance criteria, assumptions and constraints

Question 8

Define Decomposition

Answer 8

the process of continually breaking down project deliverables into small parts to the point where activity costs and durations can be reliably estimated and managed

Question 9

Define WBS

Answer 9

Work Breakdown Structure;
a hierarchical decomposition of the work to be completed on a project; each lower level represents an increasingly detailed definition of the work; lowest level is the work package; each node has a unique identifier

WBS Dictionary: provides a detailed description of each WBS component

Question 10

Define Scope Baseline

Answer 10

includes the WBS, WBS Dictionary, Project Scope Statement, Work Packages and Planning Packages

Question 11

Inputs of Plan Scope Management

Answer 11

Project Charter
Project Management Plan
EEFS/OPAs

Question 12

Tools and Techniques of Plan Scope Management

Answer 12

Expert judgment, data analysis, meetings

Question 13

Outputs of Plan Scope Management

Answer 13

Scope management plan; requirements management plan

Question 14

Inputs, T&Ts, Outputs of Collect Requirements

Answer 14

Inputs: Project charter, project management plan, project documents, business documents, agreements, EEF/OPA

T&T: Expert judgment, data gathering, data analysis, decision making, data representation, interpersonal and team skills, context diagram, prototypes

Outputs: requirements documentation, requirements traceability matrix

Question 15

Inputs, T&Ts, Outputs of Define Scope

Answer 15

Inputs: Project charter, project management plan, project documents, EEF/OPAs

T&Ts: expert judgment, data analysis, decision making, interpersonal and team skills, product analysis

Outputs: project scope statement, project documents updates

Question 16

Inputs, T&Ts, Outputs of Create WBS

Answer 16

Inputs: Project management plan, project documents, EEF/OPAs

T&Ts: Expert judgment, decomposition

Outputs: Scope baseline, project documents updates

Question 17

Inputs, T&Ts, Outputs of Validate Scope

Answer 17

Inputs: Project Management Plan, project documents, verified deliverables, work performance data

T&Ts: inspection, decision making

Outputs: Accepted deliverables, work performance information, change requests, project documents updates

Question 18

Inputs, T&Ts, Outputs of Control Scope

Answer 18

Inputs: Project management plan, project documents, work performance data, OPAs

T&Ts: data analysis

Outputs: work performance information, change requests, project management updates, project documents updates

Question 19

Define Affinity Diagrams

Answer 19

Data representation technique; Affinity diagrams allow large numbers of ideas to be classified into groups for review and analysis

Question 20

Define Mind Mapping

Answer 20

Data representation technique; consolidates ideas created through individual brainstorming sessions into a single map to reflect commonality and difference in understanding and to generate new ideas

Question 21

Joint Application Design/Development (JAD)

Answer 21

used in the SOFTWARE development; facilitated sessions focus on bringing business subject matter experts and dev team together to gather requirements and improve the software development process (Interpersonal and Team Skills (T&T))

Question 22

Quality function deployment (QFD)

Answer 22

MANUFACTURING industry; facilitation technique that helps determine critical characteristics for new product development. (Interpersonal and Team Skills (T&T))

Question 23

Requirements Management Plan

Answer 23

Describes how the project and product requirements will be analyzed, documented and managed

Question 24

Requirements Documentation

Answer 24

describes how individual requirements meet the business need for the project.

Question 25

Requirements Traceability Matrix

Answer 25

A grid that links products requirements from their origin to the deliverables that satisfy them. Also, provides a structure for managing changes to the product scope

Question 26

Define control account

Answer 26

a management control point where scope, budget and schedule are integrated and compared to the earned value for performance measurement.

Question 27

Define planning package

Answer 27

a WBS component below the control account and above the work package with known work content but without detailed schedule activities

Question 28

Define code of accounts

Answer 28

a numbering system used to uniquely identify each component of the WBS

Question 29

Components of Activity List

Answer 29

Activity identifier and scope of work description for each activity in sufficient detail

Question 30

Mandatory Dependency

Answer 30

(also called Hard Logic or a Firm Dependency) means that two tasks absolutely must occur in a particular sequence, whether because of physics, the law, etc.

Question 31

Discretionary Dependency

Answer 31

does not have to be that way, thus it is a Discretionary Dependency (also called Soft Logic or Preferential Logic)

Question 32

What is the purpose of the Validate Scope process?

Answer 32

To provide formal acceptance of the completed project deliverables