Boundary objects in Agile practices

Rebekka Wohlrab, Patrizio Pelliccione, Eric Knauss, Mats Larsson
2018 Proceedings of the 2018 International Conference on Software and System Process - ICSSP '18  
Automotive companies increasingly include proven agile methods in their plan-driven system development. The adoption of agile methods impacts not only the way individuals collaborate, but also the management of artifacts like requirements, test cases, safety documentation, and models. While practitioners aim to reduce unnecessary documentation, there is a lack of guidance for automotive companies with respect to what artifacts are needed and how to manage them. To close this knowledge gap and
more » ... eate practical guidelines, we conducted a design-science study together with 53 practitioners from six automotive companies. Using interviews, surveys, and focus groups, we analyzed categories of artifacts and practical challenges to create applicable guidelines to collaboratively manage artifacts in agile automotive contexts. Our findings indicate that different practices are required to manage artifacts that are shared among different teams within the company (boundary objects) and those that are relevant within a specific team (locally relevant artifacts). CCS CONCEPTS • Software and its engineering → Software development methods; Agile software development; Documentation; Collaboration in software development; KEYWORDS Agile systems engineering, empirical software engineering, largescale agile, documentation ACM Reference Format: Rebekka Wohlrab, Patrizio Pelliccione, Eric Knauss, and Mats Larsson. 2018.
doi:10.1145/3202710.3203155 dblp:conf/ispw/WohlrabPKL18 fatcat:qga26gf7l5fovnxy3l4iz6dvka