Information Technology Project
Management – Fourth Edition
By Jack T. Marchewka
Northern Illinois University
Power Point Slides by Gerald DeHondt
Grand Valley State University
5-1
Copyright 2012 John Wiley & Sons, Inc.
Defining and Managing Project
and Product Scope
Chapter 5
5-2
Copyright 2012 John Wiley & Sons, Inc.
Learning Objectives



5-3
Identify the five processes that support project scope
management. These processes, defined by the PMBOK
Guide®, include collect requirements, define scope, create
the work breakdown structure (WBS), verify scope, and
control scope.
Describe the difference between product scope (i.e., the
features and functions that must support the IT solution)
and project scope (i.e., the deliverables and activities that
support IT project methodology).
Apply several tools and techniques for defining and
managing the project’s scope.
Copyright 2012 John Wiley & Sons, Inc.
Project Planning Framework
MOV
Scope
Sequence
Phases
Schedule
Tasks
Resources
Time
Estimates
5-4
Copyright 2012 John Wiley & Sons, Inc.
Budget
Scope Management Plan

Collect Requirements


Define Scope


The decomposition or dividing of the major project deliverables (i.e., scope) into smaller
and more manageable components
Verify Scope


A detailed description of the product, service, or information system to be designed, built
and implemented. A detailed scope statement defines what work will and will not be part
of the project and will serve as a basis for all future project decisions
Create the Work Breakdown Structure


Defining and documenting the customer, sponsor, or stakeholder needs and expectations.
This may be a formal document.
Confirmation and formal acceptance that the project’s scope is accurate, complete, and
supports the project’s MOV. The project team and sponsor must agree to all deliverables
Control Scope

5-5
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.
Copyright 2012 John Wiley & Sons, Inc.
Scope Management Plan
Collect Requirements
Centers on defining and documenting the stakeholders’
needs to properly manage expectations
Define Scope
A detailed description of project and the product. It should
define what work will and will not be included in the
project.
Create Work Breakdown
Structure (WBS)
The decomposition or dividing of the major project
deliverables into smaller and more manageable components.
Verify Scope
Confirmation and formal acceptance that project’s scope is
accurate, complete, and supports the project’s goal.
Control Scope
Ensuring that controls are in place to manage proposed
scope changes one the project’s scope is accepted. These
procedures must be communicated and understood by all
project stakeholders.
5-6
Copyright 2012 John Wiley & Sons, Inc.
Scope Planning




Initiating process to begin defining and documenting the project
work (i.e., deliverables) needed to achieve the project’s MOV
 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?
 Makes the project sponsor’s needs and expectations explicit
Tools:
 Scope Boundary
 Scope Statement
5-7
Copyright 2012 John Wiley & Sons, Inc.
Scope Boundary
Work within the Scope Boundary
Must Support the
Project’s MOV
Work Outside of the Project Scope
5-8
Copyright 2012 John Wiley & Sons, Inc.
Statement of Work



9
Narrative description of the product, service, or
information system.
For internal projects, this is tied to the business need
For external projects, this would include specifications,
quantities, quality standards, and performance
requirements for prospective bidders.
Copyright 2012 John Wiley & Sons, Inc.
Scope Statement
1.
2.
3.
5-10
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.
Copyright 2012 John Wiley & Sons, Inc.
Out of Scope
1.
2.
5-11
Technology and organizational assessment of the current
environment
Customer resource management and data mining
components
Copyright 2012 John Wiley & Sons, Inc.
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:




5-12
Deliverable Definition Table
Deliverable Structure Chart
Context Level Data Flow Diagram
Use Case Diagram
Copyright 2012 John Wiley & Sons, Inc.
Scope

Project-Oriented Deliverables


Support the project management and IT development
processes defined in the Information Technology Project
Methodology (ITPM).
Tools



Product-Oriented Deliverables



Specific features and functionality of the application system
First cut of requirements definition
Tools


