Chief programmer team: Difference between revisions

Content deleted Content added
m Added basic information.
No edit summary
Tags: Mobile edit Mobile web edit
 
(9 intermediate revisions by 7 users not shown)
Line 1:
A '''chief programmer team''' iswas the concept of a [[programming team]] organized in a star around a "chief" role, granted to the [[software]] [[engineer]] who understandsunderstood the system's intentions the best. Other team members getgot supporting roles.<ref name=DB>{{citation |url=https://books.google.com/books?id=oMN1SR7KQd0C&pg=PA352 |title=Software engineering for students: a programming approach |author=Doug Bell|isbn=9780321261274 |year=2005 }}</ref>
 
The concept iswas 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, and similarly, the chief programmer is surrounded with the team of minor programmers, with the respectively differencing in the salary levels..<ref>{{Cite web|url=http://resumescentre.com/salary-report/computer-programmer|title=Computer Programmer Salary Report at ResumesCentre.com|website=resumescentre.com|language=en|access-date=2017-04-26}}</ref><ref name=DB/>
[[Fred Brooks]] describes the concept in detail in ''[[The Mythical Man-Month]]'',<ref name=Brooks>{{cite book|last1=Brooks, Jr.|first1=Frederick P.|title=The Mythical Man-Month|date=1975|publisher=Addison-Wesley Publishing Company|pages=32–-35|accessdate=August 25, 201632––35}}</ref> as proposed by [[Harlan Mills]]<ref name=HM>{{citation|title=Chief programmer teams, principles, and procedures|author=Mills, H.|work=IBM Federal Systems Division Report FSC71-5108|place=Gaithersburg, Md.|year=1971}}</ref> in 1971.
 
==Team structure==
The team consists of ten people. 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 supports tools used by developers.
* Tester: develops tests for verification.
* Language Lawyer: has in-depth expertise in the language(s) used to develop the project.
 
Line 22 ⟶ 16:
 
==External links==
* {{cite journal|last1=Sjoquist|first1=Robert J.|title=Experiences in the Development of a Large Scale Linear Programming System|journal=Computers and mathematicalMathematical programmingProgramming: proceedingsProceedings of the Bicentennial Conference on Mathematical Programming heldHeld at the National Bureau of Standards, Gaithersburg, Maryland, November 29-December 1, 1976|date=1976|url=https://books.google.com/books?id=wf8GmbR8WHsC&pg=PA358|accessdateaccess-date=August 25, 2016}}
* {{cite web|title=Chief Programmer Team|url=http://c2.com/cgi/wiki?ChiefProgrammerTeam|website=C2,Com|accessdateaccess-date=August 25, 2016}}
 
[[Category:Software project management]]