Information Technology Project Management, Sixth Edition

Information Technology
Project Management, Sixth

Edition
Note: See the text itself for full citations.
Understand the importance of good project scope

management
Discuss methods for collecting and documenting
requirements in order to meet stakeholder needs
and expectations
Explain the scope definition process and describe
the contents of a project scope statement
Discuss the process for creating a work breakdown
structure using the analogy, top-down, bottom-up,
and mind-mapping approaches
Information Technology Project
Copyright 2009
Explain the importance of verifying scope and

how it relates to defining and controlling scope
Understand the importance of controlling scope
and approaches for preventing scope-related
problems on information technology projects
Describe how software can assist in project
scope management
Copyright 2009
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
Copyright 2009
Collecting requirements: defining and documenting the

features and functions of the products produced during the
project as well as the processes used for creating them
Defining scope: reviewing the project charter, requirements
documents, and organizational process assets to create a
scope statement
Creating the WBS: subdividing the major project
deliverables into smaller, more manageable components
Verifying scope: formalizing acceptance of the project
deliverables
Controlling scope: controlling changes to project scope
throughout the life of the project
Copyright 2009
Copyright 2009
A requirement is a condition or capability that must

be met or possessed by a system, product, service,
result, or component to satisfy a contract, standard,
specification, or other formal document (PMBOK
Guide, 2008)
For some IT projects, it is helpful to divide
requirements development into categories called
elicitation, analysis, specification, and validation
It is important to use an iterative approach to
defining requirements since they are often unclear
early in a project
Copyright 2009
Copyright 2009
Interviewing
Focus groups and facilitated workshops
Using group creativity and decision-making
techniques
Questionnaires and surveys
Observation
Prototyping
Software tools
Copyright 2009
Genesys Telecommunications Laboratories uses

Accept software, a product planning and innovation
management application and winner of the
Excellence in Product Management Award from
20062008
Accept helps them instill a consistent, repeatable,
and predictable process for new product definition
and development
They can define what information comprises a
requirement and enforce discipline around that
process
Copyright 2009
10
Requirements documents are often generated by

software and include text, images, diagrams, videos, and
other media; they are often broken down into different
categories such as functional, service, performance,
quality, training requirements, and so on
A requirements management plan describes how
project requirements will be analyzed, documented, and
managed
A requirements traceability matrix (RTM) is a table that
lists requirements, various attributes of each requirement,
and the status of the requirements to ensure that all
requirements are addressed
Copyright 2009
11
Copyright 2009
12
Key inputs for preparing the project scope

statement include the project charter, requirements
documentation, and organizational process assets
such as policies and procedures related to scope
statements as well as project files and lessons
learned from previous, similar projects
As time progresses, the scope of a project should
become more clear and specific
Copyright 2009
13
Copyright 2009
14
Many
people enjoy watching television shows like Trading

Spaces, where participants have two days and $1,000 to
update a room in their neighbors house; since the time and
cost are set, its the scope that has the most flexibility
Although most homeowners are very happy with work
done on the show, some are obviously disappointed; part of
agreeing to be on the show includes signing a release
statement acknowledging that you will accept whatever work
has been done
Too bad you cant get sponsors for most projects to sign a
similar release form; it would make project scope
management much easier!
Copyright 2009
15
A WBS is a deliverable-oriented grouping of the

work involved in a project that defines the total
scope of the project
WBS is a foundation document that provides the
basis for planning and managing project
schedules, costs, resources, and changes
Decomposition is subdividing project
deliverables into smaller pieces
A work package is a task at the lowest level of
the WBS
Copyright 2009
16
Copyright 2009
17
Copyright 2009
18
Copyright 2009
19
Copyright 2009
20
Copyright 2009
21
Using guidelines: some organizations, like the DOD,

provide guidelines for preparing WBSs
The analogy approach: review WBSs of similar
projects and tailor to your project
The top-down approach: start with the largest
items of the project and break them down
The bottom-up approach: start with the specific
tasks and roll them up
Mind-mapping approach: mind mapping is a
technique that uses branches radiating out from a
core idea to structure thoughts and ideas
Copyright 2009
22
Copyright 2009
23
Copyright 2009
24
Many WBS tasks are vague and must be

explained more so people know what to do and
can estimate how long it will take and what it will
cost to do the work
A WBS dictionary is a document that describes
detailed information about each WBS item
The approved project scope statement and its
WBS and WBS dictionary form the scope
baseline, which is used to measure performance
in meeting project scope goals
Copyright 2009
25
A unit of work should appear at only one place in

the WBS
The work content of a WBS item is the sum of the
WBS items below it
A WBS item is the responsibility of only one
individual, even though many people may be
working on it
The WBS must be consistent with the way in which
work is actually going to be performed; it should
serve the project team first and other purposes only
if practical
Copyright 2009
26
Project team members should be involved in

