Peopleware: Productive Projects and Teams (Second Edition) [Paperback]

Tom DeMarco (Author), Timothy Lister (Author)

Book Description

Publication Date: February 1, 1999

Demarco and Lister demonstrate that the major issues of software development are human, not technical. Their answers aren't easy--just incredibly successful. New second edition features eight all-new chapters. Softcover. Previous edition: c1987. DLC: Management.

Product Details

• Paperback: 245 pages
• Publisher: Dorset House; 2nd edition (February 1, 1999)
• Language: English
• ISBN-10: 0932633439
• ISBN-13: 978-0932633439
• Product Dimensions: 6.1 x 9 inches
• Shipping Weight: 12 ounces (View shipping rates and policies)
• Average Customer Review: 4.7 out of 5 stars  See all reviews (95 customer reviews)
• Amazon Best Sellers Rank: #18,950 in Books (See Top 100 in Books)
  • #21 in Books > Computers & Technology > Business & Management > Project Management > PMP Exam
  • #61 in Books > Business & Investing > Industries & Professions > Human Resources & Personnel Management
  • #94 in Books > Business & Investing > Organizational Behavior > Workplace

Most Helpful Customer Reviews

215 of 217 people found the following review helpful

5.0 out of 5 stars Hard numbers on good work environments February 25, 2001

By David Walker

Format:Paperback

Summed up in one sentence, Peopleware says this: give smart people physical space, intellectual responsibility and strategic direction. DeMarco and Lister advocate private offices and windows. They advocate creating teams with aligned goals and limited non-team work. They advocate managers finding good staff and putting their fate in the hands of those staff. The manager's function, they write, is not to make people work but to make it possible for people to work.

Why is Peopleware so important to Microsoft and a handful of other successful companies? Why does it inspire such intense devotion amongst the elite group of people who think about software project management for a living? Its direct writing and its amusing anecdotes win it friends. So does its fundamental belief that people will behave decently given the right conditions. Then again, lots of books read easily, contain funny stories and exude goodwill. Peopleware's persuasiveness comes from its numbers - from its simple, cold, numerical demonstration that improving programmers' environments will make them more productive.

The numbers in Peopleware come from DeMarco and Lister's Coding War Games, a series of competitions to complete given coding and testing tasks in minimal time and with minimal defects. The Games have consistently confirmed various known facts of the software game. For instance, the best coders outperform the ten-to-one, but their pay seems only weakly linked to their performance. But DeMarco and Lister also found that the best-performing coders had larger, quieter, more private workspaces. It is for this one empirical finding that Peopleware is best known.

(As an aside, it's worth knowing that DeMarco and Lister tried to track down the research showing that open-plan offices make people more productive.... It didn't exist. Cubicle makers just kept saying it, without evidence - a technique Peopleware describes as "proof by repeated assertion".)

Around their Coding Wars data, DeMarco and Lister assembled a theory: that managers should help programmers, designers, writers and other brainworkers to reach a state that psychologists call "flow" - an almost meditative condition where people can achieve important leaps towards solving complex problems. It's the state where you start work, look up, and notice that three hours have passed. But it takes time - perhaps fifteen minutes on average - to get into this state. And DeMarco and Lister that today's typical noisy, cubicled, Dilbertesque office rarely allows people 15 minutes of uninterrupted work. In other words, the world is full of places where a highly-paid and dedicated programmer or creative artist can spend a full day without ever getting any hard-core work. Put another way, the world is full of cheap opportunities for people to make their co-workers more productive, just by building their offices a bit smarter.

A decade and a half after Peopleware was written, and after the arrival of a new young breed of IT companies called Web development firms, it would be nice to think DeMarco and Lister's ideas have been widely adopted. Instead, they remain widely ignored. In an economy where smart employees can increasingly pick and choose, it will be interesting to see how much longer this ignorance can continue. Read more ›

312 of 325 people found the following review helpful

