Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Peopleware

Peopleware

Productive Projects and Teams
Why do talented software teams fail, and what can managers change before the next project?
by Tom DeMarco 1987 272 pages
4.14
9k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat project failure as a people-system problem, not a technology mystery

Look behind the tools. DeMarco and Lister argue that projects often fail because people cannot coordinate, trust one another, or stay motivated, not because the technology is impossible. Their surveys of more than 500 development projects found that about 15 percent were abandoned or delivered products nobody used. Among projects lasting at least 25 work-years, the failure rate reached 25 percent. For most failed projects they investigated, technology did not explain the outcome.

Name the real problem. Participants often called the cause “politics,” but used that label for everything from poor communication to turnover. The authors call these problems sociology, a more precise term that makes them seem manageable rather than mysterious. Their warning about the High-Tech Illusion is that applying advanced tools does not make a team’s work primarily technological. Much of the job is still human communication.

Analysis

What's striking is the shift in the manager's field of attention: from the visible technical puzzle to the less visible conditions that let people solve it together. This aligns with sociotechnical thinking, which treats tools, roles, and relationships as one working system. The distinction is useful, but not absolute. Technical failures can trigger social breakdown, and social conflict can expose real design flaws. The practical lesson is not to demote technology, but to stop treating it as a universal explanation or cure.

Treat office design as production infrastructure, not a facilities expense

Space shapes performance. In the authors' Coding War Games, more than 600 developers from 92 companies completed the same programming task in their normal workplaces. The best-performing quarter worked in quieter, more private, less interruptive spaces with more room. Their average performance was 2.6 times that of the bottom quarter. Across organizations, the strongest and weakest performers differed by more than tenfold.

The evidence has limits. The study showed a relationship, not proof that office design alone caused better work. Still, the authors argue that space is too consequential to leave entirely to facilities planners. They cite IBM's Santa Teresa study, which recommended roughly 100 square feet per worker and meaningful noise protection. Saving a modest amount on space can be a poor bargain if it makes concentrated work harder or pushes skilled people away.

Analysis

The book's most persuasive move is economic: it compares the small, visible price of space with the much larger, poorly measured value of skilled labor. This is a classic accounting blind spot. Yet privacy is not a universal preference, and some tasks benefit from easy interaction. The useful design question is therefore not open versus closed office as an ideology. It is whether workers can choose between collaboration and quiet, and whether the workplace supports the tasks actually being done.

Protect uninterrupted thinking time as a core project resource

Deep work needs a runway. The authors use the term flow for sustained concentration in which complex work can proceed without repeated resets. They estimate that a worker may need 15 minutes or more to regain full concentration after an interruption. A five-minute phone call can therefore cost substantially more than five minutes of useful work. A day chopped into tiny intervals may look busy on a timesheet while producing little thoughtful progress.

Count usable time. The Environmental Factor, or E-Factor, is uninterrupted work hours divided by hours present. The authors found values ranging from 0.10 to 0.38 among sites in one large agency, with higher values in quieter offices. They suggest tracking uninterrupted time to reveal whether a workplace permits concentration. Simple signals, such as a shared do-not-disturb cue, can help make focused time socially acceptable.

Analysis

The distinction between time present and time cognitively available anticipates modern attention research: task switching imposes costs even when each switch seems brief. The E-Factor is valuable less as a universal performance score than as a diagnostic prompt. It can expose whether interruptions are structural rather than personal failures of discipline. Its limitation is that uninterrupted time is not automatically productive. Measurement should support workers' control over attention, not become another quota that turns concentration into a compliance exercise.

Don't confuse overtime with productivity; count quality and turnover

Hours can disguise waste. The authors call pressure for unpaid extra labor “Spanish Theory” management: trying to extract more value from people instead of improving what they can accomplish in an hour. They argue that salaried workers often compensate for overtime with slower or less effective periods later. Under relentless pressure, people may move faster while sacrificing quality. In one cited project at Data General, the team worked extreme hours, then virtually the entire development staff left.

Include the full bill. The book estimates that replacing a departing worker can cost four-and-a-half to five months of employee expense, including hiring and ramp-up. It also argues that builders' pride is often tied to product quality, so forced compromises can damage both morale and output. Productivity should include the value delivered, the cost of producing it, the quality achieved, and the people lost along the way.

