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.[1]
Overview edit
The concept of peopleware in the software community covers a variety of aspects:[2]
- Development of productive persons
- Organizational culture
- Organizational learning
- Development of productive teams, and
- Modeling of human competencies.
History edit
The neologism, first used by Peter G. Neumann in 1977[3] and independently coined by Meilir Page-Jones in 1980,[4] was popularized in the 1987 book Peopleware: Productive Projects and Teams by Tom DeMarco and Timothy Lister.[5]
The term Peopleware also became the title and subject matter of a long-running series of columns by Larry Constantine in Software Development magazine, later compiled in book form.[6]
References edit
- ^ Larry Constantine Constantine on Peopleware Prentice Hall, 1995, p. xxi. (ISBN 0-13-331976-8)
- ^ Silvia T. Acuna (2005). A Software Process Model Handbook for Incorporating People's Capabilities. pp. 9–11.
- ^ Peter G. Neumann "Peopleware in Systems." in Peopleware in Systems. Cleveland, OH: Assoc. for Systems management, 1977, pp 15–18. (ISBN 0-934356-13-0)
- ^ Page-Jones, M. Practical Guide to Structured Systems Design. New York: Yourdon Press. (ISBN 0-13-690769-5)
- ^ Tom DeMarco and Timothy Lister. Peopleware: Productive Projects and Teams. New York: Dorset House, 1987. (ISBN 0-932633-43-9)
- ^ Larry Constantine The Peopleware Papers Prentice Hall, 2001. (ISBN 0-13-060123-3)