5.0 out of 5 stars Anyone managing software projects should read this! March 30, 2000

By Joel Spolsky

Format:Paperback

As summer interns at Microsoft, my friends and I used to take "field trips" to the company supply room to stock up on school supplies. Among the floppy disks, mouse pads, and post-it notes was a stack of small paperback books, so I took one home to read.

The book was Peopleware, by Tom DeMarco and Timothy Lister. This book was one of the most influential books I've ever read. The best way to describe it would be as an Anti-Dilbert Manifesto.

Ever wonder why everybody at Microsoft gets their own office, with walls and a door that shuts? It's in there. Why do managers give so much leeway to their teams to get things done? That's in there too. Why are there so many jelled SWAT teams at Microsoft that are remarkably productive? Mainly because Bill Gates has built a company full of managers who read Peopleware. I can't recommend this book highly enough. It is the one thing every software manager needs to read... not just once, but once a year.

72 of 73 people found the following review helpful

5.0 out of 5 stars An absolute must-read! December 16, 1999

By Sean Kelly

Format:Paperback|Amazon Verified Purchase

I cannot overstate just how great this book is!

DeMarco and Lister don't mess around. They go right to the heart of project and team management and tell you exactly what makes one company succeed while so many others fail: it's not technology, it's people.

With reckless abandon, they attack cubicles, dress codes, telephones, hiring policies, and company core hours and demonstrate how managers who are not insecure about their positions, who shelter their employees from corporate politics, who, in short, make it possible for people to work are the ones who complete projects and whose employees have fun doing so. The authors use no-nonsense writing, statistical evidence, and even humorous anecdotes to drive their points home.

While the first edition was as appropriate to today's corporate cultures as it ever was, the authors have added analysis of some of the latest trends in management in this new second edition, and show what's good and what's not. The update includes coverage of the dangers of constant overtime, the stupidity of motivational posters, the side effects of process improvement programs, how to make change possible, and the costs of turnover. As with the rest of the book, all topics receive thorough and thoughtful treatment.

Although the book is weighed heavily towards software engineering projects, you'll find that much of what DeMarco and Lister say apply to projects where creativity and analytical skills are required. If you're a manager of such a project, consider this book required reading before you do anything else today. If you're a team member on such a project, buy a copy for your boss, and an extra one for your boss's boss....

One final note: I'd wager that Scott Adams, creator of Dilbert, must use this book as inspiration for his comic strip. Dilbert's encounters with his moronic boss and idiotic company policies seem to come right from the pages of Peopleware's advice on what not to do. Read more ›

25 of 26 people found the following review helpful

5.0 out of 5 stars The truth behind the failure of software projects December 29, 1999

By Charles Ashbacher HALL OF FAMETOP 500 REVIEWERVINE™ VOICE

Format:Paperback

Programming languages come and go with an occasional paradigm shift thrown in. However, the thought processes and the mental gyrations needed to complete large software projects remain largely unchanged in the decade since the first edition of this book was published. Unfortunately, management skills also remained stagnant as well. In this book, the authors lay out the ugly truth as to why much of software development fails. It is not a lack of technical or technological competence on the part of developers, but a strong tendency by management to treat programmers as mere code generators possessing accelerator buttons. Simply prod, bribe, threaten, cajole or berate them and the button is pressed causing them to work overtime with a smile, with no associated loss of productivity. The authors lay out examples of all of these techniques.
Quality developers must possess a great deal of originality, creativity and pride in what they do. Destroy that using the techniques listed in this book and the consequences are obvious. Even brown, scorched earth looks green by comparison and the quality people depart. A large percentage, perhaps even the majority, of software development projects fail. Many studies support the position that it is largely a failure of middle management. Millions of dollars could be saved if all who fall into that category would read this book and have the courage to act on what they read. Unfortunately, that will probably not happen. After all, the authors did come out with a second edition, didn't they?