Analysis

This is a useful correction to short-term productivity accounting: labor is not a tap that can be opened indefinitely without consequences. The broader idea resembles total-cost analysis, where downstream effects belong in the original decision rather than in a separate budget. The authors' numerical estimates come from their own observations and should not be treated as universal rates. Still, the direction of the argument is robust: an apparent gain that consumes expertise, reliability, or retention may be a loss wearing a favorable spreadsheet.

Assess the work itself, then let future peers judge the fit

Ask for evidence. The authors compare hiring a developer without reviewing past work to hiring a juggler without watching a performance. A portfolio gives candidates a chance to show designs, code, or other relevant artifacts, while giving interviewers something concrete to discuss. They also recommend an audition: a short presentation on work the candidate chooses, attended by prospective colleagues. This reveals communication ability and lets the team contribute to the decision.

Make room for difference. Hiring for a familiar appearance or style can reproduce an organization's existing blind spots. The authors caution that standardized aptitude tests may predict narrow early tasks while missing broader abilities needed later. A strong hiring process looks beyond polish and similarity to evidence of competence, learning, and collaboration. Peer input can also make a new hire's arrival smoother because colleagues have helped choose the person.

Analysis

Work samples improve on interviews by shifting evaluation from impression to performance, a principle shared with structured auditions in other professions. Peer participation can also surface whether someone communicates well with the people they will actually work beside. Still, a portfolio may reflect unequal access to prestigious projects, and an audition can reward confidence over substance. Fair evaluation requires relevant tasks, consistent criteria, and a way for candidates to explain their contribution rather than merely display a polished artifact.

Grow teams by removing the habits that prevent them from bonding

A team must gel. The authors call a strongly bonded group a jelled team: its members align around a shared goal, feel ownership of the work, and often produce more effectively than they would separately. The authors stress that managers cannot manufacture this bond on command. They can, however, avoid teamicide, their term for practices that obstruct team formation. Examples include distrustful oversight, bureaucratic paperwork, separating colleagues, splitting people's time across projects, fake deadlines, and breaking up successful groups.

Create chances to succeed. In the spaghetti-dinner story, a manager invites a new project group to cook and eat together. The small shared accomplishment gives them a first experience of coordinating as peers. The larger lesson is to provide frequent, meaningful opportunities for a group to succeed together. Keep its membership stable enough to build relationships, and give it a worthwhile standard of work to rally around.

Analysis

The agricultural metaphor matters: it replaces a manager's fantasy of direct control with attention to conditions, time, and maintenance. Research on psychological safety similarly emphasizes that people contribute more freely when they can take interpersonal risks without humiliation. But cohesion is not automatically good. Strong groups can exclude outsiders or defend their own norms too aggressively. A healthy team needs both internal trust and channels for dissent, accountability, and cooperation beyond its own boundary.

Lead by making good work possible, not by policing every move

Leadership can be service. The book contrasts authority used to extract more work with leadership that helps a group function. A tennis organizer who arranges fair matches, handles scheduling, and supports the players leads without needing a formal title. In project settings, the equivalent is clearing obstacles, providing direction where needed, and making it easier for capable people to do their jobs.

Trust requires real freedom. The authors call an autonomy-based style “Open Kimono” management: the manager accepts the risk of trusting employees with meaningful responsibility instead of protecting against every possible mistake. One project manager sent her team away to work uninterrupted for more than two weeks, staying behind to screen distractions. They returned with a complete design. The point is not to abandon oversight, but to judge work by its results rather than by constant visual supervision.

Analysis

This account distinguishes leadership from mere authority: leadership is demonstrated by improving the group's capacity to act, not by occupying the most visible role. That connects with servant leadership and distributed leadership, where expertise and initiative move among team members. The challenge is calibration. Trust does not remove the need for clear goals, feedback, or responsible escalation. Autonomy works best when people have the competence and information to use it, and when a mistake can be surfaced early rather than concealed.

Prefer adaptable methods over rulebooks that do the thinking for people

