Peopleware: Productive Projects and Teams

Peopleware: Productive Projects and Teams

by Tom DeMarco, Tim Lister
     
 

View All Available Formats & Editions

Few books in computing have had as profound an influence on software management as Peopleware . The unique insight of this longtime best seller is that the major issues of software development are human, not technical. They’re not easy issues; but solve them, and you’ll maximize your chances of success.

Peopleware

Overview

Few books in computing have had as profound an influence on software management as Peopleware . The unique insight of this longtime best seller is that the major issues of software development are human, not technical. They’re not easy issues; but solve them, and you’ll maximize your chances of success.

Peopleware has long been one of my two favorite books on software engineering. Its underlying strength is its base of immense real experience, much of it quantified. Many, many varied projects have been reflected on and distilled; but what we are given is not just lifeless distillate, but vivid examples from which we share the authors’ inductions. Their premise is right: most software project problems are sociological, not technological. The insights on team jelling and work environment have changed my thinking and teaching. The third edition adds strength to strength.”

— Frederick P. Brooks, Jr., Kenan Professor of Computer Science, University of North Carolina at Chapel Hill, Author of The Mythical Man-Month and The Design of Design

Peopleware is the one book that everyone who runs a software team needs to read and reread once a year. In the quarter century since the first edition appeared, it has become more important, not less, to think about the social and human issues in software develop¿ment. This is the only way we’re going to make more humane, productive workplaces. Buy it, read it, and keep a stock on hand in the office supply closet.”

—Joel Spolsky, Co-founder, Stack Overflow

“When a book about a field as volatile as software design and use extends to a third edition, you can be sure that the authors write of deep principle, of the fundamental causes for what we readers experience, and not of the surface that everyone recognizes. And to bring people, actual human beings, into the mix! How excellent. How rare. The authors have made this third edition, with its additions, entirely terrific.”

—Lee Devin and Rob Austin, Co-authors of The Soul of Design and Artful Making

For this third edition, the authors have added six new chapters and updated the text throughout, bringing it in line with today’s development environments and challenges. For example, the book now discusses pathologies of leadership that hadn’t previously been judged to be pathological; an evolving culture of meetings; hybrid teams made up of people from seemingly incompatible generations; and a growing awareness that some of our most common tools are more like anchors than propellers. Anyone who needs to manage a software project or software organization will find invaluable advice throughout the book.

Editorial Reviews

Booknews
Highlights ways in which managers fail to motivate members of teams to produce their best work, and demonstrates methods for improvement. Advocates such changes as elimination of the "police mentality" in management and investment by bosses in superior workspace for employees. Dismisses many of management's favorite canards, including the one that states that workers are inefficient when working from home. Annotation c. by Book News, Inc., Portland, Or.

Product Details

ISBN-13:
9780133440737
Publisher:
Pearson Education
Publication date:
07/15/2013
Sold by:
Barnes & Noble
Format:
NOOK Book
Pages:
272
Sales rank:
369,479
File size:
2 MB

Read an Excerpt


Chapter 27: Teamicide Revisited

The seven kinds of teamicide we described in the 1987 edition of Peopleware seemed to stretch from the alpha to the omega of the subject. But there are two important kinds of teamicide that we missed. Like the original seven, these two additions are practiced widely in our field. One of them has become so ubiquitous that a small growth industry has sprung up to support it. . . .

Those Damn Posters and Plaques

Pick up the airline magazine or on-board shoppers' catalog on your next flight and flip through the full-page advertisements. Somewhere in there you will come upon a colorful selection of inspirational posters and framed messages for display on corporate walls (lest someone use up the wall space with work products). Don't just glance at them, but force yourself to read through them all, turning over their texts in your mind and savoring their syrupy prose. If you're not angry by the time you're done, you may have been serving under lousy managers for much too much of your career.

Most forms of teamicide do their damage by effectively demeaning the work, or demeaning the people who do it. Teams are catalyzed by a common sense that the work is important and that doing it well is worthwhile. The word well in this last sentence is essential: The team assigns itself the task of setting and upholding a standard of prideful workmanship. All team members understand that the quality of the work is important to the organization, but the team adopts a still higher standard to distinguish itself. Without this distinguishing factor, the group is just a group, never a real team.

Into this complicated mix, now imagine dropping a $150 framed poster to advise people that ''Quality Is Job One.'' Oh. Gee, we never would have thought that. No sir, we sort of assumed -- until this wonderful poster came along -- that Quality was Job Twenty-Nine, or maybe Eleventy-Seven, or maybe even lower than that on the corporate value scale, maybe someplace after reducing ear wax or sorting the trash. But now we know. Thanks.

These motivational accessories, as they are called (including slogan coffee mugs, plaques, pins, key chains, and awards), are a triumph of form over substance. They seem to extol the importance of Quality, Leadership, Creativity, Teamwork, Loyalty, and a host of other organizational virtues. But they do so in such simplistic terms as to send an entirely different message: Management here believes that these virtues can be improved with posters rather than by hard work and managerial talent. Everyone quickly understands that the presence of the posters is a sure sign of the absence of hard work and talent.

