Scope Management - PMP Course

1. LECTURER:
ENG.HISHAM ALI, PMP

2. Project Management Processes (47)
PROCESSES GROUP

3. Project Management Processes
KNOWLEDGE AREA

4. What is the scope management??
It is a processes you must do as a PM to know exactly
what you will obtain from your project
what is the work you will do in your project to reach to
this product
To prevent Scope creep (additions from stakeholders to
your scope)
To allow you to control your time and cost if you know
exactly what you will do.
(product scope)
(project scope)

5. Product Scope Vs. Project Scope
Product Scope. What requirements do I have to fulfill
to create the product of the project?
Product Scope: the requirements that relate to the
product of the project
Project Scope. What activities and processes do I
have to perform to deliver the product scope?
Project Scope: The work done needed to deliver the
product of the project

6. • Scope Management
Plan scope management
Collect requirements
Define scope
Create WBS
Validate scope
Control scope

7. • 5.1 Plan Scope Management
that documents how the project scope will be defined,
validated, and controlled
The key benefit of this process is that it provides
guidance and direction on how scope will be managed
throughout the project
The main concept is to plan before you do

8. 5.1 Plan Scope Management
1. Project
management plan
1. Expert judgment
1. Scope
Management Plan
2. Project Charter 2. Meetings
2. Requirements
Management Plan
3. E.E.F
4. O.P.A

9. Scope Management Plan
How the scope will be defined, developed, monitored,
controlled, and verified
Process for preparing a detailed scope statement & WBS
Process that defines how acceptance for the completed
project deliverables will be obtained
Process that defines how requested changes to the
scope statement will be processed

10. Requirements Management Plan
How requirements activities will be planned, tracked,
and reported
Requirements prioritization process
Product metrics that will be used and the rationale for
using them
Traceability structure to reflect which requirement
attributes will be captured on the traceability matrix

11. • 5.2 Collect Requirements
determining, documenting, and managing stakeholder
needs and requirements to meet project objectives
what the stakeholder needs from the project in order
for the project to be successful
Looks for all requirements not just related to products

12. 5.2 Collect Requirement
Collect
Requirement
Requirement
plan
Scope plan
Stakeholder
plan
Stakeholder
Register
Project
charter

13. Collect Requirement tools:
1. Interviews 2. Focus groups

14. Collect Requirement tools:
3. Facilitated Workshops 4.Benchmarking

15. Collect Requirement tools:
5. Questioners and survey 6.Observations

16. Collect Requirement tools:
7. Prototype 8.Document Analysis

17. Collect Requirement tools:
9. Group Creativity Techniques
 Brainstorming
 Mind Mapping
 Multi Criteria Decision Analysis
 Nominal Group Techniques
Voting to select requirement
 Affinity Diagram

18. Collect Requirement tools:
10. Group Decision Making
 Dictatorship: one person makes the decision for the group
 Unanimity : everyone agrees
 Majority : more than 50% agree
 Plurality : largest percentage not a majority
 Delphi Technique : sending information to specialists and
collecting answers > than resending answers again and collecting
new answers > than repeat … in third you will get unanimity

19. Collect
Requirement tools
Interviews
Focus
groups
Facilitated
work shops
Group
creativity
techniques
Brain
storming
Nominal
group
tech.
Mind
mapping
Affinity
diagram
Multi criteria
decision anal.
Benchmarking Questionnaires Observations
Group
decision
making
Dictatorship
Unanimity
Majority
Plurality
Delphi
tech.
Document
analysis

21. Resolving Competing Requirements:
1) Project Charter
2) The business case
3) The project constraints
Requirement Traceability Matrix

22. 5.2 Collect Requirements
1. Scope
management plan
1. Interviews
1. Requirements
Documentation
2. Requirements
Management Plan
2. Focus Groups
2. Requirements
Traceability Matrix
3. Project Charter
3. Facilitated
workshops
4. Stakeholder
Management Plan
4. Group Creativity
tech.
5. Stakeholder
Register
5. Group decision
making tech.