developing the WBS to ensure consistency and
buy-in
Each WBS item must be documented in a WBS
dictionary to ensure accurate understanding of the
scope of work included and not included in that
item
The WBS must be a flexible tool to accommodate
inevitable changes while properly maintaining
control of the work content in the project according
to the scope statement
Copyright 2009
27
A project scope that is too broad and grandiose

can cause severe problems
Scope creep and an overemphasis on technology for
technologys sake resulted in the bankruptcy of a large
pharmaceutical firm, Texas-based FoxMeyer Drug
In 2001, McDonalds fast-food chain initiated a project to
create an intranet that would connect its headquarters
with all of its restaurants to provide detailed operational
information in real time; after spending $170 million on
consultants and initial implementation planning,
McDonalds realized that the project was too much to
handle and terminated it
Copyright 2009
28
It is very difficult to create a good scope statement

and WBS for a project
It is even more difficult to verify project scope and
minimize scope changes
Scope verification involves formal acceptance of
the completed project scope by the stakeholders
Acceptance is often achieved by a customer
inspection and then sign-off on key deliverables
Copyright 2009
29
Scope control involves controlling changes to the

project scope
Goals of scope control are to:
Influence the factors that cause scope changes

Assure changes are processed according to procedures
developed as part of integrated change control
Manage changes when they occur
Variance is the difference between planned and

actual performance
Copyright 2009
30
1. Keep the scope realistic. Dont make projects so large that

they cant 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 off-the-shelf hardware and software whenever possible.
Many IT people enjoy using the latest and greatest technology,
but business needs, not technology trends, must take priority.
4. Follow good project management processes. As described in
this chapter and others, there are well-defined processes for
managing project scope and others aspects of projects.
Copyright 2009
31
Develop a good project selection process and

insist that sponsors are from the user organization
Have users on the project team in important roles
Have regular meetings with defined agendas, and
have users sign off on key deliverables presented
at meetings
Deliver something to users and sponsors on a
regular basis
Dont promise to deliver when you know you cant
Co-locate users with developers
Copyright 2009
32
Develop and follow a requirements management

process
Use techniques such as prototyping, use case
modeling, and JAD to get more user involvement
Put requirements in writing and keep them current
Create a requirements management database for
documenting and controlling requirements
Copyright 2009
33
Provide adequate testing and conduct testing

throughout the project life cycle
Review changes from a systems perspective
Emphasize completion dates to help focus on
whats most important
Allocate resources specifically for handling
change requests/enhancements like NWA did with
ResNet
Copyright 2009
34
Word-processing software helps create several

scope-related documents
Spreadsheets help to perform financial
calculations and weighted scoring models and to
develop charts and graphs
Communication software like e-mail and the Web
help clarify and communicate scope information
Project management software helps in creating a
WBS, the basis for tasks on a Gantt chart
Specialized software is available to assist in
project scope management
Copyright 2009
35
Project scope management includes the

processes required to ensure that the project
addresses all the work required, and only the work
required, to complete the project successfully
Main processes include:
Collect requirements
Define scope
Create WBS
Verify scope
Control scope
Copyright 2009
36

Information Technology Project Management, Sixth Edition

Uploaded by

Copyright:

Available Formats

Information Technology Project Management, Sixth Edition

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Information Technology Project Management, Sixth Edition

Uploaded by

Copyright:

Available Formats

Information Technology

Project Management, Sixth

Understand the importance of good project scope

Information Technology Project

Explain the importance of verifying scope and

Information Technology Project

Scope refers to all the work involved in creating the

Information Technology Project

Collecting requirements: defining and documenting the

Information Technology Project

Information Technology Project

A requirement is a condition or capability that must

Information Technology Project

Information Technology Project

Information Technology Project

Genesys Telecommunications Laboratories uses

Information Technology Project

Requirements documents are often generated by

Information Technology Project

Information Technology Project

Key inputs for preparing the project scope

Information Technology Project

Information Technology Project

people enjoy watching television shows like Trading

Information Technology Project

A WBS is a deliverable-oriented grouping of the

Information Technology Project

Information Technology Project

Information Technology Project

Information Technology Project

Information Technology Project

Information Technology Project

Using guidelines: some organizations, like the DOD,

Information Technology Project

Information Technology Project

Information Technology Project

Many WBS tasks are vague and must be

Information Technology Project

A unit of work should appear at only one place in

Information Technology Project

Project team members should be involved in

Information Technology Project

A project scope that is too broad and grandiose

Information Technology Project

It is very difficult to create a good scope statement

Information Technology Project

Scope control involves controlling changes to the

Influence the factors that cause scope changes

Variance is the difference between planned and

Information Technology Project

1. Keep the scope realistic. Dont make projects so large that

Information Technology Project

Develop a good project selection process and

Information Technology Project

Develop and follow a requirements management

Information Technology Project

Provide adequate testing and conduct testing

Information Technology Project

Word-processing software helps create several