In globally distributed projects, virtual teams are often partially dispersed. One common setup occurs when several members from one company work with a large outsourcing vendor based in another country. Further, the introduction of the popular BizDevOps concept has increased the necessity to cooperate across departments and reduce the age-old disconnection between the business strategy and technical development. Establishing a good collaboration in partially distributed BizDevOps teams requires extensive collaboration and communication techniques. Nowadays, a common approach is to rely on collaboration through pull requests and frequent communication on Slack. To investigate barriers for pull requests in distributed teams, we examined an organization located in Scandinavia where cross-functional BizDevOps teams collaborated with off-site team members in India. Data were collected by conducting 14 interviews, observing 23 entire days with the team, and observing 37 meetings. We found that the pull-request approach worked very well locally but not across sites. We found barriers such as domain complexity, different agile processes (timeboxed vs. flow-based development), and employee turnover. Using an intellectual capital lens on our findings, we discuss barriers and positive and negative effects on the success of the pull-request approach.
翻译:在全球分布的项目中,虚拟团队往往被部分分散。当一家公司的若干成员与设在另一个国家的大型外包供应商合作时,就出现了一种共同的设置。此外,流行的BizDevOps概念的引入增加了各部门之间合作的必要性,并减少了商业战略与技术发展之间长期脱节的现象。在部分分布的BizDevOps团队中建立良好的协作需要广泛的合作和通信技术。现在,一个共同的方法是通过拉动请求和经常在Slack上进行沟通来依靠协作。为了调查分布在分布在另一国家的一家公司中拉动请求的障碍,我们检查了位于斯堪的纳维亚的一个组织,在那里的跨功能BizDevOps团队与印度的场外团队成员合作。通过14次访谈收集了数据,与团队观察了23天,并观察了37次会议。我们发现拉动请求方法在当地非常有效,但并非在所有地点运作。我们发现一些障碍,如域复杂、不同快速程序(时间框框对流动开发)和雇员更替。我们用知识资本透视视我们的调查结果,我们讨论了障碍和对拉动请求成功产生的积极和消极影响。