Peopleware: Productive Projects and Teams

Last updated

Peopleware: Productive Projects and Teams is a 1987 book on the social side of software development, specifically managing project teams. It was written by software consultants Tom DeMarco and Tim Lister, from their experience in the world of software development. This book was revised in 1999 and 2016. [1]

Contents

Overview

Peopleware is a popular book about software organization management. The first chapter of the book claims, "The major problems of our work are not so much technological as sociological in nature". The book approaches sociological or 'political' problems such as group chemistry and team jelling, "flow time" and quiet in the work environment, and the high cost of turnover. Other topics include the conflicts between individual work perspective and corporate ideology, corporate entropy, "teamicide" and workspace theory.

The authors presented most subjects as principles backed up by some concrete story or other information. As an example, the chapter "Spaghetti Dinner" presents a fictional example of a manager inviting a new team over for dinner, then having them buy and prepare the meal as a group, in order to produce a first team success. Other chapters use real-life stories or cite various studies to illustrate the principles being presented.

Editions

The second edition kept the original content with only a few changes or corrections. The bulk of the new content was eight chapters in a new section at the end. The new section's chapters revisited some of the concepts of the original chapters with changes and added new ones. The eBook PDF version published by DorsetHouse was not searchable as each page appeared to be an image. The Kindle version is searchable.

The new content of the third edition is spread out through the book. There are six new chapters, but the original content has also been updated.

See also

Related Research Articles

<i>The Mythical Man-Month</i> 1975 software engineering book by Fred Brooks

The Mythical Man-Month: Essays on Software Engineering is a book on software engineering and project management by Fred Brooks first published in 1975, with subsequent editions in 1982 and 1995. Its central theme is that adding manpower to a software project that is behind schedule delays it even longer. This idea is known as Brooks's law, and is presented along with the second-system effect and advocacy of prototyping.

<span class="mw-page-title-main">George Ritzer</span> American sociologist (born 1940)

George Ritzer is an American sociologist, professor, and author who has mainly studied globalization, metatheory, patterns of consumption, and modern/postmodern social theory. His concept of McDonaldization draws upon Max Weber's idea of rationalization through the lens of the fast food industry. He coined the term after writing The McDonaldization of Society (1993), which is among the best selling monographs in the history of American sociology.

Software design is the process by which an agent creates a specification of a software artifact intended to accomplish goals, using a set of primitive components and subject to constraints. The term is sometimes used broadly to refer to "all the activity involved in conceptualizing, framing, implementing, commissioning, and ultimately modifying" the software, or more specifically "the activity following requirements specification and before programming, as ... [in] a stylized software engineering process."

Brooks' law is an observation about software project management according to which adding manpower to a software project that is behind schedule delays it even longer. It was coined by Fred Brooks in his 1975 book The Mythical Man-Month. According to Brooks, under certain conditions, an incremental person when added to a project makes it take more, not less time.

<span class="mw-page-title-main">Open-source software</span> Software licensed to ensure source code usage rights

Open-source software (OSS) is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose. Open-source software may be developed in a collaborative, public manner. Open-source software is a prominent example of open collaboration, meaning any capable user is able to participate online in development, making the number of possible contributors indefinite. The ability to examine the code facilitates public trust in the software.

<span class="mw-page-title-main">PRINCE2</span> Project management method

PRINCE2 is a structured project management method and practitioner certification programme. PRINCE2 emphasises dividing projects into manageable and controllable stages.

<span class="mw-page-title-main">Analysis paralysis</span> Overthinking causes

Analysis paralysis describes an individual or group process where overanalyzing or overthinking a situation can cause forward motion or decision-making to become "paralyzed", meaning that no solution or course of action is decided upon within a natural time frame. A situation may be deemed too complicated and a decision is never made, or made much too late, due to anxiety that a potentially larger problem may arise. A person may desire a perfect solution, but may fear making a decision that could result in error, while on the way to a better solution. Equally, a person may hold that a superior solution is a short step away, and stall in its endless pursuit, with no concept of diminishing returns. On the opposite end of the time spectrum is the phrase extinct by instinct, which is making a fatal decision based on hasty judgment or a gut reaction.

