Project scope management

1. 1
Chapter 5:Chapter 5:
Project Scope ManagementProject Scope Management

2. 2
Project Scope ManagementProject Scope Management
• Scope refers to all the work involved in creating
the deliverables of the project and the processes
used to create them.
• Project scope management includes the
processes required to assure that the project
includes all the work required, and only the
work required, to complete the project
successfully .

3. 3
Project Scope ManagementProject Scope Management
• Scope Planning.
• Scope Definition.
• Create WBS.
• Scope Validation.
• Scope Control.

4. 4

5. 6
Project Scope ManagementProject Scope Management
• In the project context, the term scope can refer to:
– Product scope: The features and functions that
characterize a product, services or result.
– Project Scope: The work that needs to be
accomplished to deliver a product, service or result
with specific features and functions.

6. 7
Scope PlanningScope Planning
• The process of creating a scope management
plan that documents how the project scope will
be defined,validated,and controlled.
• Each project requires a careful balance of tools,
data sources, methodologies, processes and
procedures, and other factors to ensure that the
effort expended on scoping activities is
matching the project’s size, complexity and
importance.

7. 8

8. Plan Scope Management Data
Flow
9

9. 10
Plan Scope Management
• Inputs:
1.Project management plan: it defines how the project
is executed, monitored, controlled and closed. It
integrates all plan components.
2.Project charter.
3.Enterprise environmental factors.
4.Organizational process assets.

10. 11
Plan Scope Management
• Tools & techniques:
1.Expert judgment: knowledgeable and
experiences parties.
2.Meetings.

11. Plan Scope Management
Outputs:
1.Scope management plan.
• It includes:
process for preparing a detailed project scope
statement.
process to enable the creation of WBS
process to establish how the WBS will be managed
define formal acceptance criteria of deliverables
how change requests will be applied to scope
12

12. Plan Scope Management
Outputs:
2.Requirements management plan: describes how
requirements will be analyzed, documented, and
managed. It includes, but not limited to:
how requirements activities will be planned, tracked and
reported.
configuration management activities.
requirements prioritization process.
product metrics.
traceability structure.
13

13. 14
Scope DefinitionScope Definition
• The preparation of a detailed project scope
statement is critical to project success and
builds upon the major deliverables,
assumptions, and constraints that are
documented during project initiation in the
preliminary project scope statement.

14. 15

15. Define Scope Data Flow
16

16. Scope DefinitionScope Definition
• Inputs:
1.Scope management plan
2.Project charter
3.Requirements document
4.Organizational process assets
– Procedures & templates.
– Historical data.
– Lessons learned from old projects.
17

17. 18
Scope DefinitionScope Definition
• Tools & techniques:
1. Product analysis:
Each application area has one or more general accepted method
for translating project objectives into tangible deliverables.
1. Alternative Identification:
Is a technique used to generate different approaches to execute
and perform the work of the project.
1. Expert judgment.
4. Stakeholder Analysis(facilitated workshops):
Identify the influence and interests of the various stakeholders
and document their needs, wants and expectations.

18. 19
Sample Stakeholder AnalysisSample Stakeholder Analysis
Key Stakeholders
Ahmed Susan Erik Mark David
Organization Internal
senior
management
Project team Project team Hardware
vendor
Project
manager for
other
internal
project
Role on
project
Sponsor of
project and
one of the
company's
founders
DNA
sequencing
expert
Lead
programmer
Supplies
some
instrument
hardware
Competing
for company
resources
Unique facts Demanding,
likes details,
business
focus,
Stanford
MBA
Very smart,
Ph.D. in
biology,
easy to work
with, has a
toddler
Best
programmer
I know,
weird sense
of humor
Start-up
company, he
knows we
can make
him rich if
this works
Nice guy,
one of oldest
people at
company,
has 3 kids in
college
Level of
interest
Very high Very high High Very high Low to
medium
Level of
influence
Very high;
can call the
shots
Subject
matter
expert;
critical to
success
High; hard
to replace
Low; other
vendors
available
Low to
medium
Suggestions
on managing
relationship
Keep
informed, let
him lead
conversation
s ,do as he
says and
quickly
Make sure
she reviews
specification
s and leads
testing; can
do some
work from
home
Keep him
happy so he
stays;
emphasize
stock
options;
likes
Mexican
food
Give him
enough lead
time to
deliver
hardware
He knows
his project
takes a back
seat to this
one, but I
can learn
from him