That important matters like these should be the subject of motivational posters is already an insult. But the implementation makes it even worse. Consider one example marketed by a company: It shows a soft-focus image of sweating oarsmen, rowing in perfect unison through the misty morning. Underneath it reads, in part:

TEAMWORK
. . . The Fuel That Allows Common People To Attain Uncommon Results

The ''common people'' they're talking about here are you and your workmates. Common people. (Don't take it too hard.) At least they're consistent in attitude: The same company's Leadership poster tells us that ''the speed of the leader determines the rate of the pack.'' The pack. Yep, that's you again.

Motivational accessories are phony enough to make most people's skin crawl. They do harm in healthy organizations. The only place where they do no harm is where they are ignored -- as in companies where the harm was done long, long ago and people have ceased to register any further decline.

The Side Effects of Overtime

Readers of the original edition of Peopleware may already have picked up a certain bias against the use of overtime. It has been our experience that the positive potential of working extra hours is far exaggerated, and that its negative impact is almost never considered. That negative impact can be substantial: error, burnout, accelerated turnover, and compensatory ''undertime.'' In this section, we examine yet another negative effect of overtime: its teamicidal repercussions on otherwise healthy work groups.

Imagine a project with a well-jelled team. You and your colleagues are producing good work at a rate that is frankly astonishing, even to you and your boss. You all understand this to be the beneficial effect of team jell, that the whole of your team production capacity is greater than the sum of your individual productivities. But it's still not enough. The powers that be have promised the product for June, and it's just not going to get done at the current rate.

Sounds like a case for a little overtime, right? You move the team into high gear, add a few hours to the workweek (still at the same high production rate), maybe work a few Saturdays. There is only one problem: One of your teammatesÑlet's call him AllenÑjust doesn't have the flexibility that the rest of you enjoy. He is a widower and thus the primary care-giver for his little boy. Allen has to show up at the day-care facility at 5:15 each afternoon to pick the child up. As you might imagine, his Saturdays and Sundays, the only real quality time with his son, are inviolable.

Hey, that's okay, you think, we'll cover for Allen. We all understand. And you all do . . . in the beginning.

A few months later, however, the rest of you are starting to show the strain. All your Saturdays have been gobbled up, as have most of your Sundays. You've been working sixty-plus-hour weeks for longer than you thought possible, and your spouses and kids are grumbling. Your laundry is piling up, your bills are unpaid, your vacation plans have been scrapped. Allen, through all this, is still working a forty-hour week. Finally, somebody says what you are all thinking: ''I'm getting pretty sick of carrying Allen.''

What's happened here? A team that was positively humming with the good effects of jell has been pried apart by an overtime policy that could not be applied uniformly to the team members. But the members of good teams are never uniform in any respect, certainly not in their abilities to ''borrow'' time from their personal lives. In almost any team of four or five or six people, there are bound to be a few who can't be expected to put in the kind of overtime that might fit pretty well into some of the others' lives. All that can be shrugged off as unimportant if the overtime is only a matter of a few long evenings and maybe one extra weekend day. But if the overtime drags on over months and starts to exact a real toll on even the most willing team members, there is bound to be damage to team cohesion. The people who aren't sharing the pain will become, little by little, estranged from the others. And the team magic will be gone.

The Last Straw

Extended overtime is a productivity-reduction technique, anyway. The extra hours are almost always more than offset by the negative side effects. This is true even if you don't consider the disruption of the team. When you take into account the way that the team members' differing abilities to work overtime tends to destroy teams, the case against it becomes persuasive.

Most managers have at least a suspicion that overtime doesn't help, that projects that work a lot of overtime are not much of a credit to their managers' skills and talents. But they end up allowing or encouraging overtime, anyway. Why is this? Jerry Weinberg has an answer of sorts: He suggests that we don't work overtime so much as a way to get the work done on time as a way to shield ourselves from blame when the work inevitably doesn't get done on time.

Meet the Author

T om DeMarco and Timothy Lister are principals of The Atlantic Systems Guild (www.systemsguild.com), a consulting firm specializing in the complex processes of system building, with particular emphasis on the human dimension. Together, they have lectured, written, and consulted internationally since 1979 on management, estimating, productivity, and corporate culture.


T om DeMarco is the author or coauthor of nine books on subjects ranging from development methods to organizational function and dysfunction, as well as two novels and a book of short stories. His consulting practice focuses primarily on expert witness work, balanced against the occasional project and team consulting assignment. Currently enjoying his third year teaching ethics at the University of Maine, he lives in nearby Camden.


Timothy Lister divides his time among consulting, teaching, and writing. Based in Manhattan, Tim is coauthor, with Tom, of Waltzing With Bears: Managing Risk on Software Projects (Dorset House Publishing Co., Inc., 2003), and of Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior (Dorset House Publishing Co., Inc., 2008), written with four other principals of The Atlantic Systems Guild. He is a member of the IEEE, the ACM, and the Cutter IT Trends Council, and is a Cutter Fellow.

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >