Instant Ebooks Textbook (Ebook PDF) Project Management in Practice 5th Edition by Jack R. Meredith Download All Chapters
Instant Ebooks Textbook (Ebook PDF) Project Management in Practice 5th Edition by Jack R. Meredith Download All Chapters
Instant Ebooks Textbook (Ebook PDF) Project Management in Practice 5th Edition by Jack R. Meredith Download All Chapters
com
https://ebooksecure.com/product/ebook-pdf-project-
management-in-practice-5th-edition-by-jack-r-
meredith/
https://ebooksecure.com/product/ebook-pdf-project-management-in-
practice-6th-edition-by-jack-r-meredith/
ebooksecure.com
https://ebooksecure.com/product/project-management-in-practice-6th-
edition-by-jack-r-meredith-ebook-pdf/
ebooksecure.com
https://ebooksecure.com/download/successful-project-management-ebook-
pdf/
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-introductory-technical-
mathematics-7th-edition/
ebooksecure.com
(eBook PDF) Computer Networks 6th Edition
https://ebooksecure.com/product/ebook-pdf-computer-networks-6th-
edition/
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-anthropology-appreciating-
human-diversity-18th-edition/
ebooksecure.com
https://ebooksecure.com/download/managing-for-quality-and-performance-
excellence-ebook-pdf/
ebooksecure.com
https://ebooksecure.com/download/cultivating-an-understanding-of-
curiosity-as-a-seed-for-creativity-ebook-pdf/
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-exploring-strategic-
change-4th-edition-by-julia-balogun/
ebooksecure.com
Metal Oxide Powder Technologies: Fundamentals, Processing
Methods and Applications (Metal Oxides) 1st Edition Yarub
Al-Douri (Editor) - eBook PDF
https://ebooksecure.com/download/metal-oxide-powder-technologies-
fundamentals-processing-methods-and-applications-metal-oxides-ebook-
pdf/
ebooksecure.com
vi • c o ntents
8.1 Evaluation 280
Evaluation Criteria 281
Measurement 282
8.2 Project Auditing 283
The Audit Process 283
The Audit Report 285
8.3 Project Termination 288
When to Terminate a Project 288
Types of Project Termination 289
The Termination Process 290
The Project Final Report 292
Review Questions 293
Discussion Questions 293
Incidents for Discussion 294
Case: St. Dismas Assisted Living Facility Case—6 294
Case: Datatech 297
Case: Ivory Tower Systems 298
Bibliography 300
x • c ontents
Index 311
P r e f a c e
The Approach
Over the past several decades, more and more work has been accomplished through
the use of projects and project management. The use of projects has been growing at
an accelerated rate, and not just in engineering and information technology, but also
in all the business disciplines: marketing, finance, human resources, accounting, opera-
tions, legal, and, of course, management. One of the most interesting areas of growth,
however, has been in the use of projects to achieve the strategic goals of organizations.
The exponential growth of membership in the Project Management Institute (PMI) is
further convincing evidence, as are the sales of computer software devoted to project
management. Several societal forces are driving this growth, and many economic fac-
tors are reinforcing it. We describe these in Chapter 1 of this book.
A secondary effect has also been a major contributor to the use of project activity.
As the use of projects has grown, its very success as a way of getting complex activi-
ties carried out successfully has become well established. The result has been a striking
increase in the use of projects to accomplish jobs that in the past would simply have
been turned over to someone with the comment, “Take care of it.”
What happened then was that some individual undertook to carry out the job with
little or no planning, little or no assistance, few resources, and often with only a vague
notion of what was really wanted. The simple application of routine project management
techniques significantly improved the consistency with which the outcomes resembled
what the organization had in mind when the chore was assigned. Later, this sort of activ-
ity came to be known as “enterprise project management,” “management by projects,”
and several other names, all of which are described as the project-oriented organization.
Some of these projects were large, but most were quite small. Some were complex,
but most were relatively straightforward. Some required the full panoply of project
management techniques, but most did not. All of them, however, had to be managed
and thus required a great many people to take on the role of project manager in spite of
little or no education in the science or arcane art of project management.
One result was rising demand for education in project management. The number of
college courses grew apace, as did the number of consulting firms offering seminars and
workshops. Perhaps most striking was the growth in educational opportunities through
post-secondary schools offering “short courses”—schools such as DeVry Institute, and
ITT. In addition, short courses were offered by colleges and community colleges con-
centrating on both part-time and full-time education for individuals already in the
work force. An exemplar of this approach is the University of Phoenix.
Communications from some instructors in these institutions told us that they would
like a textbook that was shorter and focused more directly on the “technical” aspects of
project management than those currently available. They were willing to forego most of
the theoretical aspects of management, particularly if such were not directly tied to prac-
tice. Their students, who were not apt to take advanced course work in project man-
agement, had little use for understanding the historical development of the field. For
example, they felt no need to read about the latest academic research on the management
xi
xii • P reface
With few exceptions, both readers and instructors are most comfortable with project
management texts that are organized around the project life cycle, and this book is so
organized. In Chapter 1 we start by defining a project and differentiating project man-
agement from general management. After discussing the project life cycle, we briefly
cover project selection. We feel strongly that project managers who understand why a
project was selected by senior management also understand the firm’s objectives for the
project. Understanding those things, we know, will be of value in making the inevitable
trade-offs between time, budget, and the specified output of the project.
Chapter 2 is devoted to the various roles the project manager must play and to
the skills required to play them effectively. In addition, we cover the various ways in
which projects can be organized. The nature of project teams, including multidiscipli-
nary teams, and the behavioral aspects of projects are also discussed.
Project and risk planning, budgeting, and scheduling are covered in Chapters 3 to 5.
Planning the project initiates our discussion in Chapter 3, where we introduce the work
breakdown structure and other planning aids such as the RACI matrix, and end with a
thorough discussion and illustration of risk management planning. Project budgeting is
then described in Chapter 4 where we introduce the use of simulation through software
such as Crystal Ball® to analyze financial risk. Risk analysis using Oracle’s Crystal Ball®
11.1 (CB) simulations is demonstrated in several chapters with detailed instructions on
building and solving simulation models. Software is used throughout the book, where
relevant, to illustrate the use and power of such software to aid in managing projects.
Chapter 4 also includes a helpful mathematical model for improving cost estimates, or
any other numerical estimates used in planning projects. Chapter 5 initially uses stand-
ard manual methods for building project schedules, and Microsoft Project® 2010 (MSP)
is then demonstrated for doing the same thing.
Chapter 6 deals with resource allocation problems in a multiproject setting.
A major section of this chapter is devoted to the insights of E. Goldratt in his book
Critical Chain.* Chapter 7 concerns monitoring and controlling the project, especially
through the use of earned value analysis, which is covered in detail. The final chapter
deals with auditing, evaluating, and terminating projects.
Interest in risk management has grown rapidly in recent years, but the subject gets
only minimal attention in most introductory level project management textbooks. We
deal with risk throughout this book, introducing methods of risk management and analy-
sis where relevant to the subject at hand. For example, simulation is used in Chapter 4
for solving a project budgeting problem, in Chapter 5 on a scheduling problem, and in
Chapter 6 for examining the impact of a generally accepted assumption about probabilis-
tic project schedules that is usually false, and also to test the usually false assumption that
multitasking is an efficient way to improve productivity.
We are certainly aware that no text on project management could be structured
to reflect the chaos that seems to surround some projects throughout their lives, and a
*
Goldratt, E. M. Critical Chain. Great Barrington, MA: North River, 1997.
Pre fac e • xiii
large majority of projects now and then. The organization of this book reflects a tidiness
and sense of order that is nonexistent in reality. Nonetheless, we make repeated refer-
ences to the technical, interpersonal, and organizational glitches that impact the true
day-to-day life of the project manager.
Pedagogy
The book includes several pedagogical aids. The end-of-chapter material includes Review
Questions that focus on the textual material. Discussion Questions emphasize the implica-
tions and applications of ideas and techniques covered in the text. Where appropriate,
there are Problems that are primarily directed at developing skills in the technical areas of
project management as well as familiarizing the student with the use of relevant software.
In addition to the above, we have included Incidents for Discussion in the form of
caselettes. In the main, these caselettes focus on one or more elements of the chapter to
which they are appended. Several of them, however, require the application of concepts
and techniques covered in earlier chapters so that they also serve an integrative function.
More comprehensive cases are also appended to each chapter. A special set of these,
beginning in Chapter 3, is associated with the same project, which continues on through
the following chapters—the planning, building, and marketing of an assisted living facil-
ity for people whose state of health makes it difficult for them to live independently, but
who are not yet ill enough to require nursing home care. Each chapter is followed by a
continuation of this case calling upon the ideas and methods covered in that chapter.
With all these cases, integration with material in other chapters is apt to be required.
We include Learning Objectives for each chapter but instead of putting them at
the beginning of the chapter, we have added them to the Instructors’ Manual. Many
teachers feel that their students should have the Learning Objectives as they begin
each chapter. Many don’t. Many teachers like to use their own LOs. Many do not like
to use LOs because they feel that students focus solely on the listed objectives and
ignore everything else. Given our LOs in the Instructor’s Manual, each teacher may opt
for his or her own notion on the matter.
We have used Excel® spreadsheets where appropriate throughout the book.
Microsoft Office® is widely available, and with few exceptions students and professional
project managers are familiar with its operation. A free 60-day trial edition of Microsoft
Project 2010® is available with each new copy of the book through the contact informa-
tion below. It will run on Microsoft’s Windows 8® as well as several earlier versions of
Windows®. Note that Microsoft has changed their policy and no longer offers a 120-
day trial, only a 60-day trial. Please be sure to plan your course accordingly. Additionally,
Microsoft Project 2010® software is available through Dreamspark Premium, an annual
membership program that provides the easiest and most inexpensive way for universi-
ties to make the latest Microsoft software available in labs, classrooms, and on student
PCs. Through Wiley’s partnership with Microsoft, software available via Dreamspark
Premium is provided at no charge to qualifying departments upon adoption.
Contact your Wiley representative (click on “Who’s My Rep” at www.Wiley.com)
when you have selected a Wiley textbook to adopt. Schools must qualify, and some restric-
tions do apply, so please contact your Wiley representative about this opportunity. Once
qualified, your department will be awarded membership, and you, your colleagues, and the
students in your courses can begin downloading the software from a remote hosting server.
Microsoft and Wiley are working together to make obtaining software for your
department easy for you. E-mail us at [email protected] for details or call 1-888-
764-7001. For more information about the Dreamspark Premium program, go to www.
dreamspark.com.
xiv • Preface
What’s New
Both students and instructors have been generous and kind with their comments on
the first four editions of this book. They have given us very useful suggestions and
feedback such as proposing that we integrate the material on Crystal Ball® directly
Visit https://testbankfan.com
now to explore a rich
collection of testbank or
solution manual and enjoy
exciting offers!
Pre fac e • xv
into the chapters where it is used, which we have done. In this edition we have also
tried to improve the flow of material and have moved some topics around a bit to
achieve this. First, we moved the extensive Crystal Ball® simulation description out
of the introductory Chapter 1 and into the budgeting Chapter 4 to illustrate how to
simulate costs to evaluate budget risks. And we moved the discussion of risk manage-
ment earlier, from Chapter 4 to the project planning Chapter 3, since risk pervades
all the aspects of project planning, and especially scope, time, and cost. To make
room for the risk discussion in Chapter 3, we moved the discussion of multidiscipli-
nary teams to Chapter 2, which seems to be a better fit for the topic also.
Reviewers also asked us to comment about how budgets and activity expediting
are actually handled in practice, so we checked many practice-oriented magazines and
journals and then queried some project managers we knew. The result is a few para-
graphs in Chapters 4 on budgeting and Chapter 6 on resource allocation describing the
vagaries and real-world dynamics project managers commonly face in these areas.
To further improve the student’s perspective of project management from the view
of project managers in actual practice, we describe their situation throughout the text as
one of constantly making trade-offs between not only the three main goals of scope, time,
and cost but also risk and other implied ancillary goals such as organizational improve-
Trade-Offs
ment, strategic goals, and future opportunities. To highlight these areas where we talk
about trade-offs and risk, we have added new icons to the book margins where impor-
tant discussion on these topics appears. We have also added a new icon to indicate areas
Risk of discussion that we believe exemplify “best practice” in the project management field.
And we have expanded our references to locations in PMBOK® that discuss the topic at
hand for those who are also studying for the Project Management Professional® (PMP) or
Best Practice
other certification exams offered by the Project Management Institute.
Last, we added a large number of additional problems and mini-cases to the
appropriate chapters where reviewers asked for them. We also added another simula-
tion example in Chapter 5 to illustrate costs in a network. We also reduced our dis-
PMBOK Guide cussion on some topics that reviewers suggested, such as the design structure matrix.
Supplements
The Instructor’s Manual will provide assistance to the project management instructor
in the form of answers/solutions to the questions, problems, incidents for discussion,
and end-of-chapter cases. This guide will also reference relevant Harvard Business
School type cases and readings, teaching tips, and other pedagogically helpful mate-
rial. Wiley maintains a web site for this and other books. The address is www.wiley.com/
college/mantel. The site contains an electronic version of the Instructor’s Manual, an
extensive set of PowerPoint slides, sample course outlines, and test questions to test
student understanding.
Acknowledgments
There is no possible way to repay the scores of project managers and students who have
contributed to this book, often unknowingly. The professionals have given us ideas
about how to manage projects, and students have taught us how to teach project man-
agement. We are grateful beyond our ability to express it.
We are also grateful to a small group of individuals, both close friends and
acquaintances, who have graciously shared their time and knowledge without stint:
xvi • Preface
James Cochran, Louisiana Tech University; James Evans, University of Cincinnati; Karen
Garrison, Lucidity Consulting Group; Timothy Kloppenborg, Xavier University, Ohio;
Samuel J. Mantel, III, RadioShack, Inc.; Jim McCarthy, McCarthy Technologies, Inc.; the
late Gerhard Rosegger, (2008), Case Western Reserve University; and Stephen Wearne,
University of Manchester, Institute of Science and Technology.
For this edition we thank the following reviewers: Jesus Jimenez, Texas State University;
Steve MacQueen, Midlands Technical College; Al Morelli, University of Southern California;
Dee Piziak, Concordia University, Wisconsin; James Szot, The University of Texas at Dallas;
Marlee Walton, Iowa State University; and Richard Wendell, University of Pittsburgh.
Above all, we thank Suzanne Ingrao, Ingrao Associates, without whom this book would
have been unreadable. Our gratitude is also extended to Wiley Editors Lisé Johnson and
Brian Baker who did their best to keep us on track, on time, and of composed mind.
Finally, we owe a massive debt to those colleagues who reviewed the original
manuscript of this book and/or its subsequent editions: Kwasi Amoako-Gyampah,
University of North Carolina at Greensboro; James M. Buckingham, United States Military
Academy, West Point; Michael J. Casey, George Mason University; Larry Crowley, Auburn
University; Catherine Crummett, James Madison University; George R. Dean, DeVry
Institute of Technology, DuPage; Geraldo Ferrer, University of North Carolina at Chapel
Hill; Linda Fried, University of Colorado, Denver; William C. Giauque, Brigham Young
University; Bertie Greer, Northern Kentucky University; David Harris, University of New
Mexico; H. Khamooshi, George Washington University; Bill Leban, Keller Graduate School
of Management; Leonardo Legorreta, California State University, Sacramento; William
E. Matthews, William Patterson University; Sara McComb, University of Massachusetts
Amherst; J. Wayne Patterson, Clemson University; Ann Paulson, Edmonds Community
College; Patrick Philipoom, University of South Carolina; Arthur C. Rogers, City
University; Dean T. Scott, DeVry Institute of Technology, Pomona; Richard V. Sheng,
DeVry Institute of Technology, Long Beach; William A. Sherrard, San Diego State
University; Kimberlee Snyder, Winona University; Louis C. Terminello, Stevens Institute
of Technology; and Jeffrey L. Williams, University of Phoenix. We owe a special thanks
to Byron Finch, Miami University, for a number of particularly thoughtful suggestions
for improvement. While we give these reviewers our thanks, we absolve each and all of
blame for our errors, omissions, and wrong-headed notions.
1
The World of Project Management
Once upon a time there was a heroine project manager. Her projects were never late.
They never ran over budget. They always met contract specifications and invariably
satisfied the expectations of her clients. And you know as well as we do, anything that
begins with “Once upon a time . . .” is just a fairy tale.
This book is not about fairy tales. Throughout these pages we will be as realistic as
we know how to be. We will explain project management practices that we know will
work. We will describe project management tools that we know can help the project
manager come as close as Mother Nature and Lady Luck will allow to meeting the
expectations of all who have a stake in the outcome of the project.
1
2 • C h a p t e r 1 / T h e W o r l d o f P r o j ec t Management
and a nonproject is not always crystal clear. For almost any precise definition, we
can point to exceptions. At base, however, projects are unique, have a specific
deliverable, and have a specific due date. Note that our examples have all those
characteristics. The Project Management Institute (PMI) defines in its Project
PMBOK Guide Management Body of Knowledge (PMBOK Guide), 5th edition, a project as “A tem-
porary endeavor undertaken to create a unique product, service, or result” (Project
Management Institute, 2013).
Projects vary widely in size and type. The writing of this book is a project. The
reorganization of Procter & Gamble (P&G) into a global enterprise is a project, or
more accurately a program, a large integrated set of projects. The construction of a
fly-in fishing lodge in Manitoba, Canada, is a project. The organization of “Cat-in-
the-Hat Day” so that Mrs. Payne’s third grade class can celebrate Dr. Suess’s birthday
is also a project.
Both the hypothetical projects we mentioned earlier and the real-world projects
listed just above have the same characteristics. They are unique, specific, and
have desired completion dates. They all qualify as projects under the PMI’s defi-
nition. They have an additional characteristic in common—they are multidis-
ciplinary. They require input from people with different kinds of knowledge and
expertise. This multidisciplinary nature of projects means that they tend to be com-
plex, that is, composed of many interconnected elements and requiring input from
groups outside the project. The various areas of knowledge required for the construc-
tion of the fly-in fishing lodge are not difficult to imagine. The knowledge needed
for globalization of a large conglomerate like P&G is quite beyond the imagina-
tion of any one individual and requires input from a diversified group of specialists.
Working as a team, the specialists investigate the problem to discover what informa-
tion, skills, and knowledge are needed to accomplish the overall task. It may take
weeks, months, or even years to find the correct inputs and understand how they
fit together.
A secondary effect of using multidisciplinary teams to deal with complex prob-
lems is conflict. Projects are characterized by conflict. As we will see in later chap-
ters, the project schedule, budget, and specifications conflict with each other. The
needs and desires of the client conflict with those of the project team, the senior
management of the organization conducting the project and others who may have a
less direct stake in the project. Some of the most intense conflicts are those between
members of the project team. Much more will be said about this in later chapters.
For the moment, it is sufficient to recognize that projects and conflict are often
inseparable companions, an environment that is unsuitable and uncomfortable for
conflict avoiders.
It is also important to note that projects do not exist in isolation. They are often
parts of a larger entity or program, just as projects to develop a new engine and an
improved suspension system are parts of the program to develop a new automo-
bile. The overall activity is called a program. Projects are subdivisions of programs.
Likewise, projects are composed of tasks, which can be further divided into subtasks
that can be broken down further still. The purpose of these subdivisions is to allow the
project to be viewed at various levels of detail. The fact that projects are typically parts
of larger organizational programs is important for another reason, as is explained in
Section 1.5.
Finally, it is appropriate to ask, “Why projects?” The reason is simple. We form
projects in order to fix the responsibility and authority for the achievement of an
organizational goal on an individual or small group when the job does not clearly fall
within the definition of routine work.
1. 1 W HAT I S A PROJEC T? • 3
YERMÁK
KOLYÁDKA
BOWL-SONG
A PARTING SCENE
THE DOVE
On an oak-tree sat,
Sat a pair of doves;
And they billed and cooed
And they, heart to heart,
Tenderly embraced
With their little wings;
On them, suddenly,
Darted down a hawk.
Nightingale, O nightingale,
Nightingale so full of song!
Tell me, tell me, where thou fliest,
Where to sing now in the night?
Will another maiden hear thee,
Like to me, poor me, all night
Sleepless, restless, comfortless,
Ever full of tears her eyes?
Fly, O fly, dear nightingale,
Over hundred countries fly,
Over the blue sea so far!
Spy the distant countries through,
Town and village, hill and dell,
Whether thou find’st anyone,
Who so sad is as I am?
Oh, I bore a necklace once,
All of pearls like morning dew;
And I bore a finger-ring,
With a precious stone thereon;
And I bore deep in my heart
Love, a love so warm and true.
When the sad, sad autumn came,
Were the pearls no longer clear;
And in winter burst my ring,
On my finger, of itself!
Ah! and when the spring came on,
Had forgotten me my love.
ELEGY
THE FAREWELL
—From Sir John Bowring’s Specimens of the Russian Poets, Part II.
WEDDING GEAR