Preserve local judgment. The authors distinguish small-m methodology, a practical approach held by the people doing the work, from capital-M Methodology: a prescriptive system that dictates steps in advance. They argue that rigid systems can turn skilled workers into rule followers, inflate paperwork, and weaken responsibility. In human organizations, some ability to improvise is valuable. The authors call this self-healing: people recognize an unusual situation and adjust their response without rebuilding the entire process.

Standardize by learning. The book does not reject common methods. It argues that training, useful tools, and peer review can encourage teams to converge on methods that have proved themselves. A standard should codify demonstrated practice, not impose an untested theory. The authors also warn against productivity “miracles” sold through new tools or languages. Such changes may help, but they cannot replace the communication, analysis, and judgment that make up much of knowledge work.

Analysis

The distinction between guidance and prescription remains important in complex work. Rules can reduce avoidable errors, especially in safety-critical or repeatable tasks, while rigid scripts can fail when the situation departs from assumptions. The stronger design is often a clear boundary around outcomes and safety, with discretion over the route. The authors' concern is not standardization itself, but standards that transfer judgment away from the people closest to the work and then leave them responsible for the consequences.

Stop spending whole teams' attention on meetings, messages, and divided assignments

Respect collective time. The authors distinguish working meetings, which end when a decision is reached, from ceremonies that mainly provide updates or reassure a manager. A recurring status meeting with no shared decision to make may be better replaced by brief conversations or written updates. They make a similar point about e-mail: messages copied widely “for information” often impose reading and decision costs without helping recipients act.

Fragmentation has hidden costs. A worker assigned to several projects must repeatedly change context, especially when design work is mixed with urgent phone support. The restart cost is largely invisible, so timesheets may record presence while missing lost concentration. The authors recommend limiting meeting attendance, asking what result ends each meeting, and reducing unnecessary copying and parallel assignments. Coordination should help colleagues coordinate themselves, not make every interaction depend on a manager.

Analysis

The section reframes communication as a cost that must earn its place, rather than as an unqualified good. That is particularly relevant where digital tools make sending nearly free but receiving remains expensive. Yet fewer messages do not always mean better coordination: distributed teams and high-risk decisions may need explicit records and broad consultation. The useful test is whether a communication changes a decision, prevents a foreseeable failure, or gives someone information needed for action. If not, it is probably organizational noise.

Budget for the messy middle of change, not just the promised new routine

Change includes a difficult passage. The Satir Change Model describes movement from an old normal through disruption and a period of confusion, toward practice and a new normal. When people first use an unfamiliar method, their performance may dip because they are learning. Treating that temporary disorder as proof of failure can send an organization back to its old habits before the new ones have a fair test. The authors argue that people need enough safety to learn without being shamed for stumbling.

Plan for your own failure. Risk management should include the chance that the project team misses its goal, even when that possibility feels disloyal to the mission. The book uses Denver's airport baggage system to show the cost of having no backup plan when a central system is late. Organizational learning also depends on retaining people who carry skills and experience. A group that repeatedly loses its staff may keep accumulating years of experience without turning them into better practice.

Analysis

The model offers managers a map for interpreting temporary decline without pretending every change is wise. Its strongest implication is procedural: protect the learning period, define evidence of progress, and keep a fallback available. The Denver example also reflects a general resilience principle: contingency plans are not expressions of pessimism but preparations that make ambitious work safer. Still, a difficult transition is not automatically a productive one. Leaders need criteria for distinguishing a normal learning dip from evidence that the chosen change is fundamentally flawed.

Build a workplace community worth staying for, not merely a job worth tolerating

Belonging has practical value. The authors describe community as a source of loyalty, shared responsibility, and continuity. Their examples range from retraining employees for new roles to a company school whose children's daily procession through the workplace brought colleagues together. Shared meals, celebrations, and informal contact can give people a reason to identify with one another beyond their task lists.

Make room for energy. The book argues that work can be serious without being joyless. Pilot projects, brainstorming, retreats, and playful team events introduce novelty and give people shared experiences. A “free electron” is a self-directed employee given room to define a useful role, rather than a narrow list of tasks. These practices are not substitutes for fair pay or good management. They help make an organization a place where people can grow, contribute, and choose to remain.

