Scope Management

Question 0

Which tool includes how the project scope will be defined and managed throughout the project (i.e. developed, monitored, controlled, and validated)?

Answer 0

Scope Management Plan

Question 1

What tool documents how requirements will be analyzed, documented, and managed throughout the project?

Answer 1

Requirements Management Plan

Question 2

What are the three tools that can be used to collect requirements?

Answer 2

Interview
Focus Groups
Facilitated Workshops

Question 3

In collecting requirements Group Creativity Techniques” can be used. Name the 4 techniques?

Answer 3

Brainstorming
Nominal Group (Brainstorming using a ranking system)
Idea/Mind Mapping
Affinity Diagram (used for sorting ideas into groups)

Question 4

What is a Context Diagram and when is it used?

Answer 4

During Requirements Gathering - its a visually depicted model of the product scope by showing a business system and how people and other systems interact with it. (Input/Outputs from a computer system as an example)

Question 5

What provides a documented basis for future project decisions regarding the project and product scope?

Answer 5

Project Scope Statement

Question 6

What are the key components for the Project Scope Statement?

Answer 6

Product Scope Description
Acceptance Criteria
Assumptions
Constraints
Exclusions
Deliverables

Question 7

What is the chief difference between information in the project charter pertaining to Assumptions, Constraints, acceptance, and other items, and the project scope statement?

Answer 7

The Project Charter is high level and the Scope Statement is progressively elaborated and validated (and updated) throughout the project.

Question 8

What is the Scope Baseline?

Answer 8

It is the approved project scope and is used during scope change management to determine and prevent scope creep. The Scope Baseline primarily comprises the project scope statement, WBS, and WBS Dictionary.

Question 9

What is the WBS Dictionary?

Answer 9

It describes each WBS Component in the work breakdown structure. The format and structure of the description per component may vary based on org practices and project guidelines but generally should cover: code of accounts, identifier, scope description for the component, inputs/outputs and deliverables