Scribd
Upload
59 views

Project Scope Management: Engr. Bilal Ayub Ce & M Dept, Nit-Scee NUST H-12

The document discusses project scope management, defining it as the processes involved in defining and controlling what is included in a project to ensure all required work is completed successfully. It outlines the key processes as initiation, scope planning, scope definition, scope verification, and scope change control and describes each process and its goals in managing project scope. The document also discusses best practices for developing work breakdown structures and using software to assist in project scope management.

Uploaded by

Ahsan Hameed
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
59 views

Project Scope Management: Engr. Bilal Ayub Ce & M Dept, Nit-Scee NUST H-12

The document discusses project scope management, defining it as the processes involved in defining and controlling what is included in a project to ensure all required work is completed successfully. It outlines the key processes as initiation, scope planning, scope definition, scope verification, and scope change control and describes each process and its goals in managing project scope. The document also discusses best practices for developing work breakdown structures and using software to assist in project scope management.

Uploaded by

Ahsan Hameed
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 23

PROJECT SCOPE MANAGEMENT

Engr. BILAL AYUB


CE & M Dept, NIT- SCEE
NUST H-12
[email protected]

Department of Construction Engineering and Managemnet


National University of Sciences and Technology,

H-12, Islamabad- Pakistan


What is Scope?

1. “The features and functions that are to be included


in a product or service.”

2. “The work that must be done in order to deliver a


product with the specified features and functions.”

3. “The requirements that must be met in order to


successfully finish the project”
Important Definitions

• 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, or meeting minutes

• Project scope management includes the processes involved in


defining and controlling what is or is not included in a project
Project Scope Management

• Defining what is needed is the first step toward establishing


a project timeline, setting of project goals and
allocating project resources. These steps will help you to
define the work that needs to be done

• Project Scope Management includes the processes,


required to ensure, that the project includes all the work
required to complete the project successfully.

• The answer to “WHAT to do and WHAT NOT to do” lies in the


scope
Project Scope Management
Processes
1. Initiation
2. Scope Planning
3. Scope Definition
4. Scope Verification
5. Scope Change Control
Project Scope Management
Processes
• These processes interact with each other and with the
processes in the other knowledge areas as well.

• Each process may involve effort from one or more


individuals or groups of individuals based on the needs of
the project.
1. INITIATION
Initiation is the process of formally recognizing that a new project exists or that an existing
project should continue into its next phase.

Projects are typically authorized as a result of one or more of the following:

• A market demand (e.g., an oil company authorizes a project to build a new refinery in
response to chronic gasoline shortages).
• A business need (e.g., a training company authorizes a project to create a new
course in order to increase its revenues).
• A customer request (e.g., an electric utility authorizes a project to build a new
substation to serve a new industrial park).
• A technological advance (e.g., an electronics firm authorizes a new project to
develop a video game player after the introduction of the video cassette recorder).
• A legal requirement (e.g., a paint manufacturer authorizes a project to establish
guidelines for the handling of toxic materials).
• These stimuli may include problems, opportunities, or business
requirements.
• The central theme of all these terms is that management generally
must make a decision about how to respond.
• Perform S.W.O.T analysis
2. SCOPE PLANNING
• Scope planning is the process of developing a written scope
statement as the basis for future project decisions.

• The scope statement forms the basis for an agreement


between the project team and the project customer by
identifying both the project objectives and the major project
deliverables.

• Know what is required


• Plan time , cost , quality etc
SCOPE PLANNING
3. SCOPE DEFINITION

• Scope definition involves subdividing the


major project deliverables (as identified in
the scope statement) into smaller, more
manageable components

• Improve the accuracy of cost, time, and


resource estimates

• Define a baseline for performance


measurement and control

• Facilitate clear responsibility assignments


Scope statement

The scope statement provides a documented basis for making future project decisions
and for confirming or developing common understanding of project scope among the
stakeholders.

• Project justification
• Project product
• Project deliverables
• Project objectives
Work breakdown structure

A work breakdown structure is a deliverable-oriented


grouping of project elements that organizes and defines
the total scope of the project
• Templates from previous projects may be used
OR
• Develop new WBS by decomposition.
WBS of a house construction project up to level 3
The WBS 16
(Work Breakdown Structure)

 IT is used to break down the project from one main and relatively big
entity into smaller, defined, manageable and controllable units,
usually called work groups or tasks, or, at the finest level of detail
(activities)

 The deeper you go into the lower levels of the WBS, the more detailed
knowledge you’ll need to know.

 A good rule of thumb is the rule of 1-5-5-5, which entails that each level
be broken down into a maximum of five lower levels.
17
Who develops the WBS? 18

A WBS is developed by the A/E at the end of the design


phase.

and/or by the bidders during the proposal (procurement


phase).
4. Scope Verification
Scope verification is the process of
formalizing acceptance of the project
scope by the stakeholders (sponsor,
client, customer, etc.)

Work results
• Substantial
Completion
• Full Completion
5. Scope Change Control
• Influencing the factors which create
scope changes to ensure that changes
are beneficial,
• Determining that a scope change has
occurred, and
• Managing the actual changes when
and if they occur.
• Change control centers, Risk
management plans
Goals of scope control are to

• Influence the factors that cause scope changes.


• Ensure changes are processed according to
procedures developed as part of integrated
change control.
• Manage changes when they occur.
Using Software to Assist in Project Scope 22

Management
 Word-processing software helps create scope-related
documents.
 Spreadsheets help perform financial calculations and
weighed scoring models, and help develop charts and
graphs.
 Communication software, such as e-mail and the Web, helps
clarify and communicate scope information.
 Project management software helps create a WBS, the basis
for tasks on a Gantt chart. ( WBSpro, Primavera, @Risk )
 Specialized software is available to assist in project scope
management.
Best Practices for Avoiding Scope Problems
23

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 software whenever possible
4. Follow good project management processes

You might also like