SCOPE OF PROJECT
Content Outline
•
•
•
•
•
•
•
Definition (from WIKIPEDIA)
Why is scope important?
Scope Project Step
Scope Definition – Input
Scope Definition – Process
Scope Definition – Output
Project scoping dilemma
Definition (from WIKIPEDIA)
• In project management, the scope of a project is the sum total
of all of its products and their requirements or
features.
• The project scope is the boundary that tells where the project
begins and ends.
• Scope defines the size of the project.
• Scope can include such areas as departments, geographic
locations, deliverables, features and functions. Often scope is
limited by schedule and budget constraints.
Why is Scope important?
• Scope is bound to change, and this is to be expected.
• Can limit the budget & time.
• The scope changes - usually cause problems .
• If you don’t know what you are delivering and what the
boundaries of the project are, you have no chance for success.
• If you have not done a good job of defining scope, managing
scope will be almost impossible.
Scope Project Step
INPUT
PROCESS
OUTPUT
Scope Definition - Input
The scoping of a project is all about negotiation of what can be
produced to suit the client’s needs
To get a clear statement from the client as to what the client
wants from the project that is to be developed
Scope defined by the user for the project might be too wide or too
small for the budget and time allocated for the given project
These additional aspects and tasks can severely impact on project
control, duration and costs. They must be properly planned and
controlled in addition to the standard project management tasks needed
in the case of all software projects.
•However, with a lot of interactive multimedia
projects such as information kiosks, educational
CD-ROMs, e-commerce web-sites, etc, end-users
may not be involved in the development life
cycle
 Therefore, perhaps scoping the project
with the client would be appropriate to be
performed early in the project instead of
requirements analysis
Scope Definition - Process
• All projects should spend time up-front in a definition step.
• There is not a lot of information required to define a small project
and therefore this work is usually somewhat short.
• However, as the project becomes bigger and bigger, the need to fully
understand what is being requested is more important, and gaining
agreement on what is to be delivered is more difficult.
• Therefore, more time needs to be spent planning the work.
Scoping questionnaire form
• In the information gathering process,
▫ In general it is good to focus on as much detailed
information as possible of the application that is to be
developed, too much detail might make managing the
project more difficult
▫ It is important to focus on the relevance of the
information gathered in relation to the client, the
users, the project and your company
Techniques
Roles and Responsibilities
Establishing the Triple Constraint (work, cost, duration)
Understand your Client's Expressed Needs and
their Real Needs
Short-Term Schedule
Spend More Time Up-Front to Save
Time Later
Aligning Objectives and Scope
Scope Definition: Outputs
Project Scope
Management Plan
(Updates)
Project Scope
Statement
Requested Changes
Project Scope Statement
Purpose:
• to clearly describe and gain agreement on the logical
boundaries of your project.
• to define what is within the boundaries of the project and
what is outside those boundaries.
• the more aspects of scope you can identify, the better off your project
will be.
What inside?
• describes(in detail), the project’s deliverables and the work
required to create those deliverables.
• provides a common understanding of the project scope among all
project stakeholders
• describes the project’s major objectives
• enables the project team to perform more detailed planning
• guides the project team’s work during execution
• provides the baseline for evaluating whether requests for changes or
additional work are contained within or outside the project’s
boundaries.
Cont….
Initial defined risks.
Project objectives
Project deliverables.
Fund limitation.
Project specifications.
Cost estimate.
Project boundaries.
Project
Scope
Statement
Schedule milestones.
Initial project organization.
Product scope description
Project assumptions.
Project requirements.
Product acceptance criteria.
Approval requirements.
Project configuration management
requirements.
Project constraints.
Requested Changes
• Requested changes to the project management
plan and its subsidiary plans may be developed
during the Scope Definition process.
Project Scope Management Plan
(Updates)
• The project scope management plan component
of the project management plan may need to be
updated to include approved change requests
resulting from the project’s Scope Definition
process.
Project Scoping Dilemma
▫ If they under-estimate, they will have to try to capture
more budget or risk pulling down their company
▫ If they work backwards from the potential budget and
they scope out what they think they can do for the
money and the given brief
 what happens when the client asks for more or asks for
changes?
▫ If the developers are given a solid timescale, they will
scope out what they can do in the time for the brief
and put a cost on it
 What happens then if the client asks for more or asks for
changes?