Analysis

Community is presented not as workplace decoration but as social infrastructure: it supports trust, knowledge exchange, and continuity. The connection to human capital is concrete, since skills and local knowledge take time to build and disappear when experienced people leave. There is also a boundary to respect. Work should not be asked to replace family, friendships, or civic life, and belonging can become pressure to conform. The strongest workplace communities leave room for individuality and make participation meaningful rather than compulsory.

Analysis

Peopleware's central argument is that complex technical work is inseparable from the conditions under which people communicate, concentrate, learn, and remain together. Its memorable contrast is not people versus technology, but production logic versus development logic. A production line benefits from repeatability and interchangeable components. A project depends on judgment, adaptation, and relationships that cannot be swapped out without cost. The practical consequence is striking: management's job is often less about directing each task than shaping an environment in which competent people can do difficult work.

The book's breadth is a strength and a challenge. Its essays connect office design, hiring, quality, team identity, risk, meetings, and organizational learning through one recurring question: what makes good work possible? This gives the collection coherence without pretending there is one master technique. The authors repeatedly favor enabling conditions over control: quiet space, stable teams, credible deadlines, peer learning, and discretion. Their examples also make management abstractions tangible, from the Black Team's shared identity to the group that builds dinner together before starting a project.

Some claims need historical distance. The Coding War Games and project surveys are useful evidence, but many are observational, drawn from software workplaces of earlier decades, and cannot establish causation by themselves. The book sometimes speaks broadly about workers, productivity, and quality where roles and industries differ. Its suspicion of standardization also needs qualification: procedures can protect safety, reliability, and newcomers when they preserve rather than replace judgment.

The enduring value is therefore not a prescription to abolish process or celebrate every tightly bonded team. It is a managerial discipline of asking what a policy costs in attention, initiative, quality, and retention, alongside what it saves. That question turns seemingly soft matters into operational concerns. A manager who takes sociology seriously still cares about delivery. The difference is that people are no longer treated as a hidden input to the technical system. They are the system's central capability.

Summary in 30 Seconds
Complex projects depend on communication, trust, and sustained concentration as much as on technical skill. Quiet, private workspaces were associated with stronger performance, while interruptions can cost 15 minutes or more of recovery. Long hours may damage quality and drive departures, with replacing one worker estimated to cost four and a half to five months of salary and expenses. Stable teams, peer-informed hiring, local judgment, and room to learn help people deliver and stay.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.14 out of 5
Average of 9k+ ratings from Goodreads and Amazon.

Peopleware is widely praised as an essential read for managers and software professionals. Readers appreciate its focus on the human aspects of project management rather than technical issues. Key themes include creating productive work environments, building effective teams, and avoiding common management pitfalls. Many reviewers note the book's enduring relevance despite its age. While some find certain sections outdated, most agree the core principles remain valuable. Critics cite occasional repetitiveness and anecdotal evidence, but overall the book is highly recommended for its insights into team dynamics and management practices.

Your rating:
4.51
278 ratings
Want to read the full book?

Glossary

High-Tech Illusion

Technology over human work

The mistaken belief that people who apply computers or other advanced tools are principally engaged in high-technology work. DeMarco and Lister argue that much project work is actually communication: understanding needs, coordinating decisions, and translating human goals into workable systems.

Spanish Theory

Extract more labor

The authors' label for a productivity mindset that assumes value is fixed and can be increased mainly by extracting more effort from workers. In practice, it often appears as pressure for unpaid overtime or tighter deadlines, rather than investment in better methods, working conditions, or product quality.

Flow

Sustained focused work

A state of deep concentration in which a person becomes absorbed in a demanding task and can work effectively without frequent changes of attention. The book argues that design and development work often depend on this state, which takes time to enter and can be disrupted by interruptions.

E-Factor

Uninterrupted time ratio

The Environmental Factor, calculated as uninterrupted work hours divided by hours spent at work. The authors use it to assess whether a workplace provides a reasonable opportunity for concentration. A low value can signal that noise, interruptions, or work organization are preventing people from reaching sustained focus.

Jelled team

A bonded, aligned group

