Search results
Results from the WOW.Com Content Network
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.
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 work was the subject of a retrospective special session of IEEE International Conference on Software 2007 commemorating 20th anniversary of its publication. [3] Peopleware's prescriptions had mixed reception, with environmental factors like relative quiet and interrupt protection generally accepted, but other suggestions, particularly the ...
The famous book Peopleware: Productive Projects and Teams by de Marco and Lister [14] brought the importance of people-related factors to the attention of a broader audience. They collected in many software projects experiences with good and bad management practice that have an influence on the productivity of the team.
3 ISBN. 1 comment. 4 Discussion leading to page move. 11 comments. Toggle the table of contents. Talk: Peopleware: Productive Projects and Teams. Add languages.
A phone call and an instant messaging discussion are examples. Conferencing (or collaboration level, as it is called in academic papers) refers to interactive work toward a shared goal. Brainstorming and voting are examples. Coordination refers to complex interdependent work toward a shared goal. A good metaphor is to think about a sports team ...
Philip Donald Estridge (June 23, 1937 – August 2, 1985), known as Don Estridge, was an American computer engineer who led development of the original IBM Personal Computer (PC), and thus is known as the "father of the IBM PC".
One of the core ideas of evidence-based scheduling, that adds to the normal estimation practices, is the idea of including all time spent, regardless of relevance.. Most people, when estimating, measure the time they actually spend on a project – classic Time Accounting categories such as cited in McConnell's Software Project Survival Guide [1] do not allow for accounting for non-project ...