Content deleted Content added
Peter Flass (talk | contribs) link harlan mills |
Peter Flass (talk | contribs) description of team. |
||
Line 1:
A '''chief programmer team''' is a [[programming team]] organized in a star around a "chief" role, granted to the [[software]] [[engineer]] who understands the system's intentions the best. Other team members get supporting roles
The concept is similar to that of a [[surgical team]] in which a [[surgeon]] who performs the [[Surgery|operation]] is supported by medical staff such as an [[anaesthetist]] and [[nurse]]s.<ref name=DB/>
==Team structure==
Various roles have been defined for team members, the following are taken from Brooks.<ref name=Brooks />
* Chief Programmer: the most senior member of the team, has overall technical responsibility for the project.
* Backup Programmer: assists the chief programmer and shares his duties.
* Administrator: handles "money, people, space, and machines."
* Editor: has responsibility for project documentation.
* Secretaries: the Administrator and Editor each have a secretary.
* Program Clerk: responsible for all project technical records.
* Toolsmith: builds and maintains tools used by developers.
* Tester: develops tests for verification.
* Language Lawyer: has in-depth expertise in the language(s) used to develop the project.
* Programmers: work under the direction of the Chief Programmer and the Backup Programmer.
==References==
{{reflist}}
==External links==
* {{cite web|title=Chief Programmer Team|url=http://c2.com/cgi/wiki?ChiefProgrammerTeam|website=C2,Com|accessdate=August 25, 2016}}
[[Category:Software project management]]
|