19. 20
Scope DefinitionScope Definition
• Outputs:
1.Scope statement: describes project’s
deliverables and the work required to create
those deliverables. It includes
– product scope description
– deliverables’ acceptance criteria
– project deliverables
– project exclusion
– project assumptions
– constraints

20. Elements Of Project Charter
And Scope Statement
21

21. 22
Scope DefinitionScope Definition
• Continue: Outputs
2.Project documents updates: may include, but not
limited to:
– Stakeholder register
– Requirements documents
– Requirements traceability matrix

22. 23
Create WBSCreate WBS
• The WBS is a deliverable-oriented hierarchical
decomposition of the work to be executed by
the project team, to accomplish the project
objectives and create the required deliverables.
• The WBS sub dividing the project deliverables
and project work into smaller and more
manageable components.

23. 24

24. Create WBS Data Flow
25

25. 26
Create WBS: Tools and TechniquesCreate WBS: Tools and Techniques
1. WBS Templates
– A WBS from a previous project can often be used
as a template for a new project.
– PMI practice standard for WBS provides guidance
for the generation, development, and application of
WBS.
– PMBOK contains industry-specific examples of
WBS templates that can be tailored to specific
projects in a particular application area.

26. 27
Create WBS: Tools and TechniquesCreate WBS: Tools and Techniques
2. Decomposition:
– Decomposition is the subdivision of project
deliverables into smaller, more manageable
components until the work and deliverable are
defined to the work package level.
– Different deliverables can have different levels of
decomposition.
– The project team needs to seek a balance between
too little and too much in the level of WBS
planning detail.

27. 28
DecompositionDecomposition
• Decomposition of the total project work
generally involves the following activities:
– Identifying the deliverables and related work.
– Structuring and organizing the WBS.
– Decomposing the upper WBS levels into lower level
detailed components.
– Verifying that the degree of decomposition of the
work is necessary.

28. 29
WBS FormsWBS Forms
• Using the major deliverables and subprojects as
the first level of the decomposition.
• Using the phases of the project lifecycle as the
first level of the decomposition, with the project
deliverables inserted at the second level.
• Using different approaches within each branch
of the WBS.

29. 30

30. 31

31. 32

32. 33
Create WBS: OutputsCreate WBS: Outputs
1. Project scope statement (updates)
2. WBS: should not be confused with other structure
used in some application areas or other knowledge
areas like:
i. Organizational breakdown structure OBS
ii. Bill of Materials BOM
iii. Risk Breakdown Structure RBS
iv. Resource Breakdown Structure RBS
3. WBS Dictionary.
• Is a document describe the detailed content of WBS
components.
1. Scope baseline.
• Scope statement, WBS and WBS dictionary are the Scope
baseline
1. Project scope management plan (updates)
2. Requested Changes.

33. 34
Scope validationScope validation
• Formalizing acceptance of the completed.
• Project deliverables.
• Includes reviewing deliverables with the client
and obtaining formal acceptance of deliverables.
• Scope verification is concerned with acceptance
of deliverables while quality control is
concerned with correctness of the deliverables
and meeting quality requirements.

34. 35

35. Validate Scope: Data Flow
Diagram
36

36. 37
Scope ControlScope Control
• Monitoring the status of the project& products
scope
• Managing changes to scope baseline
• Ensure all requested changes and recommended
corrective or preventive actions are processed
through the “perform integrated change control”
process.
• Uncontrolled changes are often referred to as
project scope creep

37. 38

38. Control Scope Data Flow
39

39. 40
End Chapter 5End Chapter 5