Information Technology Project
Management, Eighth Edition
Note: See the text itself for full citations.
Describe the five project management process
groups, the typical level of activity for each, and
the interactions among them
Understand how the project management process
groups relate to the project management
knowledge areas
Discuss how organizations develop information
technology (IT) project management
methodologies to meet their needs
Information Technology Project
Management, Eighth Edition Copyright 2016 2
Review a case study of an organization applying the
project management process groups to manage an IT
project, describe outputs of each process group, and
understand the contribution that effective initiating,
planning, executing, monitoring and controlling, and
closing make to project success
Review the same case study of a project managed with
an agile focus to illustrate the key differences in
approaches
Describe several templates for creating documents for
each process group
Information Technology Project
Management, Eighth Edition Copyright 2016 3
Copyright 2016 4
Information Technology Project
Management, Eighth Edition 5
Copyright 2016 6
A process is a series of actions
directed toward a particular result
Project management can be viewed
as a number of interlinked processes
The project management process groups include
◦ initiating processes (define & authorize a project)
◦ planning processes (devise & maintain workable plan, cost, schedule, procurement mgmt. plans)
◦ executing processes (coordinating people and other resources to carry out the various plans)
◦ monitoring and controlling processes (regularly measuring and
monitoring progress to ensure that the project team meets the project objectives)
◦ closing processes (formalizing acceptance of the project or project phase and
ending it efficiently)
Information Technology Project
Management, Eighth Edition Copyright 2016 7
Information Technology Project
Management, Eighth Edition Copyright 2016 8
You can map the main activities of each PM
process group into the ten knowledge areas using
the PMBOK® Guide, Fifth Edition, 2013
Note that there are activities from each knowledge
area under the planning process groups
Information Technology Project
Management, Eighth Edition Copyright 2016 9
Information Technology Project
Management, Eighth Edition 10
Just as projects are unique, so are approaches to
project management
Many organizations develop their own project
management methodologies, especially for IT
projects
A methodology describes how things should be
done; a standard describes what should be done
PRINCE2, Agile, RUP, and Six Sigma provide
different project management methodologies
Information Technology Project
Management, Eighth Edition Copyright 2016 11
This case study provides an example of what’s
involved in initiating, planning, executing,
controlling, and closing an IT project
Templates for creating your own project
management documents will be provided to you
Note: This case study provides a big picture view of
managing a project. Later we will study each knowledge
area in detail
Information Technology Project
Management, Eighth Edition Copyright 2016 12
It is good practice to lay the groundwork for a project
before it officially starts
Senior managers often perform several pre-initiation
tasks, including the following:
◦ Determine the scope, time, and cost constraints for the project
◦ Identify the project sponsor
◦ Select the project manager
◦ Develop a business case for a project (see Page 91 for an example)
◦ Meet with the project manager to review the process and expectations
for managing the project
◦ Determine if the project should be divided into two or more smaller
projects
Information Technology Project
Management, Eighth Edition Copyright 2016 13
Copyright 2016 14
Copyright 2016 15
Information Technology Project
Management, Eighth Edition 16
Information Technology Project
Management, Eighth Edition 17
Information Technology Project
Management, Eighth Edition 18
Initiating a project includes recognizing and starting
a new project or project phase
The main goal is to formally select and start off
projects
Following Table shows the project initiation
knowledge areas, processes, and outputs
Information Technology Project
Management, Eighth Edition Copyright 2016 19
Information Technology Project
Management, Eighth Edition Copyright 2016 20
Contents are often sensitive, so do not publish this document.
Information Technology Project
Management, Eighth Edition Copyright 2016 21
Charters are normally short and include key
project information and stakeholder signatures
It’s good practice to hold a kick-off meeting at the
beginning of a project so that stakeholders can
meet each other, review the goals of the project,
and discuss future plans
Information Technology Project
Management, Eighth Edition Copyright 2016 22
Information Technology Project
Management, Eighth Edition 23
Information Technology Project
Management, Eighth Edition Copyright 2016 24
The main purpose of project planning is to guide
execution
Every knowledge area includes planning
information (see on pages 98-99)
Key outputs included in the JWD project include:
◦ A team contract
◦ A project scope statement
◦ A work breakdown structure (WBS)
◦ A project schedule, in the form of a Gantt chart with all
dependencies and resources entered
◦ A list of prioritized risks (part of a risk register)
See sample documents starting on p. 101
Information Technology Project
Management, Eighth Edition Copyright 2016 25
Information Technology Project
Management, Eighth Edition Copyright 2016 26
Information Technology Project
Management, Eighth Edition Copyright 2016 27
Usually takes the most time and resources to
perform project execution
Project managers must use their leadership skills
to handle the many challenges that occur during
project execution
Many project sponsors and customers focus on
deliverables related to providing the products,
services, or results desired from the project
A milestone report can help focus on completing
major milestones
Information Technology Project
Management, Eighth Edition Copyright 2016 28
Information Technology Project
Management, Eighth Edition Copyright 2016 29
Involves measuring progress toward project
objectives, monitoring deviation from the plan, and
taking correction actions
Affects all other process groups and occurs during
all phases of the project life cycle
Outputs include performance reports, change
requests, and updates to various plan
Information Technology Project
Management, Eighth Edition Copyright 2016 31
Involves gaining stakeholder and customer
acceptance of the final products and services
Even if projects are not completed, they should be
closed out to learn from the past
Outputs include project files and lessons-learned
reports, part of organizational process assets
Most projects also include a final report and
presentation to the sponsor/senior management
Information Technology Project
Management, Eighth Edition Copyright 2016 32
This section demonstrates a more agile approach
to managing the same project
Differences in using an agile approach are
highlighted
An agile project team typically uses several
iterations or deliveries of software instead of
waiting until the end of the project to provide one
product.
Information Technology Project
Management, Eighth Edition Copyright 2016 33
It is not a snap decision whether to use an agile
approach or not, just like flying or driving
somewhere on a trip
Projects with less rigid constraints, experienced
and preferably co-located teams, smaller risks,
unclear requirements, and more flexible
scheduling would be more compatible with an
agile approach
The following example uses Scrum roles, artifacts,
and ceremonies/formalities
Information Technology Project
Management, Eighth Edition Copyright 2016 34
Product owner: The person responsible for the
business value of the project and for deciding what work
to do and in what order, as documented in the product
backlog.
ScrumMaster: The person who ensures that the team is
productive, facilitates the daily Scrum, enables close
cooperation across all roles and functions, and removes
barriers that prevent the team from being effective.
Scrum team or development team: A cross-functional
team of five to nine people who organize themselves
and the work to produce the desired results for each
sprint, which normally lasts 2-4 weeks.
Information Technology Project
Management, Eighth Edition Copyright 2016 35
An artifact is a useful object created by people
Scrum artifacts include:
◦ Product backlog: A list of features prioritized by
business value
◦ Sprint backlog: The highest-priority items from the
product backlog to be completed within a sprint
◦ Burndown chart: Shows the cumulative work
remaining in a sprint on a day-by-day basis
Information Technology Project
Management, Eighth Edition Copyright 2016 36
Sprint planning session: A meeting with the team to
select a set of work from the product backlog to deliver
during a sprint.
Daily Scrum: A short meeting for the development team
to share progress and challenges and plan work for the
day.
Sprint reviews: A meeting in which the team
demonstrates to the product owner what it has
completed during the sprint.
Sprint retrospectives: A meeting in which the team looks
for ways to improve the product and the process based
on a review of the actual performance of the
development team.
Information Technology Project
Management, Eighth Edition Copyright 2016 37
Information Technology Project
Management, Eighth Edition Copyright 2016 38
Information Technology Project
Management, Eighth Edition Copyright 2016 39
3 software
releases vs. 1
Information Technology Project
Management, Eighth Edition Copyright 2016 41
Information Technology Project
Management, Eighth Edition Copyright 2016 42
Information Technology Project
Management, Eighth Edition Copyright 2016 45
Get from TA
Information Technology Project
Management, Eighth Edition Copyright 2016 47
The five project management process groups are initiating,
planning, executing, monitoring and controlling, and closing
You can map the main activities of each process group to
the nine knowledge areas
Some organizations develop their own information
technology project management methodologies
The JWD Consulting case study provides an example of
using the process groups and shows several important
project documents
The second version of the same case study illustrates
differences using agile (Scrum). The biggest difference is
providing three releases of useable software versus just one
Information Technology Project
Management, Eighth Edition Copyright 2016 48
