Big news! LibraryThing is now free to all! Read the blog post and discuss the change on Talk.
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.
Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

Peopleware: Productive Projects and Teams by…

Peopleware: Productive Projects and Teams

by Tom DeMarco, Timothy R. Lister

MembersReviewsPopularityAverage ratingMentions
1,374179,340 (4.36)2
  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.  … (more)
Recently added byConor.Murphy, flint63, barrucadu, wasureru, jlicht, private library, erikogan



Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 2 mentions

English (17)  German (1)  All languages (18)
Showing 1-5 of 17 (next | show all)
The problems we face in building effective teams and effective software are primarily sociological in nature, and attacking them with the same toolbox we use to overcome technological problems is folly at best and completely destructive at worst. The authors break down a host of topics, from pathologies in leadership, to the basic ingredients needed for team gel, to the important factors in a working environment that supports all modes of work for creative workers.

This book is a must for anyone who guides the process of creative work, especially in a technology-driven environment. I know I would benefit from an annual ritual to read and absorb its wisdom.

I am fairly certain I read (or at least started to read) an earlier edition of this book 15 years ago when I was last “leading” a “team” at [REDACTED]. It definitely made an impression on me, but it did not speak to me the way this most recent reading did.

( )
  erikogan | Mar 23, 2020 |
This book is one of the few focused specifically on how to manage projects and teams of knowledge-workers. It teaches the reader how management might retain workers and their essential skills instead of treating them like cattle. It treats the central problem of management is sociology and not technology. Keeping knowledge-workers happy and productive requires humanity and not scorched-earth policies.

The book, in its third edition, is organized into 39 short chapters each with its own focus. As with most management books, its lessons are absorbed in the industry practice. Nonetheless, it is nice to read the thinking and research behind contemporary practice.

Management of people should focus not merely on the goals/objectives of a project but upon the people involved. This is a lesson which is sometimes forgotten by management. The person who works on a project/team is a knowledge worker with feelings, experience, knowledge, and wisdom. One must not only navigate the objectives of a project but also the care of a person. People work best when they are happy and not actively stressed by poor management.
( )
  scottjpearson | Jan 25, 2020 |
The book Peopleware by Tom DeMarco and Tim Lister has recently been released in a 3rd edition, and the topics adressed in it are still very important. Software development is about people: when, how and where they can work together. If you truly are concerned with people, and looking for ways to improve how you collaboratively develop and deliver software, then this book is a must read. ( )
  BenLinders | Jul 30, 2017 |
A good read on how to build strong teams and how to be a good manager. Lots of interesting topics, including the role of product quality, methodologies, schedules, productivity, trust, freedom, and office planning.

Some good quotes from the book:

The major problems of our work are not so much technological as sociological in nature.

We Haven't Got Time to Think About This Job, Only to Do It

Historians long ago formed an abstraction about different theories of value: The Spanish Theory, for one, held that only a fixed amount of value existed on earth, and therefore the path to the accumulation of wealth was to learn to extract it more efficiently from the soil or from people's backs. Then there was the English Theory that held that value could be created through ingenuity and technology. So the English had an Industrial Revolution, while the Spanish spun their wheels trying to exploit the land and the Indians in the New World. They moved huge quantities of gold across the ocean, and all they got for their effort was enormous inflation (too much gold money chasing too few usable goods).

Writing in 1954, the British author C. Northcote Parkinson introduced the notion that work expands to fill the time allocated for it, now known as Parkinson's Law.

Projects [in the Productivity by Estimation Approach study] on which the boss applied no schedule pressure whatsoever ("Just wake me up when you're done.") had the highest productivity of all.

Three rules of thumb seem to apply whenever you measure variations in performance over a sample of individuals: Count on the best people outperforming the worst by about 10:1. Count on the best performer being about 2.5 times better than the median performer. Count on the half that are better-than-median performers outdoing the other half by more than 2:1.