23. 5.2 Collect Requirements
6. Questioners &
Surveys
7. Observations
8. Prototypes
9. Benchmarking
10. Context
Diagram
11. Document
Analysis

24. • 5.3 Define Scope
developing a detailed description of the project and
product.
it describes the project, service, or result boundaries by
defining which of the requirements collected will be
included in and excluded from the project scope.

25. Product Analysis
Product
Analysis
Product
Deliverables Deliverables

26. • Project Scope Statement

27. • Project Scope Statement
Include:
Product scope
Project Scope
Deliverables
Exclusions
Acceptance Criteria
Assumptions and
Constraints

28. Project Charter vs. Project Scope Statement

29. 5.3 Define Scope
1. Scope
management plan
1. Expert Judgment
1. Project Scope
Statement
2. Requirements
Documentation
2. Product Analysis
2. Project
Documents Updates
3. Project Charter
3. Alternatives
generation
4. O.P.A
4. Facilitated
Workshops

30. • 5.4 Create WBS
the process of subdividing project deliverables and project
work into smaller, more manageable components.
It provides a structured vision of what has to be delivered.

31. • 5.4 Create WBS
WBS Packages
Product Analysis
Product
Deliverables
WBS WBS WBS
Deliverables
WBS

32. • 5.4 Create WBS

33. • 5.4 Create WBS

34. • 5.4 Create WBS

35. • 5.4 Create WBS

36. •WBS Characteristics
the foundation of all project work.
Graphical picture of the project work.
The WBS includes only the deliverables of the project.
Any deliverable not in WBS it is out of project scope.
each level of WBS is a smaller piece of the previous level
It provides a structured vision of what has to be delivered.
The WBS created with help of the team.
Each WBS package would be assigned to only one control
account .
Each control account can include a lot of WBS packages

37. • WBS benefits:
Helps to prevent scope creep
Provide the project team with an
understanding of project work and their duties.
Allows team to get their arms around the project and
promotes team buy-in
Serves as communication tool among stakeholders
Helps to manage stakeholder expectations with deliverables
Provide basis of estimating ( time, cost, risk ..)
Helps to prevent and control changes
Part of change control to evaluate impact of change.
Provides PROOF of the need for resources.

38. WBS Dictionary
document that provides detail for each component of
WBS packages.

39. Scope Baseline
Project Scope Statement
WBS
WBS Dictionary

40. 5.4 Create WBS
1. Scope
management plan
1. Expert Judgment 1. Scope Baseline
2. Requirements
Documentation
2. Decomposition
2. Project
Documents Updates
3. Project Scope
Statement
4. O.P.A
5. E.E.F

41. • 5.5 Validate Scope
the process of formalizing acceptance of the completed
project deliverables.
1) We will review the deliverable status and be sure the
work is done according the requirement
2) Obtaining sign off from costumer

42. • Actions:

43. 5.5 Validate Scope
1. project
management plan
1. Inspection
1. Accepted
Deliverables
2. Requirements
Documentation
2. Group Decision
Making Techniques
2. Change Requests
3. Requirements
Traceability Matrix
3. Work Performance
Information
4. Verified
Deliverables
4. Project
Documents Updates
5. Work Performance
Data

44. • 5.6 Control Scope
The process of monitoring the status of the project and
product scope and managing changes to the scope baseline.
It allows the scope baseline to be maintained throughout
the project

45. 5.6 Control Scope
1. project
management plan
1. Variance Analysis
1. Work Performance
Information
2. Requirements
Documentation
2. Change Requests
3. Requirements
Traceability Matrix
3. Project
Management Plan
Updates
4. Work Performance
Data
4. Project
Documents Updates
5. O.P.A 5. O.P.A Updates

46. Integration
Validate Scope
Control Scope
Integration