Professional Documents
Culture Documents
PDF Project Management Toolbox Tools and Techniques For The Practicing Project Manager 2Nd Edition Russ J Martinelli Ebook Full Chapter
PDF Project Management Toolbox Tools and Techniques For The Practicing Project Manager 2Nd Edition Russ J Martinelli Ebook Full Chapter
PDF Project Management Toolbox Tools and Techniques For The Practicing Project Manager 2Nd Edition Russ J Martinelli Ebook Full Chapter
https://textbookfull.com/product/project-manager-competency-
development-framework-project-management-institute/
https://textbookfull.com/product/the-entrepreneurial-project-
manager-1st-edition-cook/
https://textbookfull.com/product/construction-project-manager-s-
pocket-book-2nd-edition-duncan-cartlidge/
https://textbookfull.com/product/practical-project-control-
manager-handbook-from-back-office-manager-to-trusted-project-
strategist-first-edition-averous/
The Data-Driven Project Manager Mario Vanhoucke
https://textbookfull.com/product/the-data-driven-project-manager-
mario-vanhoucke/
https://textbookfull.com/product/agile-project-management-for-
dummies-2nd-edition-layton/
https://textbookfull.com/product/project-management-in-practice-
a-guideline-and-toolbox-for-successful-projects-1st-edition-m-
daud-alam/
https://textbookfull.com/product/the-complete-project-manager-
integrating-people-organizational-and-technical-skills-2nd-
edition-randall-englund/
https://textbookfull.com/product/practice-standard-for-project-
estimating-second-edition-project-management-institute/
PROJECT
MANAGEMENT
TOOLBOX
Second Edition
Russ J. Martinelli
Dragan Z. Milosevic
Cover image: Wiley
Cover design: abstract background © yewkeo/iStockphoto
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form
or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as
permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior
written permission of the Publisher, or authorization through payment of the appropriate per-copy fee
to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978)
646-8600, or on the web at www.copyright.com. Requests to the Publisher for permission should be
addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030,
(201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in
preparing this book, they make no representations or warranties with the respect to the accuracy or
completeness of the contents of this book and specifically disclaim any implied warranties of
merchantability or fitness for a particular purpose. No warranty may be created or extended by sales
representatives or written sales materials. The advice and strategies contained herein may not be
suitable for your situation. You should consult with a professional where appropriate. Neither the
publisher nor the author shall be liable for damages arising here from.
For general information about our other products and services, please contact our Customer Care
Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or
fax (317) 572-4002.
Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material
included with standard print versions of this book may not be included in e-books or in
print-on-demand. If this book refers to media such as a CD or DVD that is not included in the version
you purchased, you may download this material at http://booksupport.wiley.com. For more
information about Wiley products, visit www.wiley.com.
Acknowledgments xvii
2 PROJECT SELECTION 25
The Benefits Map 25
Enabling Benefits Management 26
Developing a Benefits Map 28
Using a Benefits Map 29
Variations 30
Benefits 31
Economic Methods 31
Payback Time 31
Net Present Value 31
Internal Rate of Return 33
Using Economic Methods 33
Benefits of Economic Methods 34
iii
iv CONTENTS
Scoring Models 34
Developing a Scoring Model 34
Using a Scoring Model 39
Benefits 40
Voting Models 40
Developing a Voting Model 41
Using the Voting Model 42
Benefits 45
Pairwise Ranking 46
Developing a Pairwise Ranking Tool 47
Using the Pairwise Ranking Matrix 48
Benefits 49
3 PROJECT INITIATION 55
Checklist Questions for Project Initiation 55
Developing Checklist Questions for Project
Initiation 56
Using the Checklist Questions 57
Responsibility Matrix 60
Developing a Responsibility Matrix 61
Using the Responsibility Matrix 63
Benefits 64
Complexity Assessment 64
Developing the Complexity Assessment 65
Using the Complexity Assessment 67
Benefits 67
CONTENTS v
4 PROJECT REQUIREMENTS 83
The Elicitation Plan 84
Developing an Elicitation Plan 86
Using the Elicitation Plan 89
Benefits 90
Requirements Specification 91
Specifying a Requirement Using Planguage 91
Using the Requirements Specificiation 93
Benefits 96
The Product Requirements Document 96
Developing a Product Requirements
Document 97
Using the PRD 101
Benefits 102
Requirements Ambiguity Checklist 102
Using the Requirements Ambiguity
Checklist 104
Benefits 106
Requirements Baseline 106
Establishing a Requirements Baseline 107
Establish a Requirements Change Board 107
Benefits 108
References 109
vi CONTENTS
Variations 371
Benefits 372
Concluding Remarks 373
References 373
Index 451
PREFACE
M
uch has changed since the publication of the first edition of this book, as the
field of project management (PM) is continually evolving. Part of that evolution
has involved a new approach for selecting project management tools from an
ad-hoc “choose as you use” approach to a more systematic approach of creating a PM
Toolbox that can be applied to many project situations. From this perspective, we feel
fortunate to have been part of the recent project management evolution.
We also feel fortunate to have had the opportunity to work firsthand with many
project managers and project office directors as they set about the task of creating their
initial PM Toolboxes based on the teachings of this text. Our personal understanding of
how project management is evolving and how it affects the needs for PM tools has been
greatly enhanced. This new understanding became the basis for the changes introduced
in this second edition.
The most significant changes in this edition are in four areas. First, we have focused
the content of the book on the fundamental project management practice areas to
create more depth in content. Next, we have maintained the traditional view of project
management tools but have also provided a contemporary set of tools that reflect the
changes in PM practices. Then, to strengthen an area that has created some of the most
positive reader feedback, we have enhanced the various tips, tricks, and examples found
throughout the book. Finally, we worked to create a stronger message concerning the
importance of creating a PM Toolbox that enables stronger alignment between busi-
ness strategy and project execution, between strategic goals and project deliverables,
and between the work of senior leaders and project managers.
This book has established itself as both educational lecture material and an industry
practice reference, which we hope to maintain with this second edition. Our heartfelt
thanks to the existing and future readers of this book; we hope you find it both enjoyable
and useful to read.
Of course, we would like to hear from you directly and get your feedback at
www.programmanagement-academy.com. Supplemental materials and templates can
be found on our web site as well.
xv
ACKNOWLEDGMENTS
W
e would like to thank the many people who have helped in making this book
a reality.
To our contributing authors, whose subject matter expertise is appreciated:
Debra Lavell, Jim Waddell, Tim Rahschulte, Peerasit Patanakul, James Henrey, and Jeffrey
Leach.
To the team at John Wiley & Sons, who continue to provide outstanding support and
guidance. In particular, we want to thank our executive editor, Margaret Cummins, and
our assistant editor, Amanda Shettleton. Your continued partnership and collaboration
is greatly valued.
To our many colleagues and coworkers who have contributed to the concepts pre-
sented in this work in many ways.
To our families who provide the support and encouragement necessary to complete
the writing process.
We are truly blessed to be associated with such a wonderful and supportive com-
munity of people!
xvii
PART
I
The PM
Toolbox
1
INTRODUCTION
TO THE PM TOOLBOX
onventional wisdom holds that project management (PM) tools are enabling
C devices that assist a project manager in reaching an objective or, more specifi-
cally, a project deliverable or outcome. While this traditional role of PM tools is
more than meaningful, we believe that there is greater opportunity to provide value to
an organization and its project managers. In particular, each PM tool can be part of a set
of tools that makes up a project manager’s PM Toolbox.
The PM Toolbox, then, serves a higher purpose: (1) to increase efficiency of the
project players, (2) to provide the right information to support problem-solving and
decision-making processes, and (3) to help establish and maintain alignment among
business strategy, project strategy, and project execution outcomes.
Project management tools support the practices, methods, and various processes
used to effectively manage a project.1 They are enabling devices for the primary players
on a project: the project manager, the specialists who make up the project team, the
executive leadership team, and the governance body.
PM tools include procedures, techniques, and job aids by which a project deliverable
is produced or project information is created. Similarly, A Guide to the Project Manage-
ment Body of Knowledge and other sources use the phrase “tools and techniques” in place
of what we define as PM tools.2
PM tools may be either qualitative or quantative in nature. To illustrate, consider
two examples: the team charter and Monte Carlo analysis. They differ in the type of
information they process. The team charter provides a systematic procedure to process
qualitative information about authorizing a team to implement a project. Monte Carlo
analysis is a risk-planning tool that uses an algorithm to quantify risks. The heart of both
the qualitative and quantitative groups of tools—and all PM tools belong to one of these
groups—is in their systematic procedure.
Note that we don’t talk about software tools here. True, many PM tools that we dis-
cuss in this book exist in a software format. However, our focus is not on tool formats.
Rather, we concentrate on the substance of PM tools: the use of tools to manage projects
more effectively and efficiently.
The design of a PM Toolbox should mirror the approach an organization takes for
establishing standardized project management methodologies and processes. A highly
3
4 INTRODUCTION TO THE PM TOOLBOX
standardized set of methods and processes will in turn require an equally high level of
standardization of the PM Toolbox. Less standardization introduces more variability in
PM Toolbox design and use, and therefore more possibility for inconsistent results.
In practice, as organizations strive to grow and mature, project execution efficiency
and repeatability become increasingly important as the leaders of the organization look
for consistency in achieving business results. This means that project managers must be
armed with the right tools—those that support the business strategy, project strategy,
and project management methodologies and processes. It also means that the same
tools should be used across the gamut of projects with limited exceptions.
Standardization of a firm’s PM Toolbox does not happen overnight. Rather, it is
an evolutionary process. In a practical sense, PM Toolboxes will look quite ad hoc at
first. The tendency is to begin building the PM Toolbox with existing tools due to a
project manager’s familiarity with them. So the early-stage PM Toolbox has more to do
with familiarity of use than with standardization. As a firm begins to mature its project
management practices, standardization of methodologies and processes begins to
take hold. This is when the PM Toolbox also begins to become more standardized, as
well as more aligned with the project strategy and the business strategy of the firm.
Construction of a PM Toolbox should be systematically driven, meaning that PM
tools are a vital part of an organization’s overall project execution mechanism. How-
ever, project execution must first be aligned to company strategy to be most effective.
When this is the case, the PM Toolbox becomes strategically aligned as well, as illustrated
in Figure 1.1.
As illustrated by the downward arrow, business strategy drives the project strategy,
which in turn drives methods and processes, which influences the PM Toolbox design.
For this downward flow to work, the PM Toolbox supports the project management
methodology and processes implemented by an organization. The methodology and
process in turn helps to implement the project strategy, which supports and is aligned
to the business strategy of a company in its quest for growth (upward arrow).
Business
Strategy
St
en
ra
riv
teg
Project
D
ic
Strategy
lly
Al
ica
ign
teg
me
ra
Project Management
nt
St
PM ToolBox
DIFFERENTATION
Low High
Business Strategy:
Differentiation
Project Strategy:
High
To understand the effect of business strategy, let’s use Porter’s model as an example
to evaluate the strategies for three companies producing liquid crystal display (LCD)
projectors.
The core of differentiation strategies (high differentiation/high cost quadrant
in Figure 1.2) is an ability to offer customers something different from a company’s
competitors. This may include fast time to market (which we used as an example in
Figure 1.2), high quality, innovative technology, special features, superior service, and
so on. When striving for product superiority, LCD projector companies pursuing these
strategies provide cutting-edge features that customers are willing to pay a premium
price for.
Companies focusing on low-cost strategies aim at establishing a sustainable cost
advantage over rivals (low-cost/low-differentiation quadrant). The intent is to use the
low-cost advantage as a strategy to underprice rivals and take market share away from
them. Another strategic option is to earn a higher profit by selling at the going market
price. This is pursued with a good basic product that has few frills and continuous quest
for cost reduction without giving up quality and essential features.
Best-cost companies combine upscale features with low cost (low-cost/high-
differentiation quadrant). This should lead to superior value by meeting or exceeding
customer expectations on product features and surpassing their expectations on
price. At the same time, the aim is to become the low-cost provider of a product that
has good-to-excellent features and use that cost advantage to underprice rivals with
comparable features. Because such a company has the lowest cost compared with
similarly positioned rivals, the strategy is called a best-cost strategy.
In Figure 1.2, the blank quadrant of high cost/low differentiation is not a viable
option in the quest for short- or long-term business growth.
Now, let us use the model to see how the business strategy shapes project strategies.
Examples of three companies—Sirius, Park, and Prima—will help us illustrate the point.
Sirius’s business strategy is one of differentiation. The strategy uses innovation and
time-to-market speed as competitive advantages. The business strategy is executed
through product development projects, whose job it is to roll out new advanced LCD
projector chips faster and faster. This is where the project strategy comes into play,
focusing on overlap across project phase activities to shorten the project cycle time
and the management of risk due to a number of new technologies. The project strategy
emphasizes time and risk management.
Park’s business strategy is quite different from that of Sirius. Instead of the differen-
tiation and time-to-market emphasis that Sirius relentlessly pursues, Park has set out
to become the low-cost leader in the industry. To develop the ability and become the
leader in the industry, Park has had to employ a project strategy to continuously lower
project and product cost goals. Part of that effort has been perfecting project cost
planning and management methods for managing cost cutting within the projects.
Nurturing these competencies supports Park’s low-cost advantages.
The strategies of Sirius and Park exploit their schedule- and cost-focused project
strategies, respectively. In contrast, Prima relies on a best-cost strategy. The goal is to
have the best cost relative to competitors whose LCD projectors are of comparable qual-
ity. Accordingly, their project strategies emphasize high quality and low development
PROJECT MANAGEMENT METHODOLOGIES AND PROCESSES 7
cost. Project management methodologies and practices aim to accomplish cost and
quality goals through excellent cost and performance management.
These examples provide a context from which we can construct a common base
of understanding. First, companies select business strategies as a means of operating
within the markets that they serve. Although each type of strategy has the same
goal—to create and sustain business growth, ways to accomplish the goal differ. One
company builds a strategy on the basis of differentiation, another on low cost, and still
another on a best-cost approach.
Second, companies align their project strategies with their business strategy.
Consequently, in the case of Sirius, Park, and Prima, each company’s project strat-
egy is focused differently: schedule focus (Sirius), cost focus (Park), and cost/quality
focus (Prima).
Any of these approaches is, of course, acceptable. What is critically important, how-
ever, is that care should be taken to ensure that the projects and their associated project
strategies align to and support the business strategies of the enterprise.
100% 0%
Degree of Variation
Standardization
Degree of Standardization
Degree of
Degree of Variation
0% 100%
This means that organizations have a host of options when developing their
methodologies and processes—they can be more standardized or less standardized.
The rationale behind standardization is to create a predictable process that prevents
activities from differing completely from project to project, and from project manager
to project manager. Put simply, standardization saves project players the trouble of
reinventing a new method and process for each individual project.8 As a result, the
process is repeatable despite changes in customer expectations or management
turnover. The higher the standardization, the higher the repeatability.
When establishing standardized methodologies and processes, organizations have
a host of options to choose from. Some companies adopt one of the well-known
project management methodologies such as the PMBoK, PRINCE2, or Agile Scrum.
Many establish their own methodologies and processes based on how they normally
perform their project work. Still others combine approaches by utilizing elements of the
standard methodologies and then augmenting and customizing based on the culture
of their organization.
The decision about how much to standardize project management methodologies
and processes is a decision about the ratio of standardization and variation (popularly
called flexibility). It is driven by business strategy and by the types of projects needed to
realize the business strategy. Generally, projects of higher certainty will strive for higher
levels of standardization and lower levels of flexibility. According to experts, the majority
of projects in organizations belong to this group.9 Projects that face high uncertainty
require lower standardization and higher flexibility.
Selecting PM tools one at a time demands a substantial amount of resources and
expertise. It is not reasonable to presume that each project manager—especially if he
or she is less than experienced, as is the case with many—would have the resources
and expertise to quickly, smoothly, and consistently select his or her own set of tools.
Rather, such managers end up struggling to find the right PM tools and how to use them,
introducing variability in results. In contrast, having a standardized PM Toolbox capable
of supporting the methods and processes results in minimum variation (see Table 1.1).
Often, project managers assume that the PM Toolbox is of a one-size-fits-all nature.
This, of course, is incorrect. The PM Toolbox can come in many sizes, shapes, and flavors.
Logically, this is an issue related to the project management methodology and types of
projects the methodology serves. Since the PM Toolbox is aligned with the PM method-
ology used, it is understandable that the level of standardization of the methodology
CONSTRUCTING AND ADAPTING A PM TOOLBOX 9
impacts the standardization level of the PM Toolbox. For example, a methodology that
is highly standardized will probably be supported by a highly standardized PM Toolbox.
Regardless of whether an organization’s project management methods and pro-
cesses are standardized, flexible, or semiflexible, a PM Toolbox needs to be designed so
that it aligns with both the PM methods and processes employed as well as the strategy
of the project and the business strategies driving the need for the project. To accomplish
this, a process for selecting and adapting the PM Toolbox is needed.
As detailed in the previous sections, aligning the PM Toolbox with the organization’s
business strategy tells us in broad terms what categories of project management tools
to select. This alignment drives the next step—customization of the PM Toolbox—by
OUTSIDERS.
After all, outsiders furnish quite as much fun as the legislators
themselves. The number of men who persist in writing one letters of
praise, abuse, and advice on every conceivable subject is appalling;
and the writers are of every grade, from the lunatic and the criminal
up. The most difficult to deal with are the men with hobbies. There is
the Protestant fool, who thinks that our liberties are menaced by the
machinations of the Church of Rome; and his companion idiot, who
wants legislation against all secret societies, especially the Masons.
Then there are the believers in “isms,” of whom the women-
suffragists stand in the first rank. Now I have always been a believer
in woman’s rights, but I must confess I have never seen such a
hopelessly impracticable set of persons as the woman-suffragists
who came up to Albany to get legislation. They simply would not
draw up their measures in proper form; when I pointed out to one of
them that their proposed bill was drawn up in direct defiance of
certain of the sections of the Constitution of the State he blandly
replied that he did not care at all for that, because the measure had
been drawn up so as to be in accord with the Constitution of Heaven.
There was no answer to this beyond the very obvious one that
Albany was in no way akin to Heaven. The ultra-temperance people
—not the moderate and sensible ones—are quite as impervious to
common sense.
A member’s correspondence is sometimes amusing. A member
receives shoals of letters of advice, congratulation, entreaty, and
abuse, half of them anonymous. Most of these are stupid; but some
are at least out of the common.
I had some constant correspondents. One lady in the western part
of the State wrote me a weekly disquisition on woman’s rights. A
Buffalo clergyman spent two years on a one-sided correspondence
about prohibition. A gentleman of Syracuse wrote me such a stream
of essays and requests about the charter of that city that I feared he
would drive me into a lunatic asylum; but he anticipated matters by
going into one himself. A New Yorker at regular intervals sent up a
request that I would “reintroduce” the Dongan charter, which had
lapsed two centuries before. A gentleman interested in a proposed
law to protect primaries took to telegraphing daily questions as to its
progress—a habit of which I broke him by sending in response
telegrams of several hundred words each, which I was careful not to
prepay.
There are certain legislative actions which must be taken in a
purely Pickwickian sense. Notable among these are the resolutions
of sympathy for the alleged oppressed patriots and peoples of
Europe. These are generally directed against England, as there
exists in the lower strata of political life an Anglophobia quite as
objectionable as the Anglomania of the higher social circles.
As a rule, these resolutions are to be classed as simply bouffe
affairs; they are commonly introduced by some ambitious legislator
—often, I regret to say, a native American—who has a large foreign
vote in his district. During my term of service in the Legislature,
resolutions were introduced demanding the recall of Minister Lowell,
assailing the Czar for his conduct towards the Russian Jews,
sympathizing with the Land League and the Dutch Boers, etc., etc.;
the passage of each of which we strenuously and usually
successfully opposed, on the ground that while we would warmly
welcome any foreigner who came here, and in good faith assumed
the duties of American citizenship, we had a right to demand in
return that he should not bring any of his race or national antipathies
into American political life. Resolutions of this character are
sometimes undoubtedly proper; but in nine cases out of ten they are
wholly unjustifiable. An instance of this sort of thing which took place
not at Albany may be cited. Recently the Board of Aldermen of one
of our great cities received a stinging rebuke, which it is to be feared
the aldermanic intellect was too dense fully to appreciate. The
aldermen passed a resolution “condemning” the Czar of Russia for
his conduct towards his fellow-citizens of Hebrew faith, and
“demanding” that he should forthwith treat them better; this was
forwarded to the Russian Minister, with a request that it be sent to
the Czar. It came back forty-eight hours afterwards, with a note on
the back by one of the under-secretaries of the legation, to the effect
that as he was not aware that Russia had any diplomatic relations
with this particular Board of Aldermen, and as, indeed, Russia was
not officially cognizant of their existence, and, moreover, was wholly
indifferent to their opinions on any conceivable subject, he herewith
returned them their kind communication.[7]
In concluding I would say, that while there is so much evil at
Albany, and so much reason for our exerting ourselves to bring
about a better state of things, yet there is no cause for being
disheartened or for thinking that it is hopeless to expect
improvement. On the contrary, the standard of legislative morals is
certainly higher than it was fifteen years ago or twenty-five years
ago. In the future it may either improve or retrograde, by fits and
starts, for it will keep pace exactly with the awakening of the popular
mind to the necessity of having honest and intelligent
representatives in the State Legislature.[8]
I have had opportunity of knowing something about the workings
of but a few of our other State legislatures: from what I have seen
and heard, I should say that we stand about on a par with those of
Pennsylvania, Maryland, and Illinois, above that of Louisiana, and
below those of Vermont, Massachusetts, Rhode Island, and
Wyoming, as well as below the national legislature at Washington.
But the moral status of a legislative body, especially in the West,
often varies widely from year to year.
FOOTNOTES:
[6] The Century, January, 1885.
[7] A few years later a member of the Italian Legation “scored”
heavily on one of our least pleasant national peculiarities. An
Italian had just been lynched in Colorado, and an Italian paper in
New York bitterly denounced the Italian Minister for his supposed
apathy in the matter. The member of the Legation in question
answered that the accusations were most unjust, for the Minister
had worked zealously until he found that the deceased “had taken
out his naturalization papers, and was entitled to all the privileges
of American citizenship.”
[8] At present, twelve years later, I should say that there was
rather less personal corruption in the Legislature; but also less
independence and greater subservience to the machine, which is
even less responsive to honest and enlightened public opinion.
VI
MACHINE POLITICS IN NEW YORK CITY[9]
“HEELERS.”
The “heelers,” or “workers,” who stand at the polls, and are paid in
the way above described, form a large part of the rank and file
composing each organization. There are, of course, scores of them
in each assembly district association, and, together with the almost
equally numerous class of federal, State, or local paid office-holders
(except in so far as these last have been cut out by the operations of
the civil-service reform laws), they form the bulk of the men by whom
the machine is run, the bosses of great and small degree chiefly
merely oversee the work and supervise the deeds of their
henchmen. The organization of a party in our city is really much like
that of an army. There is one great central boss, assisted by some
trusted and able lieutenants; these communicate with the different
district bosses, whom they alternately bully and assist. The district
boss in turn has a number of half-subordinates, half-allies, under
him; these latter choose the captains of the election districts, etc.,
and come into contact with the common heelers. The more stupid
and ignorant the common heelers are, and the more implicitly they
obey orders, the greater becomes the effectiveness of the machine.
An ideal machine has for its officers men of marked force, cunning
and unscrupulous, and for its common soldiers men who may be
either corrupt or moderately honest, but who must be of low
intelligence. This is the reason why such a large proportion of the
members of every political machine are recruited from the lower
grades of the foreign population. These henchmen obey
unhesitatingly the orders of their chiefs, both at the primary or
caucus and on election day, receiving regular rewards for so doing,
either in employment procured for them or else in money outright. Of
course it is by no means true that these men are all actuated merely
by mercenary motives. The great majority entertain also a real
feeling of allegiance towards the party to which they belong, or
towards the political chief whose fortunes they follow; and many
work entirely without pay and purely for what they believe to be right.
Indeed, an experienced politician always greatly prefers to have
under him men whose hearts are in their work and upon whose
unbribed devotion he can rely; but unfortunately he finds in most
cases that their exertions have to be seconded by others which are
prompted by motives far more mixed.
All of these men, whether paid or not, make a business of political
life and are thoroughly at home among the obscure intrigues that go
to make up so much of it; and consequently they have quite as much
the advantage when pitted against amateurs as regular soldiers
have when matched against militiamen. But their numbers, though
absolutely large, are, relatively to the entire community, so small that
some other cause must be taken into consideration in order to
account for the commanding position occupied by the machine and
the machine politicians in public life. This other determining cause is
to be found in the fact that all these machine associations have a
social as well as a political side, and that a large part of the political
life of every leader or boss is also identical with his social life.