Module: Project Scope Management

Instructor: Bilal Ahmad

LECTURE: Introduction
Project Scope Management
bilal.ahmad@szabist-isb.edu.pk

MS Faculty hall 2nd Floor (Cubicle No: 216)

Office: 051-4863363-512
Key Problems with Scope
1. Even the high-level project goals are never clearly
defined.
2. Customers are too busy to participate in the process of
requirements elicitation.
3. A lot of people who are not actual customers or users
speak and provide requirements on the customers’/users’
behalf.
4. Product scope exists in the heads of “experts” (business
or technical) and is never written down.
5. All the product features are, according to customers—
whether real or surrogate—equally important.
Key Problems with Scope
6. Technical team members discover missing or ambiguous
information in the documents and they have to guess.
7. Technical team members and customers frequently focus on what
the product should look like, and its functionality is ignored.
8. Customers either do not sign off on the requirements or design
documents or provide their sign-off and change their minds all the
time.
9. Your company does not have proper requirements specifications,
requirements management plan, requirements traceability matrix,
and work breakdown structure templates, to name just a few.
10. Project scope changes or increases, and time, resources, and budget
stay the same.
Sample Project Charter
Project Scope Management
 Project Scope Management includes the processes
required to ensure that the project includes all the
work required, and only the work required, to
complete the project successfully. Managing the
project scope is primarily concerned with defining and
controlling what is and is not included in the project.
Why Manage Project Scope?
 Some of the issues faced in projects
 Project teams believe the additional work is a change
request, but the client insists it is part of the original
scope.
 The project suddenly finds itself crunched for time. A
number of additional requirements are coming up along
with the continuing development work.
 The client talks about a high level vision which the
project is expected to achieve, but the stakeholders are
either unable to articulate this vision in concrete
objectives and deliverables or provide conflicting views
Why Manage Project Scope?
 Some of the issues faced in projects
 Contradicting requirements. Different interpretation of
the same statement by different people.
 Commitment made to the customer without
understanding the application portfolio
Project Scope Management?
 Scope refers to all the work involved in creating
the products of the project and the processes used
to create them
 A deliverable is a product produced as part of a
project, such as hardware or software, planning
documents etc.
 Project scope management includes the
processes involved in defining and controlling
what is or is not included in a project
Project Scope Management
Processes
 Scope planning: deciding how the scope will be
defined, verified, and controlled
 Scope definition: reviewing the project charter and
preliminary scope statement and adding more
information as requirements are developed and
change requests are approved
 Creating the WBS: subdividing the major project
deliverables into smaller, more manageable
components
Project Scope Management
Processes
 Scope verification: formalizing acceptance of the
project scope by key project stakeholders
 Scope control: controlling changes to project scope
which impact project cost and time goals
Project Scope Management
Summary
Scope Planning and the
Scope Management Plan
 The scope management plan is a document that
includes descriptions of how the team will prepare
the project scope statement, create the WBS, verify
completion of the project deliverables, and control
requests for changes to the project scope
 Key inputs include the project charter, preliminary
scope statement, and project management plan
 It should be reviewed with the project sponsor to
make sure the approach meets expectations
The Seven Steps
1. Analyze the project atmosphere, staekholders and centers
of influence
2. Align the project scope with the organization’s strategic
objectives and business challenges
3. Determine where to add value to the business
4. Study the process flow between the business units
5. Develop an efficient communication strategy
6. Develop the project approach
7. Coordinate the new project with the other initiatives
already under way
Plan scope management
Sample Scope Management Plan
Scope Definition and the
Project Scope Statement
 The project team develops a preliminary scope
statement in initiating a project as part of the
project integration management knowledge area
 The preliminary scope statement, project charter,
organizational process assets, and approved
change requests provide a basis for creating the
more specific project scope statement
Scope Definition and the Project
Scope Statement
 Project scope statements should contain at a minimum:
 Description of the project – overall objectives, justification
 Detailed descriptions of all project deliverables
 Characteristics and requirements of products and services
produced as part of the project
 Other helpful information:
 Project success criteria
 Project boundaries
 Product acceptance criteria
 Schedule milestones
 Order of magnitude costs estimates…
Project Scope Management
Process
 Following steps included in the project scope
management process.

 Initiation
 Scope Planning
 Scope Definition
 Scope Verification
 Scope Change Control
Plan Scope Management
 Plan Scope Management
 The process of creating a scope management plan that
documents how the project scope will be defined ,
validated and controlled.
 Collect Requirements
 The process of defining and documenting stakeholders’
needs to meet the project objectives.
 Define Scope
 The process of developing a detailed description of the
project and product
 Create WBS
 The process of subdividing project deliverables and
project work into smaller, more manageable
components .
 Validate Scope
 The process of formalizing acceptance of the completed
project deliverables.
 Control Scope
 The process of monitoring the status of the project and
product scope and managing changes to the scope
baseline.