A group whose members share a strong identity, align around a common goal, and take joint ownership of their work. The authors argue that such a group can produce more effectively and enjoy the work more than the same individuals operating as a loose collection. Managers can encourage the conditions for jelling but cannot command it.

Teamicide

Practices that prevent bonding

The authors' term for organizational habits that inhibit a team's ability to form or stay together. Examples include distrustful oversight, bureaucratic burdens, physical separation, splitting workers across projects, fake deadlines, and breaking up successful groups. These practices can damage both team cohesion and the work itself.

Open Kimono

Trust through real autonomy

A management attitude in which leaders place genuine trust in employees by giving them responsibility and meaningful freedom to act. Rather than trying to prevent every mistake through surveillance or approval gates, the manager accepts some risk and judges the work by its results.

Methodology

Prescriptive work system

In the book, capital-M Methodology means a comprehensive, centrally defined set of rules intended to prescribe how a class of work must be done. The authors distinguish it from small-m methodology, the practical approach and skills used by the people doing a particular job. Their critique targets rules that displace local judgment.

Self-healing system

People adapt as needed

A human-run system can respond to an unforeseen situation because its participants understand the system's goals and can improvise a sensible solution. The authors argue that fully deterministic procedures may lose this flexibility, since they can only produce responses explicitly anticipated by their designers.

Satir Change Model

Stages of organizational change

A model of change associated with family therapist Virginia Satir. It describes an old status quo disrupted by a foreign element, followed by a period of chaos, a transforming idea, practice and integration, and a new status quo. The book uses it to explain why a temporary decline in confidence or performance can accompany learning.

Free electrons

Self-directed organizational contributors

A term for employees who are motivated and capable enough to define much of their own work. Instead of a narrowly specified assignment, they may receive a broad charter, such as exploring a new method or designing a training program. The organization benefits by giving such people room to pursue useful work.

FAQ

What's Peopleware: Productive Projects and Teams about?

  • Human Factors Focus: The book emphasizes that the primary challenges in project management are sociological rather than technological, highlighting the importance of understanding team dynamics and human behavior.
  • Team Dynamics and Environment: It explores how team chemistry, interpersonal relationships, and the physical workspace impact productivity and project outcomes.
  • Management Insights: The authors provide insights into effective management practices that foster team cohesion and productivity, encouraging a focus on building community and trust within teams.

Why should I read Peopleware: Productive Projects and Teams?

  • Insightful Management Strategies: The book offers practical advice for managers on improving team productivity and morale, challenging conventional practices that prioritize technology over people.
  • Timeless Relevance: Despite being published in the 1980s, the principles remain relevant in today’s work environments, making it a valuable read for modern managers.
  • Real-World Examples: The authors share numerous case studies and anecdotes, making the content relatable and actionable for readers.

What are the key takeaways of Peopleware: Productive Projects and Teams?

  • Sociological Over Technological: The authors assert that the major problems in work are more sociological than technological, encouraging a focus on team dynamics and communication.
  • Jelled Teams: The concept of a "jelled team" is central, describing a group that works together seamlessly and effectively, often outperforming individual efforts.
  • Avoiding Teamicide: The book outlines practices that can kill team spirit and productivity, advising managers to avoid these pitfalls to maintain a healthy work environment.

What are the best quotes from Peopleware: Productive Projects and Teams and what do they mean?

  • "The Great Oz has spoken.": Reflects the often unquestioned authority of management decisions, suggesting leaders should be open to feedback and collaboration.
  • "You never get anything done around here between 9 and 5.": Highlights inefficiencies in typical office environments, where interruptions hinder productivity.
  • "The whole is greater than the sum of the parts.": Emphasizes the power of teamwork, indicating that collaborative efforts can yield results that exceed individual contributions.

What is the concept of a "jelled team" in Peopleware: Productive Projects and Teams?

  • Definition: A jelled team is one where members are closely knit, functioning as a cohesive unit, leading to enhanced productivity and job satisfaction.
  • Characteristics: These teams exhibit low turnover, a strong sense of identity, and a shared commitment to their goals, with members taking pride in their collective achievements.
  • Impact on Success: Once a team begins to jell, their chances of success increase dramatically, becoming highly motivated and capable of overcoming significant challenges together.

