Project Scope Management

PROJECT SCOPE
MANAGEMENT
What is Project Scope Management?
• Scope → all the work involved in creating the products

of the project and the processes used to create them
• A deliverable → a product produced as part of a
project, such as hardware or software, planning
documents, or meeting minutes
• Project scope management → the processes involved in
defining and controlling what is or is not included in a
project
Project Scope Management Processes
Planning Scope Management
Collecting requirements
Defining Scope
Creating the WBS
Validating Scope
Controlling Scope
Project Scope Management Summary
Planning Scope Management
A Scope Management Plan’s Informations:
1 How to prepare a detailed project scope statement
2 How to create a WBS
3 How to maintain and approve the WBS
How to obtain formal acceptance of the completed

4 project deliverables
How to control requests for changes to the

5 project scope
Requirements
• IEEE Standard Glossary of Software Engineering

Terminology, Requirements is:
1. A condition or capability needed by a user to solve a problem
or achieve an objective.
2. A condition or capability that must be met or possessed by a
system or system component to satisfy a contract, standard,
specification, or other formally imposed document.
3. A documented representation of a condition or capability as
in 1 or 2.
• The PMBOK® Guide, Fifth Edition: requirements as “conditions
or capabilities that must be met by the project or present in the
product, service, or result to satisfy an agreement or other
formally imposed specification
The Requirements Management Plan
How to plan, track, and report requirements

activities
How to perform configuration management
activities
How to prioritize requirements
How to use product metrics
How to trace and capture attributes of

requirements
Collecting Requirements
Interview
Workshop
Using group creativity and Decision making technique
Questionnaires and surveys
Observation
Prototyping and document analysis
Benchmarking
Documenting Requirements
Review the project charter
Review the stakeholders registers and

stakeholder management plan
Requirements document are generated by

software
Requirements are broken down into

different categories
Requirements Traceability Matrix (RTM)
• Is a table that lists requirements, their various attributes, and

the status of the requirements to ensure that all are
addressed.
• the main purpose of an RTM is to maintain the linkage from
the source of each requirement through its decomposition to
implementation and validation
Defining Scope
• Key inputs:
• Project charter
• Scope management plan
• Requirements documentation
• Project Scope Statement, include:
• A product scope description
• Product user acceptance criteria
• Detailed information on all project deliverables
Project Charter
Project Charter
Defining Project Scope
Creating Work Breakdown Structure (WBS)
a deliverable-oriented grouping of the

work involved in a project that defines
the total scope of the project
The main tool or technique : decomposition

The outputs : the scope baseline and project documents updates
Sample Intranet WBS
Organized by Product
Sample Intranet WBS
Organized by Phase
Intranet WBS in Tabular Form
Intranet WBS and Gantt Chart in Microsoft
Project
Executing Tasks for JWD Consulting’s WBS
Intranet project Gantt chart organized by project
management process groups
Approaches to Developing WBSs
1 • The Guidelines
2 • The analogy approach
3 • The top-down approach
4 • The bottom-up approach
5 • Mind-mapping approach
Sample Mind-Mapping Approach for Creating a
WBS
The WBS Dictionary
A WBS dictionary is a document that describes

detailed information about each WBS item
WBS Dictionary
Advice for Creating a WBS and WBS Dictionary*
(continued)
A unit of work should appear at only one place in the WBS.
The work content of a WBS item is the sum of the WBS items
below it.
A WBS item is the responsibility of only one person, even

though many people might be working on it.
The WBS must be consistent with the way work actually will
be performed
Project team members should be involved in developing the
WBS
Each WBS item must be documented in a WBS dictionary
The WBS must be a flexible tool
Validating Scope
• Scope validation involves formal acceptance of
the completed project deliverables.
• This acceptance is often achieved by a customer
inspection and then sign-off on key deliverables
• The main inputs for scope validation:
• The scope management plan,
• scope baseline,
• requirements documentation,
• Requirements traceability matrix,
• validated deliverables,
• Work performance data
Controlling Scope
• Scope control involves controlling changes to
the project scope
• Goals of scope control are to:
• Influence the factors that cause scope
changes
• Assure changes are processed according to
procedures developed as part of integrated
change control
• Manage changes when they occur
• Variance is the difference between planned and
actual performance
Best Practices for Avoiding Scope
Problems
1. Keep the scope realistic: Don’t make projects so large
that they can’t be completed; break large projects down
into a series of smaller ones
2. Involve users in project scope management: Assign key
users to the project team and give them ownership of
requirements definition and scope verification
3. Use off-the-shelf hardware and software whenever
possible: Many IT people enjoy using the latest and
greatest technology, but business needs, not technology
trends, must take priority
4. Follow good project management processes: As
described in this chapter and others, there are well-
defined processes for managing project scope and
others aspects of projects

Project Scope Management

Uploaded by

Copyright:

Available Formats

Project Scope Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Scope Management

Uploaded by

Copyright:

Available Formats

PROJECT SCOPE

• Scope → all the work involved in creating the products

Planning Scope Management

Creating the WBS

A Scope Management Plan’s Informations:

1 How to prepare a detailed project scope statement

2 How to create a WBS

3 How to maintain and approve the WBS

How to obtain formal acceptance of the completed

How to control requests for changes to the

• IEEE Standard Glossary of Software Engineering

How to plan, track, and report requirements

How to prioritize requirements

How to use product metrics

How to trace and capture attributes of

Using group creativity and Decision making technique

Questionnaires and surveys

Prototyping and document analysis

Review the project charter

Review the stakeholders registers and

Requirements document are generated by

Requirements are broken down into

• Is a table that lists requirements, their various attributes, and

a deliverable-oriented grouping of the

The main tool or technique : decomposition

2 • The analogy approach

3 • The top-down approach

4 • The bottom-up approach

A WBS dictionary is a document that describes

A WBS item is the responsibility of only one person, even

You might also like