Project Management Professional: Vincent Mckeown
Project Management Professional: Vincent Mckeown
Project Management Professional: Vincent Mckeown
Scope Management
1
Project Management Process Table
5 Process Groups
Initiation, Planning, Executing, Monitoring & Controlling, and
Closing
10 Knowledge Areas
Integration, Scope, Time, Cost, Quality, Human Resources,
Communication, Risk, Procurement, and Stakeholder.
47 Processes
2
Project Management Process Table
Integration 1 1 1 2 1
Scope 4 2
Time 6 1
Cost 3 1
Quality 1 1 1
Human 1 3 1
Resources
Communications 1 1
Risk 5 1
Procurement 1 1 1 1
Stakeholder 1 1 1 1
3
Scope Management
4
Planning Plan Scope Management
Scope Management
Plan Scope Management Process
All knowledge areas consist of a plan on how that knowledge
area is to be developed.
This process creates the Scope Management Plan and the
Requirements Management Plan.
Key inputs to this process are the Project Management Plan,
Project Charter, Enterprise Environmental Factors, and
Organizational Process Assets.
A Project Manager will use both Expert Judgment and Meetings
to develop the Scope Management Plan and Requirements
Management Plan.
5
Planning Plan Scope Management
Scope Management
Scope Management Plan
Establishes rules for managing scope, such as;
Methods used to create the scope statement
How to create the WBS
How to validate project deliverables
How to address scope change requests
6
Planning Plan Scope Management
Scope Management
Requirements Management Plan
Helps to analyze, document, and manage the project
requirements and may include;
Methods used to management requirements
Methods used to create requirements
Methods used to plan track, and report requirements activities
Methods used to perform configuration management activities
Methods used to prioritize requirements
Methods used to determine product metrics and usage rationale
How the traceability structure will show what requirement's
attributes will be on the requirements traceability matrix (RTM)
Methods used to create the RTM and the other project documents to
which the requirements will be traced.
7
Planning Plan Scope Management
Scope Management
Inputs Outputs
Tools
Expert Judgment
Meetings
8
Scope Management
9
Planning Collect Requirements
Scope Management
Collect Requirements Process
Creates the Project Requirements by focusing on project
stakeholders needs.
This process creates the Requirements Documentation and
the Requirements Traceability Matrix (RTM).
Key inputs are the Scope Management Plan, Requirements
Management Plan, Project Charter, and the Stakeholder Register.
A Project Manager can use interviews, focus groups, observations,
prototypes, benchmarking, document analysis, facilitated workshops,
group creativity techniques, group decision-making techniques,
questions and surveys, or context diagrams to develop the
Requirements Documentation and RTM.
10
Planning Collect Requirements
Scope Management
Collect Requirements Process Tools
Interviews
Establishes stakeholder needs from one on one questions.
Develops accurate requirements, but time consuming.
Facilitated Workshops
Joint Application Development (JAD), Quality Function
Deployment (QFD), and Voice of the Customer (VOC) are
examples of facilitated workshops.
Focus Groups
Subject Matter Experts (SMEs) and specific stakeholders meet
to determine their expectations and attitudes about the
projects product, service, or result.
11
Planning Collect Requirements
Scope Management
Collect Requirements Process Tools
Group Creativity Techniques
Brainstorming
Nominal Group Technique
Idea/mind mapping
Affinity diagrams
Multi-criteria decision analysis
Group Decision-Making Techniques
Unanimity
Majority
Plurality
Dictatorship
12
Planning Collect Requirements
Scope Management
Collect Requirements Process Tools
Questions and Surveys
Accumulate information from a lot of resources and quickly.
Limited to general questions or statistical analysis.
Observations
Known as job shadowing. Watching a person doing their job
and assessing.
Prototypes
Creating a working model of the expected product.
Benchmarking
Comparing Actual or planned practices to a comparable
organization to identify best practices.
13
Planning Collect Requirements
Scope Management
Collect Requirements Process Tools
Context Diagram
Visually depicts the product scope by showing a business
system and how people and other systems interact with it.
Document Analysis
Using existing documentation and analyzing to identify
information relevant to the requirements.
14
Planning Collect Requirements
Scope Management
Requirements Documentation
Basis for describing how requirements meet the business need of the
project.
Requirements need to be measurable, testable, traceable, complete,
consistent, and acceptable.
15
Planning Collect Requirements
Scope Management
Requirements Traceability Matrix
Matrix which aligns requirements to their source, business need, and
project objectives. It also may align requirements to the project
scope, WBS deliverables, product design and development, and to test
strategy and scenarios.
The Matrix may also align high level requirements to detailed
requirements.
16
Planning Collect Requirements
Scope Management
Requirements Traceability Matrix
Home Improvement Projects
WBS Requirements Source Owner Acceptance Status
Description Criteria
1.1.1.1 Grass Cut Wife Husband Inspection Complete
17
Planning Collect Requirements
Scope Management
Inputs Outputs
Project Charter
Tools
Interviews Observations Benchmarking Facilitated Workshops Group Decision Context Diagrams
Making Techniques
18
Scope Management
19
Planning Define Scope Process
Scope Management
Define Scope Process
Creates a written Project Scope Statement which can be used
in future project decision-making. It should include what the
project consists of, what is involved to create the project, and
what is expected when complete.
Key inputs are the Scope Management Plan, Project Charter,
Requirements Documentation, and Organizational Process Assets.
The Project Manager will use Expert Judgment, Product
Analysis, Alternatives Generation, and Facilitated Workshops to
develop the Project Scope Statement.
20
Planning Define Scope Process
Scope Management
Project Scope Statement
This document helps with buy-in towards the scope.
Usually includes;
Product Scope Description
Acceptance Criteria
Deliverables
Exclusions
Constraints an Assumptions.
21
Scope Management
22
Planning Create WBS Process
Scope Management
Create WBS Process
Creates the scope baseline, which includes project scope
statement, the work breakdown structure (WBS), and the WBS
dictionary.
Key inputs are the Scope Management Plan, Project Scope
Statement, Requirements Documentation, Enterprise Environmental
Factors, and Organizational Process Assets.
The Project Manager will use Decomposition, and Expert
Judgment to develop the Scope Baseline.
23
Planning Create WBS Process
Scope Management
Work Breakdown Structure
Created by the Project Manager and team.
This helps with buy-in from the team.
Work is broken down into pieces and then to the level of
decomposition for the work packages.
100% rule, all work is included represented.
Can include work packages, planning packages, and control accounts.
24
Planning Create WBS Process
Scope Management
Work Breakdown Structure
1
Level 1 Home
Improvements
Level 2 1.1
Outside Work
1.2
Inside Work
Level 3 1.1.1
Lawn Care
1.1.2
Gardening
1.2.1
Trim Work
1.2.1.1
Level 4 1.1.1.1
Cutting Grass
1.1.1.2
Fertilizing
1.1.2.1
Planting Shrubs
Crown
Molding
1.2.1.2
Baseboards
25
Planning Create WBS Process
Scope Management
Work Breakdown Structure Dictionary
Provides supporting information to the WBS such as;
Code of Account Identifier
Cost Estimates
Description of work
Associated schedule activities
Quality requirements
Contract information
Resources Required
Responsible company
Acceptance Criteria
26
Planning Create WBS Process
Scope Management
Inputs Outputs
Decomposition
27
Scope Management
28
Monitoring & Controlling Validate Scope Process
Scope Management
Validate Scope Process
29
Monitoring & Controlling Validate Scope Process
Scope Management
Inputs Outputs
Tools
Inspections
30
Scope Management
31
Monitoring & Controlling Control Scope Process
Scope Management
Control Scope Process
The control scope process is to monitor the status of the
project and product scope. This manages changes to the
scope baseline.
Key inputs are the Project Management Plan, Requirements
Documentation, Requirements Traceability Matrix, Work Performance
Data, and Organizational Process Assets.
The Project Manager will use Variance Analysis to create work
performance information, change requests, updates to the
Project Management Plan, project documentation updates, and
to update the organizational process assets33wz.
32
Monitoring & Controlling Control Scope Process
Scope Management
Inputs Outputs
Tools
Variance Analysis
33