"Anything you need to quantify can be measured In some way that Is superior to not measuring it at all." Gilb's Law doesn't promise you that measurement will be free or even cheap, and it may not be perfect—just better than nothing.

Your people bring their brains with them every morning. They could put them to work for you at no additional cost if only there were a small measure of peace and quiet in the workplace.

The company would love for every one of us to have a window, we hear, but that just isn't realistic. Sure it is. There is a perfect proof that sufficient windows can be built into a space without excessive cost. The existence proof is the hotel, any hotel. You can't even imagine being shown a hotel room with no window.

The best way we've discovered to do this is through the use of auditions for job candidates. The idea is simple enough. You ask a candidate to prepare a ten- or fifteen-minute presentation on some aspect of past work.

The best organizations are not of a kind; they are more notable for their dissimilarities than for their likenesses. But one thing that they all share is a preoccupation with being the best. It is a constant topic in the corridors, in working meetings, and in bull sessions. The converse of this effect is equally true: In organizations that are not "the best," the topic is rarely or never discussed.

The maddening thing about most of our organizations is that they are only as good as the people who staff them. Wouldn't it be nice if we could get around that natural limit, and have good organizations even though they were staffed by mediocre or incompetent people? Nothing could be easier—all we need is (trumpet fanfare, please) a Methodology.

The Hawthorne Effect. Loosely stated, it says that people perform better when they're trying something new.

Believing that workers will automatically accept organizational goals is the sign of naive managerial optimism.

In no time at all, we came up with lots of sure-fire ways to inhibit the formation of teams and disrupt project sociology. These measures, taken together, constitute a strategy we dubbed teamicide. Our short list of teamicide techniques is presented below: defensive management; bureaucracy; physical separation; fragmentation of people' s time; quality reduction of the product; phony deadlines; clique control.

The only freedom that has any meaning is the freedom to proceed differently from the way your manager would have proceeded. This is true in a broader sense, too: The right to be right (in your manager's eyes or in your government's eyes) is irrelevant; it's only the right to be wrong that makes you free.

The heading used here is a facetious one; nobody really talks about quality-reduced products. What they talk about is cost-reduced products. But it usually boils down to the same thing. The typical steps we take to deliver a product in less time result in lower quality. Often the product's end user gives willing consent to this trade-off (less quality for earlier, cheaper delivery). But such concessions can be very painful for the developers. Their self-esteem and enjoyment are undermined by the necessity of building a product of clearly lower quality than what they are capable of.

The common thread is that good managers provide frequent easy opportunities for the team to succeed together. The opportunities may be tiny pilot sub-projects, or demonstrations, or simulations, anything that gets the team quickly into the habit of succeeding together.

The fundamental response to change is not logical, but emotional.

This is part of the reason why response to change is so emotional. It is frustrating and embarrassing to abandon approaches and methods you have long since mastered, only to become a novice again.

Most of us today live in places that aren't really communities at all. People don't know their neighbors very well, they commute out to work someplace else, and nobody expects the kids to settle down in the same town. ( )
  brikis98 | Nov 11, 2015 |
It's about the software engineer's paradise and the small steps you can take to make it real. Recommended to everyone. ( )
  valdanylchuk | Aug 26, 2015 |
Showing 1-5 of 17 (next | show all)
no reviews | add a review

» Add other authors (2 possible)

Author nameRoleType of authorWork?Status
Tom DeMarcoprimary authorall editionscalculated
Lister, Timothy R.main authorall editionsconfirmed
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Series (with order)
Canonical title
Original title
Alternative titles
Original publication date
Important places
Important events
Related movies
Awards and honors
First words
Last words
Disambiguation notice
Publisher's editors
Publisher series
Original language
Canonical DDC/MDS

No library descriptions found.

Book description
Haiku summary

Quick Links

Popular covers


Average: (4.36)
1 2
2 4
3 24
3.5 7
4 83
4.5 10
5 129

Is this you?

Become a LibraryThing Author.


About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 146,362,800 books! | Top bar: Always visible