Plan Scope Management
Collect Requirements
Define Scope
Create WBS
Validate Scope
100

The work performed to deliver a product, service, or result with the specified features and functions. 

What is Project Scope?

100

Assumption log, lessons learned register and stakeholder register.

What are Project Documents? 

100

This project document contains response strategies that may affect the project scope, such as reducing or changing project and product scope to avoid or mitigate risk. 

A repository in which outputs of the risk management processes are recorded.

What is a Risk Register? 

100

A 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. 

This also organizes and defines the total scope of the project and represents the work specified in the currently approved project scope statement. 

What is a WBS? 

100

A measure that is compared to actual results to determine if a change, corrective action, or preventive action is necessary.

What is the Scope Baseline?

200

A document that has the project purpose, high-level project description, assumptions, constraints, and high-level requirements that the project is intended to satisfy. 

What is the Project Charter?

200

Factors that can influence the Collect Requirements process include but are not limited to: Organizational culture, Infrastructure, Personnel administration, and Marketplace conditions. 

What are Enterprise Environmental Factors? 

200

A tool/technique that should be considered from individuals or groups with knowledge of or experience with similar projects.

What is expert judgment? 

200

Plans, policies, procedures, and templates for the WBS, Project files from previous projects; and lessons learned from previous projects.

What are Organizational Process Assets? 

200

Project deliverables that are completed and checked for correctness through the control quality process.

What are Verified Deliverables? 

300

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

What is a Project Life Cycle?

300

Data representation that consolidates ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas. 

What is Mind Mapping?

300

Where additional information on existing or new stakeholders is gathered/recorded.

What is a Stakeholder Register?

300

The work defined at the lowest level in the work breakdown structure with a unique identifier for which cost and duration are estimated and managed. 


What is a work package?

300

Reviews, product reviews, and walkthroughs; activities such as measuring, examining, and validating to determine whether work and deliverables meet the requirements and product acceptance criteria.

What is an Inspection?

400

This "plan" includes a process that enables the creation of the WBS from the detailed project scope statement. 

What is the Scope Management Plan?

400

A type of diagram that illustrates the product scope by showing a business system (process, equipment, computer system, etc.) and how people and other systems (actors) interact with it. 

What is a context diagram? 

400

This analysis can be used to defined products and services. It included asking questions about a product or service and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be delivered. 

What is Product Analysis? 

400

A document that provides detailed deliverables, activity, and scheduling information about each component in the WBS. 

What is a WBS dictionary? 

400

Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor. Formal documentation received from the customer or sponsor acknowledging formal stakeholder acceptance of the project's deliverables is forwarded to the Close Project or Phase Process.

What are Accepted Deliverables?

 

500

This plan included configuration management activities such as: how changes will be initiated; how impacts will be analyzed; how they will be traced, tracked and reported; as well as the authorization levels required to approve these changes. 

What is the Requirements Management Plan?

500
A grid that links product requirements from their origin to the deliverables that satisfy them. It also provides a structure for managing changes to the product scope. 

What is a Requirements Traceability Matrix?

500

A formal proposal to modify a document, deliverable, or baseline. 

What is a Change Request? 

M
e
n
u