Communication through Boundary Objects in Distributed Agile Teams

Blomkvist, Johan; Persson, Johan; Åberg, Johan

doi:10.1145/2702123.2702366

Cited by 25 publications

(37 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For instance, Pareto et al examined architectural descriptions as boundary objects in agile systems engineering and specified requirements for their creation . Another study focused on boundary objects in distributed agile user‐centered design, concluding that boundary objects are facilitators for communication in that domain. The production process was in the focus of another study, analyzing how engineers, assemblers, and technicians communicate across boundaries .…”

Section: Related Workmentioning

confidence: 99%

Boundary objects and their use in agile systems engineering

Wohlrab

Knauss

Larsson

2019

J Software Evolu Process

View full text Add to dashboard Cite

Summary Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders and makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design‐science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry.

show abstract

Section: Related Workmentioning

confidence: 99%

Boundary objects and their use in agile systems engineering

Wohlrab

Knauss

Larsson

2019

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Additionally, we could realize that authors use different nomenclature for artifacts that are used for the same purpose. For example, the term guideline [64] [65] was also used as style guide [49], and design specification [60]. To handle these different names, we grouped the artifacts according to their objectives.…”

Section: A Artifacts On Agile User-centered Designmentioning

confidence: 99%

Artifacts for Agile User-Centered Design: A Systematic Mapping

Garcia¹,

Silva²,

Silveira³

2017

Proceedings of the 50th Hawaii International Conference on System Sciences (2017)

View full text Add to dashboard Cite

Abstract-The integration of Agile and User-Centered Design methods is a fundamental condition to improve the quality of software products. However, one of the main problems faced to establish this integration on a day-to-day basis is how to improve communication among the invariably distinct involved teams. We believe that the artifacts involved in the development process could be used to support and increase teams' communication.To better understand this scenario, we performed a systematic mapping study on artifacts and their role in the communication between Agile and User-Centered Design fields. Through the analysis of 56 papers dealing with this specific topic, we present the artifacts used for communication in these approaches and software development events when they are used. The analyzed studies reinforced our beliefs about the importance of artifacts to improve teams' communication.

show abstract

“…Working with Scrum teams particularly in large corporations, Budwig et al [93] detail the practices of user experience teams. Blomkvist et al [113] analyse one-to-one communication among UCD specialists believed to be a major factor for identifying users needs and design solutions in agile development.…”

Section: Team Integrationmentioning

confidence: 99%

Integrating Usability into the Agile Development Process: A preliminary empirical study

Magües¹,

Castro²,

Acuña³

2017

CLEIej

View full text Add to dashboard Cite

Background: Interest in the integration of the agile software development process (ASDP) and user-centred design (UCD) has grown over the last decade. However, there are not many papers that study this issue holistically and uncover the current state of this integration. Aim: This study sets out to answer the following research question: What is the current state of integration between agile processes and usability? Method: We conduct a systematic mapping study (SMS). We analyze the articles and the results were cross checked by the authors, and any disagreements were discussed and resolved in meetings. Results: We retrieved a total of 161 Primary Studies. There are very few papers that study the literature holistically and report the current state of usability in the ASDP. Conclusions: We categorized according to four criteria: process, practice, team and technology integration. The largest group refers to process integration with a total of 76 Primary Studies.

show abstract

Communication through Boundary Objects in Distributed Agile Teams

Cited by 25 publications

References 25 publications

Boundary objects and their use in agile systems engineering

Boundary objects and their use in agile systems engineering

Artifacts for Agile User-Centered Design: A Systematic Mapping

Integrating Usability into the Agile Development Process: A preliminary empirical study

Contact Info

Product

Resources

About