[Context & motivation] Driven by the need for faster time-to-market and reduced development lead-time, large-scale systems engineering companies are adopting agile methods in their organizations. This agile transformation is challenging and it is common that adoption starts bottom-up with agile software teams within the context of traditional company structures. [Question/Problem] This creates the challenge of agile teams working within a document-centric and plan-driven (or waterfall) environment. While it may be desirable to take the best of both worlds, it is not clear how that can be achieved especially with respect to managing requirements in large-scale systems. [Principal ideas/Results] This paper presents an exploratory case study at an automotive company, focusing on two departments of a large-scale systems company that is in the process of company-wide agile adoption. [Contribution] We present challenges related to requirements engineering that agile teams face while working within a larger plan-driven context and propose potential strategies to mitigate the challenges. Challenges relate to, e.g., development teams not being aware of the high-level requirement and dealing with flexibility of writing user stories. We found that strategies for overcoming most of these challenges are still lacking and thus call for more research.
翻译:由于需要更快的时到市场和减少发展周转时间,大型系统工程公司在其组织中正在采用灵活的方法。这种敏捷的转变具有挑战性,而且通常在传统的公司结构中,采用自下而上,由灵活软件团队在传统的公司结构中开始采用。[问题/问题]这带来了灵活团队在以文件为中心、计划驱动(或瀑布)的环境中工作的挑战。虽然最好在两个世界中采取最佳行动,但尚不清楚如何做到这一点,特别是在管理大型系统的要求方面。 [主要想法/Results]本文件介绍了一家汽车公司的一项探索性案例研究,重点是一家大型系统公司的两个部门,而这两个部门正处于全公司采用灵活程序之中。[原因]我们提出了与灵活团队在更大计划驱动的环境中工作所面临的工程要求有关的挑战,并提出了减轻挑战的潜在战略。挑战涉及,例如,发展团队不了解高层次的要求,处理用户故事的灵活性问题。因此,我们发现,这些研究战略往往缺乏。