Gift Guide

Peopleware: Productive Projects and Teams / Edition 2

Paperback (Print)
Rent from
(Save 65%)
Est. Return Date: 02/20/2015
Used and New from Other Sellers
Used and New from Other Sellers
from $3.00
Usually ships in 1-2 business days
(Save 91%)
Other sellers (Paperback)
  • All (22) from $3.00   
  • New (3) from $23.59   
  • Used (19) from $3.00   
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any coupons and promotions
Seller since 2014

Feedback rating:



New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

1999 Paperback New

Ships from: san francisco, CA

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Seller since 2007

Feedback rating:


Condition: New
PAPERBACK New 0932633439 Brand new book. STUDENT US EDITION. Never used. Nice gift. Best buy. Shipped promptly and packaged carefully.

Ships from: Woodinville, WA

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Seller since 2014

Feedback rating:


Condition: New
New Free gift-wrapping if requested; simply message us with your request. Expedited delivery 1-2 business days. Normal delivery 2-4 business days. Dispatched from Cheshire UK. ... Secure packaging. Airmail Internationally. Please see our feedback, buy with complete confidence and enjoy your book. *****PLEASE NOTE: This item is shipping from an authorized seller in Europe. In the event that a return is necessary, you will be able to return your item within the US. To learn more about our European sellers and policies see the BookQuest FAQ section***** Read more Show Less

Ships from: Altrincham, United Kingdom

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Page 1 of 1
Showing All
Sort by


Two of the computer industry's best-selling authors and lecturers return with a new edition of the software management book that started a revolution.

With humor and wisdom drawn from years of management and consulting experience, DeMarco and Lister demonstrate that the major issues of software development are human, not technical - and that managers ignore them at their peril.

Now, with a new Preface and eight new chapters, the authors enlarge upon their previous ideas and add fresh insights, examples, and anecdotes.

Discover dozens of helpful tips on

  • Putting more quality into a product
  • Loosening up formal methodologies
  • Fighting corporate entropy
  • Making it acceptable to be uninterruptible

Peopleware shows you how to cultivate teams that are healthy and productive. The answers aren't easy - just incredibly successful.

Authors Tom DeMarco and Timothy Lister have updated and expanded their classic publication on growing and managing productive teams and successful software projects. And, they did it just in time for the 10th anniversary of their prescient first edition. As in the first edition, they emphasize the "human resource" and take a hard, incisive and many times humorous look at people, teams and their surroundings -- Peopleware, the source of success or failure for all software projects.

Read More Show Less

Editorial Reviews

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.
Computing - Alan Campbell
Lister and DeMarco savagely destroy a sizeable chunk of received wisdom, using well-picked example, careful reasoning, and even data. Even if you disagree with what they say, you will enjoy how they say it. Get the book and read it. Then give it to your manager. Of, if you dare, your subordinates.
Book Jacket - Fred Brooks
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.
Book Jacket - Joel Spolsky
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 development. 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.
Read More Show Less

Product Details

  • ISBN-13: 9780932633439
  • Publisher: Dorset House Publishing
  • Publication date: 2/1/1999
  • Edition description: 20%
  • Edition number: 2
  • Pages: 264
  • Product dimensions: 6.06 (w) x 9.04 (h) x 0.56 (d)

Meet the Author

Tom DeMarco is a principal of the Atlantic Systems Guild, a computer systems think tank with offices in the U.S. and Great Britain. He was the winner of the 1986 Warnier Prize for "lifetime contribution to the field of computing."

His most recent work is an expanded, second edition of the classic Peopleware: Productive Projects and Teams. In the summer of 1997, Dorset House published his award-winning The Deadline: A Novel About Project Management. It is the story of a veteran software manager who bets his life on a delivery date.

Mr. DeMarco's book of essays, published in 1995, is entitled Why Does Software Cost So Much? (And Other Puzzles of the Information Age), also from Dorset House. His prior works include more than one hundred articles and papers about management and the system development process. In 1990, he served with Tim Lister as co-editors of Software State-of-the-Art: Selected Papers (with Timothy Lister)

Mr. DeMarco's career began at Bell Telephone Laboratories where he served as part of the now-legendary ESS-1 project. In later years, he managed real-time projects for La CEGOS Informatique in France, and was responsible for distributed on-line banking systems installed in Sweden, Holland, France and Finland. He has lectured and consulted throughout the Americas, Europe, Africa, Australia and the Far East.

Mr. DeMarco has a BSEE degree from Cornell University, an M.S. from Columbia University and a diplome from the University of Paris at the Sorbonne. In his spare time, he is an Emergency Medical Technician, certified by his home state and by the National Registry of EMTs, and a founding member of The Penobscot Compact, a business-education partnership operating under the auspices of the Maine State Aspirations Program. He makes his home in Camden, Maine.