Social computing is an area of computer science that is concerned with the intersection of social behavior and computational systems. It is based on creating or recreating social conventions and social contexts through the use of software and technology. Thus, blogs, email, instant messaging, social network services, wikis, social bookmarking and other instances of what is often called social software illustrate ideas from social computing.

Lean software development is a translation of lean manufacturing principles and practices to the software development domain. Adapted from the Toyota Production System, it is emerging with the support of a pro-lean subculture within the agile community. Lean offers a solid conceptual framework, values and principles, as well as good practices, derived from experience, that support agile organizations.

Tom DeMarco is an American software engineer, author, and consultant on software engineering topics. He was an early developer of structured analysis in the 1970s.

<span class="mw-page-title-main">Operations management</span> In business operations, controlling the process of production of goods

Operations management is an area of management concerned with designing and controlling the process of production and redesigning business operations in the production of goods or services. It involves the responsibility of ensuring that business operations are efficient in terms of using as few resources as needed and effective in meeting customer requirements.

Malicious compliance is the behavior of strictly following the orders of a superior despite knowing that compliance with the orders will have an unintended or negative result. It usually implies following an order in such a way that ignores or otherwise undermines the order's intent, but follows it to the letter. A form of passive-aggressive behavior, it is often associated with poor management-labor relationships, micromanagement, a generalized lack of confidence in leadership, and resistance to changes perceived as pointless, duplicative, dangerous, or otherwise undesirable. It is common in organizations with top-down management structures lacking morale, leadership or mutual trust. In U.S. law, this practice has been theorized as a form of uncivil obedience, and it is a technique which is also used in art practice.

<i>Decline and Fall of the American Programmer</i> Book by Edward Yourdon

Decline and Fall of the American Programmer is a book written by Edward Yourdon in 1992. It was addressed to American programmers and software organizations of the 1990s, warning that they were about to be driven out of business by programmers in other countries who could produce software more cheaply and with higher quality. Yourdon claimed that American software organizations could only retain their edge by using technologies such as ones he described in the book. Yourdon gave examples of how non-American—specifically Indian and Japanese—companies were making use of these technologies to produce high-quality software.

Agile testing is a software testing practice that follows the principles of agile software development. Agile testing involves all members of a cross-functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by the customer at frequent intervals, working at a sustainable pace. Specification by example is used to capture examples of desired and undesired behavior and guide coding.

Programming productivity describes the degree of the ability of individual programmers or development teams to build and evolve software systems. Productivity traditionally refers to the ratio between the quantity of software produced and the cost spent for it. Here the delicacy lies in finding a reasonable way to define software quantity.

Peopleware is a term used to refer to one of the three core aspects of computer technology, the other two being hardware and software. Peopleware can refer to anything that has to do with the role of people in the development or use of computer software and hardware systems, including such issues as developer productivity, teamwork, group dynamics, the psychology of programming, project management, organizational factors, human interface design, and human–machine interaction.

<span class="mw-page-title-main">Extreme programming</span> Software development methodology

Extreme programming (XP) is a software development methodology intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent releases in short development cycles, intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted.

<span class="mw-page-title-main">Tim Lister</span>

Tim Lister is an American software engineer and author with specialty in design, software risk management, and human aspects of technological work. He is a Principal of The Atlantic Systems Guild Inc. and a fellow of the Cutter Consortium.

Open source is source code that is made freely available for possible modification and redistribution. Products include permission to use the source code, design documents, or content of the product. The open-source model is a decentralized software development model that encourages open collaboration. A main principle of open-source software development is peer production, with products such as source code, blueprints, and documentation freely available to the public. The open-source movement in software began as a response to the limitations of proprietary code. The model is used for projects such as in open-source appropriate technology, and open-source drug discovery.

Hands-on management is a particular style of management where the manager or person in charge is particularly active in day-to-day business and leadership. It is not to be confused with micromanagement and is seen as the opposite of Laissez-faire management style.

References

  1. DeMarco, Tom; Lister, Tim (2016-04-22). Peopleware: Productive Projects and Teams (3rd ed.). Upper Saddle River, NJ: Addison Wesley. ISBN   978-0-321-93411-6.