Boundary object use in cross-cultural software development teams

Abstract

This article examines the evolving use of boundary objects in cross-cultural software teams. Our field study of a Jamaican-Indian team examines the use of software specifications and project management tools as boundary objects in facilitating sharing across knowledge boundaries. We examine how and why the role and use of boundary objects may facilitate collaboration across knowledge boundaries at one time and contribute to conflict at other times. We unpack the interacting elements that both facilitate and constrain knowledge sharing, and trigger conflicts at different stages of the software team development. Specifically, we found that the use of boundary objects at transitions involving definitional control and the subsequent redistribution of power/authority may inhibit knowledge sharing. The subsequent reifying of cultural boundaries along with negative stereotyping led to relational conflict, through a process we call culturizing, as cross-cultural differences emerged as problematic for team dynamics.

Developing a Relational View of the Organizing Role of Objects: A study of the innovation process in computer games

“…This work promotes a view of objects not as static and fixed, but as unfolding and dynamic, demonstrating 'plasticity' (Barrett & Oborn, 2010), and 'openness or closedness' in enabling different forms of coordination over time (Ewenstein & Whyte, 2009). They are also seen as changing their coordinative roles over time (Star, 2010), for example, from acting as epistemic objects to becoming boundary objects (McGivern & Dopson, 2010), depending on the way in which they are used (Levina & Vaast, 2005).…”

La adquisición de un equipo de alto desempeño como alternativa en la estrategia de crecimiento inorgánico. Acquisition of a High performing team as an alternative in the inorganic growth strategy

“…Una mala previsión o gestión de los aspectos culturales podría acentuar las diferencias entre grupos diversos en el sentido cultural y repercutir en conflictos y estereotipos negativos (Barrett y Oborn, 2010), generar dificultad de aprendizaje para los expatriados (Chen, Kirkman, Kim, Farh y Tangirala, 2010) y problemas para comunicarse y compartir sus experiencias (Yadong, 2001), lo que puede incidir en el desempeño esperado.…”

Focal Points for a More User-Centred Agile Development

“…To this end, we point to the concept of boundary objects, i.e. mediating artefacts that allow knowledge sharing and promote collaboration since their interpretive flexibility facilitates "an overlap of meaning while preserving sufficient ambiguity" for different groups to read their own meanings [2]. The briefs used in H-umus can be considered as boundary objects in this sense, as they gather mockups from designers, technical specs from developers, and business requirements from the customer, and they act as a common reference point for monitoring the evolution of the product.…”