Timothy Lister is a principal of the Atlantic Systems Guild and author of two best-selling Dorset House books (the new second edition of Peopleware: Productive Projects and Teams and Software State-of-the-Art: Selected Papers, with Tom DeMarco) and a ground-breaking training video (Productive Teams: A Video, with Tom DeMarco).

Based in Manhattan, Tim divides his time between consulting, teaching, and writing, mostly in the area of risk management for software organizations and projects. Lister also negotiates software disputes for the American Arbitration Association and participates on the Airlie Council of the DoD's Software Program Manager's Network.

Read More Show Less

Table of Contents

Preface to the Second Edition
Preface to the First Edition
Part 1: Managing the Human Resource
Chapter 1: Somewhere Today, a Project Is Failing
Chapter 2: Make a Cheeseburger, Sell a Cheeseburger
Chapter 3: Vienna Waits for You
Chapter 4: Quality-If Time Permits
Chapter 5: Parkinson's Law Revisited
Chapter 6: Laetrile
Part II: The Office Environment
Chapter 7: The Furniture Police
Chapter 8: "You Never Get Anything Done Around Here Between 9 and 5"
Chapter 9: Saving Money on Space
Intermezzo: Productivity Measurement and Unidentified Flying Objects
Chapter 10: Brain Time Versus Body Time
Chapter 11: The Telephone
Chapter 12: Bring Back the Door
Chapter 13: Taking Umbrella Steps
Part III: The Right People
Chapter 14: The Hornblower Factor
Chapter 15: Hiring a Juggler
Chapter 16: Happy to Be Here
Chapter 17: The Self-Healing System
Part IV: Growing Productive Teams
Chapter 18: The Whole Is Greater Than the Sum of the Parts
Chapter 19: The Black Team
Chapter 20: Teamicide
Chapter 21: A Spaghetti Dinner
Chapter 22: Open Kimono
Chapter 23: Chemistry for Team Formation
Part V: It't Supposed to Be Fun to Work Here
Chapter 24: Chaos and Order
Chapter 25: Free Electrons
Chapter 26: Holgar Dansk
Part VI: Son of Peopleware
Chapter 27: Teamicide, Revisited
Chapter 28: Competition
Chapter 29: Process Improvement Programs
Chapter 30: Making Change Possible
Chapter 31: Human Capital
Chapter 32:Organizational Learning
Chapter 33: The Ultimate Management Sin Is
Chapter 34: The Making of Community
About the Authors
Read More Show Less

First Chapter

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:

. . . 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.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 2 Customer Reviews
  • Anonymous

    Posted September 2, 2005

    The way Programmers would like it to be

    Fantastic book about the people side of software development. The ideas in this book, and the typical corporate environment, are worlds apart. My experience has been that managers either don't know this stuff, or if they do know it, then they feel that they would just have to go out on too much of a limb to implement these ideas. This is a shame because most for the concepts in this book are the very things that enable software developers to thrive. One of the main ideas that resonated with me was the idea of giving developers enough private space. I have never been a fan of open plan office space. I think that it works well for some professions, but not all, and certainly not for software developers. Legend has it that Microsoft lets each developer have their own office which they can furnish as they please. One programmer is supposed to have brought in bucket-loads of sand to make his office into a beach ! If you are a Manager then read this book and implement as much as you can. Otherwise buy a copy and leave it on your Managers desk.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted October 12, 2002

    Deep, accurate.

    The main goal of this book is that it encourages the software developers and their management to think about they way they create the software. Software development is the ¿research¿, not the ¿production¿, and the stimulus and processes that work well in for example metallurgy will harm software development. The authors show the consequences of borrowing organizational processes from other areas to software. They encourage to focus on the people rather than to process. Although the textual work of the authors is marvelous, the quality of the printed book (paperback edition) is awful. The paper is thin and translucent, showing the lines from the other pages, the interline spacing is too low, turning a page to a big mess. That's why I've rated the book four stars. The information in this book is very accurate, without pure assertions. The authors always are giving full references if they are providing figures or studies. The authors have a good sense of humor, and it is the great pleasure to read this book. The information is given in the very dense manner: the other authors might have needed ten volumes to express what Tom DeMarco and Timothy Lister has put in this small book. I strongly recommend this book to any individual involved in software development, as well as ¿Agile Software Development¿ by Alistair Cockburn. These books aren¿t from ¿ten steps to success¿ series. They encourage deep, creative approach to the topic.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 2 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)