How does Peopleware: Productive Projects and Teams address the issue of management by objectives (MBO)?

  • Critique of MBO: The authors criticize MBO for potentially undermining team cohesion and motivation, fostering competition rather than collaboration.
  • Alternative Approaches: Advocates for creating a shared vision and goals that all team members can rally around, encouraging cooperation and a sense of collective purpose.
  • Long-term Success: By focusing on team alignment rather than individual performance metrics, organizations can achieve better long-term results, building a more engaged workforce.

What is the High-Tech Illusion mentioned in Peopleware: Productive Projects and Teams?

  • Misplaced Focus on Technology: Refers to the belief that technology is the primary driver of success, often leading to neglecting the human aspects of work.
  • Reality of Human Interaction: Emphasizes that successes stem from good human interactions, underscoring the importance of communication and collaboration over mere technological advancements.
  • Need for Balance: Encourages managers to balance attention between technology and the people who use it, recognizing that effective teamwork is essential for leveraging technology successfully.

How does Peopleware: Productive Projects and Teams define effective team management?

  • Understanding Team Dynamics: Involves recognizing the unique contributions of each member and fostering a collaborative environment, where the whole is greater than the sum of the parts.
  • Encouraging Open Communication: Promotes transparency and open dialogue among team members to build trust and improve collaboration, addressing issues before they escalate.
  • Creating a Supportive Environment: Advocates for a work environment that allows for creativity and innovation, where the best workers know enough to keep silent and roll their eyes.

How does Peopleware: Productive Projects and Teams suggest hiring practices should change?

  • Focus on Skills and Fit: Recommends prioritizing candidates' skills and their fit within the team, emphasizing the importance of seeing candidates' work samples.
  • Use of Auditions: Suggests implementing auditions for candidates to provide insight into their abilities and communication, assessing potential hires in a practical context.
  • Avoiding Aptitude Tests: Critiques reliance on aptitude tests, arguing they often measure the wrong skills, suggesting a focus on real-world performance and team dynamics.

What role does the physical workspace play in productivity according to Peopleware: Productive Projects and Teams?

  • Impact of Noise and Interruptions: Argues that a noisy and disruptive environment can severely limit productivity, highlighting the need for quiet spaces.
  • Importance of Privacy: Suggests that a workspace allowing for privacy and concentration is essential for effective work, with spaces catering to comfort.
  • Designing for Collaboration: Advocates for physical layouts that facilitate teamwork while providing areas for individual work, ensuring spaces are functional.

How does Peopleware: Productive Projects and Teams address the issue of employee turnover?

  • Understanding Turnover Costs: Explains that high turnover rates can be costly, both financially and in terms of team cohesion, creating a cycle of instability.
  • Creating a Sense of Community: Suggests fostering a sense of belonging and community among employees to reduce turnover, with organizations striving to be the best.
  • Investing in Employee Development: Argues that providing opportunities for growth and development enhances employee satisfaction and loyalty, essential for long-term success.

What strategies does Peopleware: Productive Projects and Teams recommend for improving team productivity?

  • Fostering Open Communication: Encourages open dialogue among team members to address issues and improve collaboration, with communication being key to effective teamwork.
  • Creating a Conducive Environment: Advocates for designing workspaces that minimize distractions and promote focus, allowing for both individual work and team collaboration.
  • Investing in Team Dynamics: Prioritizes team-building activities and fostering relationships among team members, emphasizing the importance of team chemistry for productivity.

About the Author

Tom DeMarco is an accomplished author with fifteen published books spanning various genres. His works include five novels, a short story collection, and several business-oriented books. DeMarco's most recent publication is "The One-Way Time Traveler," a love story described as "seemingly jinxed." Prior to this, he wrote "Dark Harbor House." DeMarco is perhaps best known for his business books, including the widely acclaimed "Slack," "Peopleware," and "The Deadline." These works have established him as a respected voice in project management and organizational behavior, particularly within the software development industry.

Download PDF

To save this Peopleware summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.39 MB     Pages: 22

Download EPUB

To read this Peopleware summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.34 MB     Pages: 29
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...