一句话:通过档案、访谈与问卷实证分析工业界 fireteam 小团队实践的特征、活动、效益与问题。
论文针对软件开发中团队效率与项目管理开销问题,研究某全球ICT企业制度化推行的小团队实践“fireteam”,旨在应对友善、人才、技能和沟通等人与社会因素。作者采用档案分析、访谈和问卷相结合的混合方法,在工业环境中考察其特征与影响。研究将 fireteam 分为带扩展的普通敏捷团队、单一职能团队和全生命周期团队三类,归纳团队组建、维护、沟通与会议四项关键活动。结果表明,更少沟通与管理开销、更高敏捷性与并发性、个人能力提升是提高生产力的主要因素;管理/领导投入、对 fireteam 理解分歧及自组织团队是主要问题。尽管实践中可观察到收益,该做法并未完全达到企业预期,论文还讨论了改进考虑与建议。
Software development is a collective undertaking, and the team’s efficiency is critical in development. In order to reduce project management overheads and improve productivity, a global information and communication technology enterprise institutionalizes an organization wide small-team practice, called fireteams, to tackle the problems arising from human and social aspects, such as amicability, talent, skill, and communications. This paper reports a mixed-method research, which combines archive analysis, interviews and survey, to empirically investigate the characteristics and impacts of fireteam in this industrial setting. We identify three categories of fireteam in terms of its demonstrated characteristics: ordinary agile team with extensions, single-function team, and entire life-cycle team; elaborate four key activities of fireteam, i.e. team formation, maintenance, communication, and meeting. Less communication and management overheads, higher agility & concurrency, and improved personal ability are the three important contributors that increase the productivity of fireteams. Whereas management & leadership effort, divergent understanding of fireteam, and self-organized team are discovered as the three major problems associated with fireteams. Although the benefits of fireteam can be observed from its adoption, this practice does not achieve the enterprise’s anticipations very well. Some considerations and recommendations are also discussed to improve this small-team practice.
DOI 原文 ·
@inproceedings{paperbot5829,
title = {Fireteam: a small-team development practice in industry},
author = {He Zhang and Huang Huang and Dong Shao and Xin Huang},
booktitle = {FSE},
year = {2020},
doi = {10.1145/3368089.3417068}
}