Understanding the Building Blocks of Accountability in Software Engineering

In the social and organizational sciences, accountability has been linked to the efficient operation of organizations. However, it has received limited attention in software engineering (SE) research, in spite of its central role in the most popular software development methods (i.e., Scrum). In this article, we seek to explore the mechanisms of accountability in SE environments and investigate the factors that foster software engineers' individual accountability within their teams through an interview study with 12 people. Our findings recognize two primary forms of accountability shaping software engineers individual senses of accountability: \emph{institutionalized} and \emph{grassroots}. While the former is directed by formal processes and mechanisms, like performance reviews, grassroots accountability arises organically within teams, driven by factors such as peers' expectations and intrinsic motivation. This organic form cultivates a shared sense of collective responsibility, emanating from shared team standards and individual engineers' inner commitment to their personal, professional values, and self-set standards. While institutionalized accountability relies on traditional "carrot and stick" approaches, such as financial incentives or denial of promotions, grassroots accountability operates on reciprocity with peers and intrinsic motivations, like maintaining one's reputation in the team.在社会与组织科学领域，问责制（accountability）与组织的高效运转息息相关。然而，尽管其在当下最主流的软件开发方法（即Scrum）中居于核心地位，但该概念在软件工程（SE）研究中却鲜有受到关注。本文旨在探究软件工程场景下的问责机制，并通过针对12名受访者的访谈研究，剖析能够推动团队中软件工程师个体履职问责的各类影响因素。本研究发现，塑造软件工程师个体问责意识的问责形式主要分为两类：制度化问责（institutionalized）与草根式问责（grassroots）。前者由正式流程与机制主导，例如绩效考评；而后者则在团队内部自发形成，其驱动因素包括同伴期望与内在动机。这种自发形成的问责模式依托共同的团队准则，以及软件工程师个体对个人与职业价值观的内在恪守、自我设定的行为标准，从而培育出共享的集体责任意识。制度化问责依托传统的"胡萝卜加大棒"手段，例如物质激励或晋升资格否决；而草根式问责则基于同伴间的互惠关系与内在动机，例如维护自身在团队中的声誉。