论文标题
敏捷团队中的组织结构模式：一项工业实证研究
Organisational Structure Patterns in Agile Teams: An Industrial Empirical Study
论文作者
论文摘要
在任何大规模的软件工程努力中，将组织的成员纳入连贯的团体或社区是一个重要的问题，尤其是在敏捷软件开发团队中，依赖自我组织和组织灵活性的敏捷软件开发团队。为了解决这个问题，许多研究人员和从业人员提倡一种镜像系统结构和组织结构的策略，以简化协作工作的沟通和协调。但是，在敏捷软件社区实践中发现的组织模式是什么？这些模式的有效性有多？我们使用工业中的混合方法研究来解决这些研究问题，即对敏捷团队的访谈调查，焦点组和Delphi研究。在我们对30个敏捷软件组织的研究中，我们发现，在我们数据集遍布的7种组织结构模式中，单个组织模式发生在37％以上。这种模式：（a）反映了年轻社区（1-12个月大）； （b）在既定的人（13个月以上）中消失； （c）反映了报告的最高数量的建筑问题。最后，我们观察到拟议的组织措施和建筑问题之间存在负相关性。这些见解可能有助于建筑师不仅设计其架构，还可以设计其社区，以最好地支持他们的共同发展。
Forming members of an organization into coherent groups or communities is an important issue in any large-scale software engineering endeavour, especially so in agile software development teams which rely heavily on self-organisation and organisational flexibility. To address this problem, many researchers and practitioners have advocated a strategy of mirroring system structure and organisational structure, to simplify communication and coordination of collaborative work. But what are the patterns of organisation found in practice in agile software communities and how effective are those patterns? We address these research questions using mixed-methods research in industry, that is, interview surveys, focus-groups, and delphi studies of agile teams. In our study of 30 agile software organisations we found that, out of 7 organisational structure patterns that recur across our dataset, a single organisational pattern occurs over 37% of the time. This pattern: (a) reflects young communities (1-12 months old); (b) disappears in established ones (13+ months); (c) reflects the highest number of architecture issues reported. Finally, we observe a negative correlation between a proposed organisational measure and architecture issues. These insights may serve to aid architects in designing not only their architectures but also their communities to best support their co-evolution.
