Building Bridges, Burning Bridges: The Use of Boundary Objects in Agile Distributed ISD Teams

Abstract

Boundary objects are physical and abstract artefacts which support team interactions across diverse knowledge domains. Despite their relevancy, research into the effectiveness of boundary objects in agile distributed ISD remains nascent. In this paper, we develop a framework to theorize their effectiveness in generating cohesion within distributed teams. Our indepth case study finds that their effectiveness is influenced by the nature of the boundary objects themselves but also by team members' willingness to address differences in contextual factors. We identify three contextual factors -structure, identity, and culture -that are critical to supporting team members crossing knowledge boundaries within distributed teams. Furthermore, findings suggest that while boundary objects can indeed foster team cohesion in agile distributed ISD, there are other less explored aspects to their role. For example, we find that boundary objects can be useful for enabling constructive team conflict.

An Empirical Investigation of Factors Causing Scope Creep in Agile Global Software Development Context: A Conceptual Model for Project Managers

“…For this purpose, we have reduced the number of research articles based on the selection criteria based on title, abstract, and introduction. Table 3 represents the selected articles using the tollgate approach [78], retrieved from the considered data repositories. 2) DATA EXTRACTION…”

The Rise and Fall of Collective Identity: Understanding Antecedents and Inhibitors of Social Identification in Distributed Teams

“…Vahtera, et al [29] study of virtual teams found that identification with an 'in-group' can create negative perceptions of a perceived 'outgroup' which in turn intergroup interactions and brokerage between team members. The lack of a shared history and context can also make individuals unsure of their roles in the team, role expectations, and power relations [9,10,11]. In these situations, social identification occurs and is reinforced through individuals constructing a situational definition [cf.…”

“…However, distributed teams are unlikely to have the shared context or shared history necessary to generate agreement early on due to their diverse professional, organisational, and disciplinary backgrounds [9,10,11]. This can create impediments during decision-making processes due to issues such as role ambiguity [12,13] and differences in interests [6,14].…”

“…This can create impediments during decision-making processes due to issues such as role ambiguity [12,13] and differences in interests [6,14]. For instance, IT professionals adept at following an agile methodology of systems development may prefer flat structures, whereas healthcare practitioners may value top-down structures where senior members are conferred with decision-making authority [15]. In addition, IT professionals may wish to pursue different agendas to healthcare practitioners: while IT professionals may be primarily interested in developing novel and innovative IT solutions, healthcare practitioners may be more technophobic due to concerns around patient outcomes and safety [15].…”

The Impact of Covid 19 on Agile Software Development: A Systematic Literature Review

“…For a consistent understanding of values and principles, the agile manifesto was published 20 years ago [4]. It is known that social aspects like collaboration and communication are of importance in agile software development [5,6]. The iterative approach and recurring practices such as daily stand-up or planning meetings are characteristics of agile methods [7].…”