Peopleware : Productive Projects and Teams, 2nd Ed. 
asked by avi on November 22, 2006 11:32 AM
Peopleware asserts that most software development projects fail because of failures within the team running them. This strikingly clear, direct book is written for software development-team leaders and managers, but it's filled with enough commonsense wisdom to appeal to anyone working in technology. Authors Tom DeMarco and Timothy Lister include plenty of illustrative, often amusing anecdotes; their writing is light, conversational, and filled with equal portions of humor and wisdom, and there is a refreshing absence of "new age" terms and multistep programs. The advice is presented straightforwardly and ranges from simple issues of prioritization to complex ways of engendering harmony and productivity in your team. Peopleware is a short read that delivers more than many books on the subject twice its size.
Reviews
0%
0%
I found in this book a really bright analysis for any organization. I like the approach, and I've found a lot of very useful tips for my proffesional life
reviewed by macfan on November 28, 2006 2:11 AM
0%
0%
Tom DeMarco writes classics about software development. Peopleware (1987 but updated version has since come out) is about people who develop software. It's about you. What people are like -- what works and what doesn't on topics such as working space, interruptions, how people work together in teams. What really goes on between 9 and 5, why, and what managers can help do to make it better. Don't expect coding theory in this one. Do expect common sense where DeMarco voices what people know but didn't say.
reviewed by caramel on November 29, 2006 12:52 AM
0%
0%
This book is full of information of things that current managers have forgotten. Every new project is wanted done with less money, less time and with higher quality than old projects, putting a lot of pressure to the project team. Managers do things that they believe is good for the project but actually damages the project (and the company) at long term. I have seen many co-workers leave my company for issues like the ones described in this book. Managers and company owners: Please read it!!!
reviewed by fabio on November 29, 2006 1:46 PM
0%
0%
This book takes a look at the role people, specifically creative people, play in a company. It offers various insights into management, the environment, and team "building". The second edition also adds a final section with eight new chapters with later insights.
While I agreed with much of what was written, there were some noticeable gaps such as mentoring, and business training (as opposed to technical training). Also, some of the content was, at this point, cliché (such as not treating people as widgets or, specifically, creative people as factory line workers, and the value of team "jelling").
Nonetheless, there is original content, and thoughtful suggestions, and the book is an enjoyable read.
While I agreed with much of what was written, there were some noticeable gaps such as mentoring, and business training (as opposed to technical training). Also, some of the content was, at this point, cliché (such as not treating people as widgets or, specifically, creative people as factory line workers, and the value of team "jelling").
Nonetheless, there is original content, and thoughtful suggestions, and the book is an enjoyable read.
reviewed by shagdag on November 29, 2006 7:17 PM
0%
0%
First of all let me thank people responsible for making this book.
This book mainly talks about people, office environment, work environment, team etc. Eventhough, it is definite must read book for managers who manage software or software type of works(Application Specific Hardware, ASIC, VLSI, etc), it is highly recommended book for anyone from junior engineer to CEO.
Read this book to know,
- why somewhere today some projects are failing?
- why managers like to manage technology than people?
- how far do we need to push the quality of a product?
- how much space and facility should we need?
- what are the side effects of working overtime?
- what are the fundamental response to change?
and many more.
Excellent advise, best insight into the organizations, classic work area facts in simple plain English.
This book mainly talks about people, office environment, work environment, team etc. Eventhough, it is definite must read book for managers who manage software or software type of works(Application Specific Hardware, ASIC, VLSI, etc), it is highly recommended book for anyone from junior engineer to CEO.
Read this book to know,
- why somewhere today some projects are failing?
- why managers like to manage technology than people?
- how far do we need to push the quality of a product?
- how much space and facility should we need?
- what are the side effects of working overtime?
- what are the fundamental response to change?
and many more.
Excellent advise, best insight into the organizations, classic work area facts in simple plain English.
reviewed by drvale on November 29, 2006 7:27 PM