论文标题
关于敏捷开发协作工具支持的案例研究
A Case Study on Tool Support for Collaboration in Agile Development
论文作者
论文摘要
我们报告了一家大型软件公司意大利遗址进行的纵向案例研究，以进一步了解如何改善开发和通信工具，以更好地支持敏捷实践和协作。在使用通信工具（即电子邮件，Skype和Slack）的方式观察到不一致之后，我们首先加强了Slack作为内部通信的中心枢纽的使用，同时设置了有关工具使用情况的明确规则。作为第二个主要更改，我们将Jira Scrum Board重新分配给两个单独的董事会，这是针对开发人员的详细董事会，以及用于管理人员的高级董事会，同时还引入了自动化规则以及与Slack的集成。第一个更改表明，开发人员团队使用和赞赏的宽松方式不同，质量保证团队最有利，并且通过开发工具（例如Jenkins）的自动通知阻碍了使用渠道的使用。第二次变更的发现表明，有85％的受访者报告了他们的工作流程有所改善。尽管由于报道案件的单一性质造成的局限性，但我们强调了公司反思如何正确建立其敏捷工作环境以改善沟通和促进协作的重要性。
We report on a longitudinal case study conducted at the Italian site of a large software company to further our understanding of how development and communication tools can be improved to better support agile practices and collaboration. After observing inconsistencies in the way communication tools (i.e., email, Skype, and Slack) were used, we first reinforced the use of Slack as the central hub for internal communication, while setting clear rules regarding tools usage. As a second main change, we refactored the Jira Scrum board into two separate boards, a detailed one for developers and a high-level one for managers, while also introducing automation rules and the integration with Slack. The first change revealed that the teams of developers used and appreciated Slack differently with the QA team being the most favorable and that the use of channels is hindered by automatic notifications from development tools (e.g., Jenkins). The findings from the second change show that 85\% of the interviewees reported perceived improvements in their workflow. Despite the limitations due to the single nature of the reported case, we highlight the importance for companies to reflect on how to properly set up their agile work environment to improve communication and facilitate collaboration.
