Communication through Boundary Objects in Distributed Agile Teams
Communication through Boundary Objects in Distributed Agile Teams
复制标题
分布式敏捷团队中通过边界对象进行通信
DOI：
--
复制
发表时间：
2015
期刊：
影响因子：
--
通讯作者：
Johan Aberg
中科院分区：
文献类型：
--
作者：
Johan Blomkvist;J. Persson;Johan Aberg
以用户为中心的设计（UCD）专家和开发人员之间的个人交流对于传达敏捷开发中的用户需求和设计解决方案很重要。在分布式项目的机会有限的分布式项目中，设计文档是一个重要的代理。这项研究调查了边界对象在分布式敏捷团队中的感知有效性，以及它们在传达目标用户需求中的作用。与UCD专家的六次深入访谈表明，边界对象很少传达用户的潜在需求，而是专注于与正在开发的系统的互动。所用的边界对象也不可作为独立的可交付成果。它们需要被解释和详细说明。使边界对象完全全面地被视为太耗时，不值得付出努力。对于具有分布式团队的敏捷项目，这会造成手工和后续问题。
Personal communication between User-Centered Design (UCD) specialists and developers is important for communicating user needs and design solutions in agile development. In distributed projects where opportunities for personal communication are limited, the design documentation is an important surrogate. This study has investigated the perceived effectiveness of boundary objects in a distributed agile team, and their role in communicating target user needs. Six in-depth interviews with UCD specialists showed that the boundary objects rarely communicate underlying needs of the users but rather focus on interaction with the system that is being developed. The used boundary objects also do not work as stand-alone deliverables; they need to be explained and elaborated. Making the boundary objects comprehensive enough to be stand-alone is seen as too time consuming and not worth the effort. For agile projects with distributed teams, this creates hand-over and follow-up problems.