Browse the Knowledge Hub211 resources
Peopleware: is it worth reading?
The argument that software problems are sociological rather than technological, made in 1987 and still unanswered.
We earn nothing from any link on this page. No affiliate links anywhere in this library.
- published
- 2013
- key ideas
- 3
- reading path
- 1
Peopleware
Productive Projects and Teams
by Tom DeMarco, Timothy Lister
- Publisher
- Addison-Wesley
- Year
- 2013
- Edition
- Third edition. The first appeared in 1987 and the core argument is unchanged.
- ISBN
- 9780321934116
Useful when you are: Senior / lead, Manager
Verdict
Should you read it?
Read it if
You manage anyone, or you are trying to understand why a technically capable team delivers badly.
Skip it if
You want technical content. There is none.
The argument
What it argues
The major problems of software work are not technological but sociological. Projects fail because of how people are organised, interrupted, measured and housed, far more often than because of technical difficulty.
The book covers the cost of interruption and the time it takes to regain flow, why open-plan offices measurably reduce productivity, how teams gel and what management reliably does to prevent it, and why measuring individual productivity in knowledge work produces worse outcomes.
The relevance to quality is direct: almost everything that makes testing ineffective is organisational rather than technical, and this book is the clearest statement of why.
Key ideas
Ideas worth taking from it
- 01
Flow and the cost of interruption
Knowledge work requires sustained concentration, and the recovery time after an interruption is substantial. An argument against the ambient interruption most offices normalise.
- 02
Teamicide
The specific management behaviours that prevent teams from gelling: defensive management, bureaucracy, physical separation, fragmentation of people across projects.
- 03
You cannot measure individual productivity
Attempts to do so in knowledge work distort behaviour and damage the thing being measured. Directly applicable to measuring testers by defect count.
Criticism
What has dated, and what it gets wrong
The office design material assumes everyone is co-located and has dated considerably in a remote and hybrid world, though the underlying point about interruption transfers. Some evidence is anecdotal or from studies that would not satisfy a modern reader, and the tone is occasionally smug.
Reading paths
On our reading paths
Leading a quality team
Book 1 of 4 · QA and engineering managers
The classic argument that most project failures are sociological rather than technical, and still the best book on the conditions people need to do good work.
- 1. Peopleware (this book)
2. The Mythical Man-Month
3. Team Topologies
4. The Manager's Path
Keep reading
What to read next
Reads well with
Reading about quality is cheaper than learning it in production.
QAble runs QA for products in BFSI, gaming, healthcare and SaaS, with engineers who have read these and argued about them. Start with a free QA audit.