5-13
Deliverable Definition Table (DDT)
Deliverable Structure Chart (DSC)
Context Dataflow Diagram (DFD)
Use Case Diagram (UCD)
Copyright 2012 John Wiley & Sons, Inc.
Deliverable Definition Table (DDT)
Deliverable
Structure
Standards
Approval
Needed
By
Resources
Required
Business Case
Document
As defined in
the
Project
Methodology
Project
Sponsor
Business Case
Team, & office
automation (OA)
tools
Project Charter &
Project Plan
Document
As defined in
the
Project
Methodology
Project
Sponsor
Project manager,
project sponsor
& OA tools
Current
Study
Document
As defined in
the
Project
Methodology
Project
Manager &
Project
Sponsor
Systems
analysts users,
case tool and
OA tools
5-14
System
Copyright 2012 John Wiley & Sons, Inc.
Deliverable
Structure
Chart
Initialize & Conceptualize
Business Case
Analysis
Strategic EC Plan
Systems Proposal
5-15
Electronic
Commerce
Banking Project
Project Charter & Plan
Project Charter & Project Plan
Design
Logical Design
Technical Design
Execute & Control
Construction
EC Application System
Close Project
Final Project Report
Formal Acceptance
Testing
Test Plan
Test Results
Copyright 2012 John Wiley & Sons, Inc.
Evaluate Project Success
Project Evaluations
Lessons Learned
Implementation
Documentation
Training Program
Conversion Plan
Context Data Flow Diagram
Account Balance Info
Account Balance Request
Product/Service Request
Customer
Cu
sto
Product
t
un
o
c
c
me
ber
m
Nu
o
Inf
n
io
A
rI
nf
o
&
Service
Info
Fund Transfer Request
Fund Transfer Confirmation
0
E-Commerce
Banking
System
s ac
n
a
Tr
t
Account Info
Transaction Confirmation
Promotion Info
Usage
Reports
Senior
Management
5-16
ERP
System
Copyright 2012 John Wiley & Sons, Inc.
EC Banking System
Check Balances
View Transaction
Histories
Get Account Info
View Check Images
Update Account
Balances
Order Checks
ERP System
Pay Bills
Customer
Transfer Funds
Print Reports
Change Address
Manager
Apply for Loans
Check Interest
Rates
Find Product/
Service Info.
Get Branch Info.
Look up ATM Locati
ons
5-17
Copyright 2012 John Wiley & Sons, Inc.
Use Case
Diagram
Project Scope Verification

MOV


Has the project’s MOV been clearly defined and agreed upon?
Deliverables


Are the deliverables tangible and verifiable?
Do they support the project’s MOV?
Quality Standards
 Milestones



Review and Acceptance

5-18
Significant events that mark the acceptance of a deliverable
Formal Signoff
Copyright 2012 John Wiley & Sons, Inc.
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
Scope Creep
Scope Leap
Scope
Tools/Procedures:


5-19
Schedule
Budget
Scope Change Request Form
Scope Change Request Log
Copyright 2012 John Wiley & Sons, Inc.
Scope Change Request Form
Requestor Name: _______________
Request Title: __________________
Request Description:
Request Date: __________
Request Number: _______
Justification:
Possible Alternatives:
Impacts
Alternative 1
Alternative 2
Scope
Schedule
Resources Required
Cost
Recommendation:
Authorized By:
Date:
5-20
Copyright 2012 John Wiley & Sons, Inc.
Alternative 3
Scope Change Request Log
Request
Number
5-21
Request
Title
Date of
Request
Requested
By
Priority
(L, M, H)
Authority
to
Approve
Request
Copyright 2012 John Wiley & Sons, Inc.
Expected
Response
Date
Scope
Change
Approved?
(Y/N)
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

5-22
They do not have to perform unnecessary work.
Copyright 2012 John Wiley & Sons, Inc.
Copyright 2012 John Wiley & Sons, Inc.
All rights reserved. Reproduction or translation of this work beyond that
permitted in section 117 of the 1976 United States Copyright Act without
express permission of the copyright owner is unlawful. Request for further
information should be addressed to the Permissions Department, John
Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own
use only and not for distribution or resale. The Publisher assumes no
responsibility for errors, omissions, or damages caused by the use of these
programs or from the use of the information herein.
5-23
Copyright 2012 John Wiley & Sons, Inc.