Project Planning Framework
MOV Scope provides basis
for project planning
SCOPE
PHASES SEQUENCE
SCHEDULE
RESOURCESES
TASKS
TIME
Project mngt. QUALITY
BUDGET
methodology
provides guide
to planning RISKS
Scope Management
Scope is the work boundaries and deliverables of the
project
The boundary and deliverables that the project team will
provide to the project sponsor
The scope boundary acts as a fence to ensure that what –
and only what needs to get done, gets done
Scope is what is part of the project and what is NOT
Performing work that does not help the project achieve its
MOV needlessly consumes valuable time and resources
2
Scope Management Processes
I/ Scope Planning
The development of a scope management plan that defines the project’s scope and
how it will be verified and controlled throughout the project
Lays out the processes, tools and techniques to be used by the project team to
define and manage the project’s scope
II/ Scope Definition
A detailed scope statement that defines what work will and will not be part of the
project and will serve as a basis for all future project decisions
III/ Create Work Breakdown Structure
The decomposition or dividing of the major project deliverables (i.e., scope) into
smaller and more manageable components
IV/ Scope Verification
Confirmation and formal acceptance that the project’s scope is accurate, complete,
and supports the project’s MOV
V/ Scope Change Control
Ensuring that controls are in place to manage proposed scope changes once the
project’s scope is set. Must be communicated to all project stakeholders.
3
Scope Management Plan Components
Scope Scope Create Scope Scope Change
Planning Definition WBS Verification Control
Documents how Builds upon the A project
the team will A formalized A defined
preliminary planning tool acceptance from process for
define and project scope that
develop the the appropriate managing
statement to decomposes or stakeholders changes to
project’s scope define all the subdivides and
and WBS, as that the defined project and
project and organizes the project scope is product scope
well as product project’s scope
processes for complete and the impact
deliverables, into a of those changes
verifying and including the deliverable-orien
controlling the to the project’s
processes and tated hierarchy. schedule and
project and criteria for
product budget.
acceptance.
deliverables.
Scope
Scope Detailed Work Scope
Change
Mgnt Project Breakdown Verification
Control
Plan Scope Structure Checklist
Process
4
I/ Scope Planning
Initiating process to begin defining and documenting the project work
(i.e., deliverables) needed to achieve the project’s MOV
Remember, extra work that will not help the project achieve it’s
MOV will only needlessly increase the project’s schedule and budget
This process begins at a high level and will become more detailed as the
project progresses and more information becomes available
Attempts to answer the question: What is, and what is not to be
delivered by this project?
Need to know what work is to be done in order to estimate time and
cost
Makes the project sponsor’s needs and expectations explicit
Tools: -Scope Boundary; Scope Statement
5
Scope Boundary
6
Scope Statement
To define the scope boundary, create a more detailed scope
statement to document the project ‘s needs and expectations
Example Scope statement to develop an e-commerce application
for a bank :-
Develop a proactive electronic commerce strategy that
identifies the processes, products and services to be delivered
through the World Wide Web.
Develop an application system that supports all of the
processes, products, and services identified in the electronic
commerce strategy.
The application system must integrate with the bank’s existing
enterprise resource planning system.
7
Out of Scope
Technology and organizational assessment of the
current environment
Bank’s IT dept will conduct assessment not the project
team
8
II/ Project Scope Definition
The scope boundary and scope statement provide a
useful first step
The project’s scope must now be defined in more
detail in terms of specific deliverables that provide a
basis for developing the project’s work breakdown
structure (WBS)
Tools:
Deliverable Definition Table
Deliverable Structure Chart
Context Level Data Flow Diagram
Use Case Diagram
9
III/ Scope (Formulating a Basis for the WBS)
Project-Oriented Deliverables
Support the project management and IT development
processes defined in the Information Technology
Project Methodology (ITPM)
Tools
Deliverable Definition Table (DDT)
◻ All the projects deliverables must have a clear and concise
definition
Deliverable Structure Chart (DSC)
◻ Once the deliverables have been defined, the DSC serves as an
interim step to define detailed work packages that will be used
to estimate the project schedule and budget
◻ This will, in turn , be used to create the work breakdown structure
(WBS)
10
Deliverable Definition Table (DDT)
11
Deliverable
Structure
Chart
12
Scope
Product-Oriented Deliverables
What exactly is going to be delivered to the client? What does
the system do?
Tools
Context Dataflow Diagram (DFD)
◻ High-level representation of the system that has one
process(circle) and depicts all the inflows and outflows of
data and information between the system and external
entities
◻ Lower level DFDs will model the processes and flows in
greater detail
Use Case Diagram (UCD)
◻ Identifies main functions and features of the system and the
different users and external systems that interact with it
◻ Further refined and detailed during requirements analysis
13
Context Data
Flow Diagram
14
Scope
Use Case Diagram (UCD)
◻ Identifies main functions and features of the system and the
different users and external systems that interact with it
◻ May be developed iteratively during joint application development
(JAD) sessions
◻ Further refined and detailed during requirements analysis
◻ Actors – people (users, customers, managers, etc.) or external
systems that interact or use the system
◻ Use Case – depicts the major functions the system must perform
for an actor or actors
◻ The use case diagram shows a customer actor using the system
to transfer payments (for the e.g).
◻ In the requirements analysis, a set of scenarios would be
developed to depict what happens when a transfer is successful,
another when there are insufficient funds, etc.
15
Use Case
Diagram
16
IV/ Project Scope Verification
Provides a mechanism for ensuring that the project
deliverables are completed according to the DDT.
MOV
Has the project’s MOV been clearly defined and agreed upon? If not, scope
changes may result later in the project.
Deliverables
Are the deliverables tangible and verifiable?
Do they support the project’s MOV?
Quality Standards
Will the work be completed to meet specific standards?
Milestones
Significant events that mark the acceptance of a deliverable
Tell that a deliverable was not only completed but reviewed and accepted
Review and Acceptance
Formal signoff by project stakeholders, plan sponsor and project team.
17
V/ Scope Change Control
Concerned with managing changes to the project’s scope and to ensure that
these changes are beneficial when they occur
Mitigates:
Scope Grope – project team’s inability to define the project scope. Use MOV as
guidelines and follow scope processes and tools
Scope Creep – increasing featurism
Scope Leap – fundamental change in the project scope. New MOV may require killing
of existing project and start of new one.
Tools/Procedures:
Scope Change Request Form
Scope Change Request Log
18
Scope Change Request Form
Requestor Name: _______________ Request Date: __________
Request Title: __________________ Request Number: _______
Request Description:
Justification:
Possible Alternatives:
Impacts Alternative 1 Alternative 2 Alternative 3
Scope
Schedule
Resources Required
Cost
Recommendation:
Authorized By:
19
Date:
Scope Change Request Log
20
Benefits of Scope Control
Keeps the project manager in control of the project.
Authorized changes to the project’s scope are reflected in changes to the
project’s schedule and budget.
Allows the project team to stay focused and on track
Team does not have to perform unnecessary work.
21
