This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "Programming team" – news · newspapers · books · scholar · JSTOR (March 2019) (Learn how and when to remove this template message) This article needs to be updated. The reason given is: Sources are dated for this topic; other teams exist and should be explored (with references). Please help update this article to reflect recent events or newly available information. (March 2019) (Learn how and when to remove this template message)

A programming team is a team of people who develop or maintain computer software.[1] They may be organised in numerous ways, but the egoless programming team and chief programmer team have been common structures.[2]

Description

A programming team comprises people who develop or maintain computer software.[3]

Programming team structures

Programming teams may be organised in numerous ways, but the egoless programming team and chief programmer team are two common structures typically used.[2] The main determinants when choosing the programming team structure typically include: difficulty, size, duration, modularity, reliability, time, and sociability.[2]

Egoless programming

Main article: Egoless programming

According to Marilyn Mantei, individuals that are a part of a decentralized programming team report higher job satisfaction.[2] But an egoless programming team contains groups of ten or fewer programmers. Code is exchanged and goals are set amongst the group members. Leadership is rotated within the group according to the needs and abilities required during a specific time. The lack of structure in the egoless team can result in a weakness of efficiency, effectiveness, and error detection for large-scale projects. Egoless programming teams work best for tasks that are very complex.

Chief programmer team

Main article: Chief programmer team

A chief programmer team will usually contain three-person teams consisting of a chief programmer, senior level programmer, and a program librarian. Additional programmers and analysts are added to the team when necessary. The weaknesses of this structure include a lack of communication across team members, task cooperation, and complex task completion. The chief programmer team works best for tasks that are simpler and straightforward since the flow of information in the team is limited. Individuals that work in this team structure typically report lower work morale.[2]

Shared workstation teams

Pair programming

Main article: Pair programming

A development technique where two programmers work together at one workstation.

Mob programming

Main article: Mob programming

A software development approach where the whole team works on the same thing, at the same time, in the same space, and at the same computer.

Programming Models

Programming models allow software development teams to develop, deploy, and test projects using these different methodologies.

Waterfall Model

Main article: Waterfall model

The waterfall model, noted as the more traditional[4] approach, is a linear model of production. The sequence of events of this methodology follows as:

  1. Gather and document requirements
  2. Design
  3. Code and unit test
  4. Perform system testing
  5. Perform user acceptance testing (UAT)
  6. Fix any issues
  7. Deliver the finished product

Each stage is distinct during the software development process, and each stage generally finishes before the next one can begin.

Programming teams using this model are able to design the project early on in the development process allowing teams to focus on coding and testing during the bulk of the work instead of constantly reiterating design. This also allows teams to design completely and more carefully so that teams can have a complete understanding of all software deliverables.

Agile Model

Main article: Agile software development

The Agile development model is a more team-based approach to development[4] than the previous waterfall model. Teams work in rapid delivery/deployment which splits work into phases called "sprints". Sprints are usually defined as two weeks of planned software deliverables given to each team/team member.

After each sprint, work is reprioritized and the information learned from the previous sprint is used for future sprint planning. As the sprint work is complete, it can be reviewed and evaluated by the programming team and sent back for another iteration (i.e. next sprint) or closed if completed.

The general principles[5] of the Agile Manifesto[6] are as follows:

See also

References

  1. ^ Jack Belzer, Albert George Holzman, Allen Kent (October 1, 1979), Encyclopedia of computer science and technology, vol. 13, ISBN 9780824722630((citation)): CS1 maint: multiple names: authors list (link)
  2. ^ a b c d e Marilyn Mantei (March 1981). "The Effect of Programming Team Structures on Programming Tasks" (PDF). Communications of the ACM. Vol. 24, no. 3. p. 106–113. Retrieved 2019-03-26.
  3. ^ Jack Belzer, Albert George Holzman, Allen Kent (October 1979), Encyclopedia of computer science and technology, vol. 13, ISBN 9780824722630((citation)): CS1 maint: multiple names: authors list (link)
  4. ^ a b Mary Lotz (July 5, 2018), Waterfall vs. Agile: Which is the Right Development Methodology for Your Project?
  5. ^ Linchpin SEO Team (March 26, 2019), A Beginners Guide To The Agile Method & Scrums
  6. ^ "Principles behind the Agile Manifesto". 2019-06-11.