The document discusses the six processes of scope management: plan scope management, collect requirements, define scope, create work breakdown structure (WBS), validate scope, and control scope. It provides key points about each process, including that plan scope management establishes how scope will be defined, validated and controlled throughout the project. Collect requirements determines stakeholder needs in detail. Define scope establishes requirement boundaries. The WBS breaks down all work into manageable parts and is critical for estimating and tracking project progress. Validate scope involves formal acceptance of deliverables. Control scope monitors project status against the scope baseline to prevent uncontrolled changes.

1. Scope Management
Chapter 5
“Is the process of defining what work is required and making sure all of that work &
only that work is done successfully.”
• “Completion of the project scope is measured against the PMP.”
• “Completion of the product scope is measured against the product requirements.”
Process Process Group Key Deliverables
5.1 Plan Scope Management Planning Scope Management Plan
5.2 Collect Requirements Planning Requirements Document
5.3 Define Scope Planning Project Scope Statement
5.4 Create WBS Planning WBS, WBS Dictionary
5.5 Validate Scope Monitoring & Controlling Acceptance Deliverables
5.6 Control Scope Monitoring & Controlling Change Requests

2. Scope Management
Chapter 5
Plan Scope Management
Process 1
Key Points
 “Documents how the project scope is defined, validated, controlled & managed throughout the project”
 Process generates 2 management plans that both become part of the PMP
 “The plan helps to reduce the risk of project scope creep”

3. Scope Management
Chapter 5
Collect Requirements
Process 2
Key Points
 Is the process of determining & documenting stakeholder’s needs & requirements in detail
 Critical to project’s success as missed requirements could mean major changes & conflicts

4. Scope Management
Chapter 5
Collect Requirements
Process 2
Key Points
 Project manager chooses the best Tools & Techniques to gather info:
 Interviews, Focus Groups, Facilitated Workshops,
 Brainstorming; Nominal, Multicriteria Analysis, Affinity diagram, Mind Maps
 Group Decision; Unanimity/Delphi Tech, Majority, Plurality, Dictatorship, Consensus
 Questionnaires, Surveys, Observations, Prototypes, Benchmarking
 Context Diagrams, Document Analysis
 Requirements Documentation: Acceptance Criteria used to set Scope Baseline
 Requirements Traceability Matrix: “helps to ensure each req. adds value by linking to a
project objective”

5. Scope Management
Chapter 5
Define Scope
Process 3
Key Points
 The process of developing a detailed description of the project & product/deliverable
 Defines requirement boundaries – of those collected included or excluded from project scope
 Tools: Product Analysis, Alternatives Generation (different ways to do same work efficiently)

6. Scope Management
Chapter 5
Create WBS
Process 4
Key Points
 “Is the hierarchical decomposition of the total scope of the work to be done by the project…
into smaller more manageable parts/deliverables.”
 Is the process of subdividing, breaking down, decomposing the project scope into
manageable work packages that is a visual to the entire team.
 Scope baseline: comprised of WBS, WBS dictionary & Project Scope Statement

7. Scope Management
Chapter 5
Create WBS
Process 4
Key Points
 WBS is the most important process in Scope Management & foundation of the project
 must be graphical & can be organized by Phase or Category
 used as a basis to estimate costs & time at the work package level
 The entire project is represented in the WBS, if not, then it’s not part of the project
 Control Accounts: Unique accounting codes assigned to track completion of work
 Created with help of the team’s experience to be realistic
 Helps gain the team’s buy-in & builds the team
 Keeps up team momentum by letting ppl see their importance to complete their work
 Helps prevent Scope Creep: impact of an uncontrolled change to scope, time, cost

8. Scope Management
Chapter 5
Validate Scope
Process 5
Key Points
 “Is the process of formalizing acceptance of completed project deliverables.”
 Involves frequent formal meetings with sponsor /customer to gain formal acceptance of deliverables
 Recommended to validate scope at the end of each phase and/or multiple times in a project
 Validate Scope process: the customer checks & approves deliverables
 Control Quality process: the QC dept checks deliverables to see that requirements are met.

9. Scope Management
Chapter 5
Control Scope
Process 6
Key Points
 “Is the process of monitoring the project status (scope performance aka work completed) by managing
changes between the work performance data against the scope baseline.”
 Is a proactive process lead by the Project Manager to prevent project changes
 Incontrolled adjustments to project constraints lead to Scope Creep

10. Scope Management
Chapter 5