Tim Lister (born 1949) 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. [1] . He is (with co-authors) a two-time winner of the Jolt Award for best published sofware development book of the year.
Lister's work with collaborator Tom DeMarco on non-technical factors affecting team and individual performance eventually resulted in their book, Peopleware: Productive Projects and Teams [2] originally published in 1987. 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 use of enclosed space around a team in preference to open plan seating, largely ignored. [4] The authors' Coding War Games study [5] which supplies evidence for the book's conclusions about the effects of workplace factors on performance is still being cited in articles about workplace design [6] [7] more than 25 years after its initial publication. The term "Peopleware" is in general use [8] [9] [10] among software practitioners to describe the extent to which an organization does or not conform to the book's proposed ideals.
Lister is one of the originators of work [11] that characterizes organizational culture using an approach first advocated (for architecture) by Christopher Alexander et al. [12] In this scheme, organizations are classified by the extent to which they fit or do not fit one or more of 86 common patterns. The 86 proposed patterns serve as an organizational "pattern language" [12] much as Alexander's 250 patterns make up an architectural pattern language.
Lister is author or co-author of the following works:
A programmer, computer programmer or coder is an author of computer source code – someone with skill in computer programming.
Pair programming is a software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it is typed in. The two programmers switch roles frequently.
Software engineering is an engineering approach to software development. A practitioner, a software engineer, applies the engineering design process to develop software.
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.
Brooks's law is an observation about software project management that "Adding manpower to a late software project makes it later." 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.
An anti-pattern in software engineering, project management, and business processes is a common response to a recurring problem that is usually ineffective and risks being highly counterproductive. The term, coined in 1995 by computer programmer Andrew Koenig, was inspired by the book Design Patterns and first published in his article in the Journal of Object-Oriented Programming. A further paper in 1996 presented by Michael Ackroyd at the Object World West Conference also documented anti-patterns.
In computer programming, a code smell is any characteristic in the source code of a program that possibly indicates a deeper problem. Determining what is and is not a code smell is subjective, and varies by language, developer, and development methodology.
Software development is the process used to create software. Programming and maintaining the source code is the central step of this process, but it also includes conceiving the project, evaluating its feasibility, analyzing the business requirements, software design, testing, to release. Software engineering, in addition to development, also includes project management, employee management, and other overhead functions. Software development may be sequential, in which each step is complete before the next begins, but iterative development methods where multiple steps can be executed at once and earlier steps can be revisited have also been devised to improve flexibility, efficiency, and scheduling.
The following outline is provided as an overview of and topical guide to software engineering:
In computer programming, a software framework is an abstraction in which software, providing generic functionality, can be selectively changed by additional user-written code, thus providing application-specific software. It provides a standard way to build and deploy applications and is a universal, reusable software environment that provides particular functionality as part of a larger software platform to facilitate the development of software applications, products and solutions.
Founder's syndrome is the difficulty faced by organizations, and in particular young companies such as start-ups, where one or more founders maintain disproportionate power and influence following the effective initial establishment of the organization, leading to a wide range of problems. The syndrome occurs in both non-profit and for-profit organizations or companies.
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.
Structured analysis and design technique (SADT) is a systems engineering and software engineering methodology for describing systems as a hierarchy of functions. SADT is a structured analysis modelling language, which uses two types of diagrams: activity models and data models. It was developed in the late 1960s by Douglas T. Ross, and was formalized and published as IDEF0 in 1981.
James A. Highsmith III is an American software engineer and author of books in the field of software development methodology. He is the creator of Adaptive Software Development, described in his 1999 book "Adaptive Software Development", and winner of the 2000 Jolt Award, and the Stevens Award in 2005. Highsmith was one of the 17 original signatories of the Agile Manifesto, the founding document for agile software development.
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.
In software engineering, structured analysis (SA) and structured design (SD) are methods for analyzing business requirements and developing specifications for converting practices into computer programs, hardware configurations, and related manual procedures.
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.
The bus factor is a measurement of the risk resulting from information and capabilities not being shared among team members, derived from the phrase "in case they get hit by a bus". It is also known as the bus problem, truck factor, or bus/truck number.
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.
{{cite book}}: CS1 maint: multiple names: authors list (link)