Scope Management

Question 1

Product Scope

Answer 1

Requirements for the final product

Question 2

Project Scope

Answer 2

work the project team will do to deliver the product of the project, including the product scope

Question 3

Inputs: Plan Scope Management

Answer 3

• Project Charter
• PM Plan
• EEFs
• OPAs

Question 4

Outputs: Plan Scope Management

Answer 4

• Scope Management Plan
• Requirements Management Plan

Question 5

Scope Management Plan

Answer 5

• how to achieve scope
• what tools to use to plan
• how to create the WBS
• how scope will be managed and controlled
• how to obtain acceptance of deliverables

Question 6

Requirements Management Plan

Answer 6

aka business analysis plan

outlines how requirements are analyzed, prioritized, managed, and tracked

Question 7

Types of Requirements

Answer 7

• how the work is planned and managed
• capabilities for product
• stakeholder requirements (from stakeholder register)
• quality measures
• business procedures (i.e. reporting of expenses)
• legal or ethical complaince
• project management procedures

Question 8

Inputs: Collect Requirements

Answer 8

• Project charter
• PM Plan
• Project docs
• Business docs
• Agreements
• EEFs
• OPAs

Question 9

Outputs: Collect Requirements

Answer 9

• Requirements documentation (including acceptance criteria)
• Requirements traceability matrix

Question 10

Affinity diagrams

Answer 10

Groups ideas for requirements by similarities; aid in determining whether all areas of scope have been identified

Also used for risks.

Question 11

Nominal Group Technique

Answer 11

• question or issue is posed
• all meeting particiapants write down and share their ideas
• group discussion
• ideas ranked

Question 12

Delphi Technique

Answer 12

requirements are collected anonymously from SMEs (to avoid stakeholders influencing each other)

Question 13

Facilitation

Answer 13

concensus-based approach that brings stakeholders with different perspectives to talk about the product & define reqirements.

user stories may be developed through facilitation

Question 14

Quality Functional Deployment

Answer 14

type of facilitation, aka voice of the customer

Question 15

Context Diagrams

Answer 15

shows boundaries of scope by highlighting the product and its interfaces with people, processes or systems

Question 16

Requirement Traceability Matrix

Answer 16

links requirements to the objectives to ensure strategic goals are accomplished

(may also link to stakeholders and origin of requirement)

Question 17

Inputs: Define Scope

Answer 17

• Project Charter
• PM Plan
• Project docs
• EEFs
• OPAs

Question 18

Outputs: Define Scope

Answer 18

• Project Scope Statement
• Project docs updates

Question 19

Project Scope Statement

Answer 19

douments the characteristics and boundaries of the project and its associated products, results, and services in addition to the acceptance criteria.

Question 20

Components of Project Scope Statement

Answer 20

Components may vary depending on project approach.

• product scope
• detailed list of deliverables*
• acceptance criteria
• exclusions
• constraints
• assumptions

* must be in all scope statements

Question 21

Scope Baseline

Answer 21

Scope statement, WBS, WBS dictionary

Question 22

Inputs: Create WBS

Answer 22

• PM Plan
• Project Docs
• EEFs
• OPAs

Question 23

Outputs: Create WBS

Answer 23

• Scope Baseline
• Project docs update

Question 24

Levels of WBS

Answer 24

Project

Control Accounts

Work Packages

Note: Work Packages should be work products or deliverables, NOT activities.

Question 25

Difference between task and activity

Answer 25

**activity:** particular piece of work scheduled for the project **tasks:** smaller components of work that make up an activity

Question 26

WBS

Answer 26

a graphical picture of the hierarchy of a porject identifies **all** deliverables to be completed does not show dependencies

Question 27

PM uses for WBS

Answer 27

* to determine appropriateness of scope-related change request * evaluate impact of changes that relate to scope * control scope creep * communicatins tool * onboarding of team members

Question 28

WBS Dictionary

Answer 28

provides a desription of the work to be done for each WBS work package + acceptance criteria for each deliverable

Question 29

Inputs: Validate Scope

Answer 29

* PM Plan * Project docs * Verified Deliverables * Work Performance Data

Question 30

Outputs: Validate Scope

Answer 30

* Accepted deliverables * Change requests * Work Performance Information * Project docs updates

Question 31

Validate Scope

Answer 31

process where deliverables are formally inspected and accepted by the customer or sponsor. occurs immediately after Control Quality

Question 32

What is the difference between acceptance in Validate Scope & Close Project or Phase?

Answer 32

Validate Scope = (interim) deliverables acceptance Close Project or Phase = final project acceptance

Question 33

Inputs: Control Scope

Answer 33

* PM plan * Project docs * Work Performance Data * OPAs

Question 34

Outputs: Control Scope

Answer 34

* Work Performance Information * Change Requests * PM Plan updates * Project docs updates * OPAs updates

Question 35

What process includes testing of interim deliverables?

Answer 35

Control Scope