The Surgical Team structure is led by one chief-person performing the most critical work himself while directing his team to assist with or overtake other important but less critical parts.
Books defines the surgical team as in the following summary:
The surgeon is the chief programmer of the whole team. He produces all the specifications, codes the entire system the team is responsible for, tests it, and drafts its supporting documentation.
The copilot is the surgeon’s right-hand man. His main purpose is to share in the thinking about design issues. The copilot represents the team in meetings with other teams. He knows the code intimately, and serves as insurance in case of disaster to the surgeon.
The toolsmith supports the surgeon and builds specialized utilities and tools as may be required by his surgeon. Each team has its dedicated toolsmith in addition to any central services provided by the rest of the project infrastructure.
The tester is responsible for maintaining test cases for testing the surgeon’s work as he writes it. He is both an adversary who devises test cases to measure against the formal specs and devises test data to be used in debugging.
The language lawyer, which can serve several surgeons, is a widely consulted specialist who delights in the mastery of the intricacies of the programming languages and the operating systems upon which the software must perform.
The administrator handles money, people, space, and machines. The surgeon is the ultimate boss, with the last word on all these issues, but the day to day management of the issues and interfacing with the administrative machinery of the project is the role of a professional administrator. One administrator may serve more than one team.
The editor edits and revises the documentation as drafted or dictated by the surgeon and oversees the mechanics of its production.
The program clerk, trained as a secretary, is responsible for maintaining all the machine-readable and human-readable technical records generated by the team. All the filing and indexing is the responsibility of the program clerk.
The secretaries handle the project correspondence and non-project files.
发布评论
评论（1）
您可能需要考虑“有争议的”外科团队结构，该结构首先由 Harlan Mills 提出，并且Fred Brooks 在神话人月。
外科团队结构由一名负责最关键工作的负责人领导他自己同时指导他的团队协助或超越其他重要但不太关键的部分。
书籍对手术团队的定义如下：
手术团队 http://img705。 imageshack.us/img705/1599/image022b.gif
外科医生是整个团队的首席程序员。他制定所有规范，对团队负责的整个系统进行编码，测试并起草其支持文档。
副驾驶是外科医生的得力助手。他的主要目的是分享对设计问题的思考。副驾驶代表团队参加与其他团队的会议。他对密码了如指掌，在外科医生发生灾难时充当保险。
工具匠为外科医生提供支持，并根据外科医生的需要建造专门的实用程序和工具。除了项目基础设施的其余部分提供的任何中央服务之外，每个团队都有其专门的工具匠。
测试人员负责维护测试用例，以测试外科医生编写的工作。他既是设计测试用例来衡量正式规范的对手，也是设计用于调试的测试数据的对手。
语言律师可以为多名外科医生提供服务，是一位广受咨询的专家，他乐于掌握复杂的编程语言和软件必须运行的操作系统。
管理员处理资金、人员、空间和机器。外科医生是最终的老板，对所有这些问题拥有最终决定权，但问题的日常管理以及与项目管理机制的交互是专业管理员的角色。一名管理员可以为多个团队服务。
编辑按照外科医生起草或指示的方式编辑和修订文档，并监督其制作机制。
程序文员接受过秘书培训，负责维护团队生成的所有机器可读和人类可读的技术记录。所有归档和索引均由程序文员负责。
秘书处理项目信件和非项目文件。
资料来源和进一步阅读（赞成和反对）：
You may want to consider the "controversial" Surgical Team structure, first proposed by Harlan Mills, and described in detail by Fred Brooks in The Mythical Man Month.
The Surgical Team structure is led by one chief-person performing the most critical work himself while directing his team to assist with or overtake other important but less critical parts.
Books defines the surgical team as in the following summary:
The Surgical Team http://img705.imageshack.us/img705/1599/image022b.gif
The surgeon is the chief programmer of the whole team. He produces all the specifications, codes the entire system the team is responsible for, tests it, and drafts its supporting documentation.
The copilot is the surgeon’s right-hand man. His main purpose is to share in the thinking about design issues. The copilot represents the team in meetings with other teams. He knows the code intimately, and serves as insurance in case of disaster to the surgeon.
The toolsmith supports the surgeon and builds specialized utilities and tools as may be required by his surgeon. Each team has its dedicated toolsmith in addition to any central services provided by the rest of the project infrastructure.
The tester is responsible for maintaining test cases for testing the surgeon’s work as he writes it. He is both an adversary who devises test cases to measure against the formal specs and devises test data to be used in debugging.
The language lawyer, which can serve several surgeons, is a widely consulted specialist who delights in the mastery of the intricacies of the programming languages and the operating systems upon which the software must perform.
The administrator handles money, people, space, and machines. The surgeon is the ultimate boss, with the last word on all these issues, but the day to day management of the issues and interfacing with the administrative machinery of the project is the role of a professional administrator. One administrator may serve more than one team.
The editor edits and revises the documentation as drafted or dictated by the surgeon and oversees the mechanics of its production.
The program clerk, trained as a secretary, is responsible for maintaining all the machine-readable and human-readable technical records generated by the team. All the filing and indexing is the responsibility of the program clerk.
The secretaries handle the project correspondence and non-project files.
Sources and Further Reading (Pro and Against):