Knowledge Sharing in Agile Software Teams

Abstract

Abstract. Traditionally, software development teams follow Tayloristic approaches favoring division of labor and, hence, the use of role-based teams. Role-based teams require the transfer of knowledge from one stage of the development process to the next. As multiple stages are involved, the problem of miscommunication due to indirect and long communication path is amplified. Agile development teams address this problem by using cross-functional teams that encourages direct communication and reduces the likelihood of miscommunication. Agile approaches usually require team members to be co-located and only facilitate intra-team learning. To overcome the restriction in colocation and support organizational inter-team learning while supporting the social context critical to the sharing of tacit knowledge is the focus of this paper. We also highlight that humans are good at making sense of incomplete and approximative information.

Knowledge Sharing in Distributed Agile Projects: Techniques, Strategies and Challenges

“…Agile teams share knowledge through several practices [10]: pair programming, release and sprint planning, customer collaboration, cross-functional teams, daily scrum meetings and project retrospectives. But, the authors [10] argue that, these practices are team-oriented and rely on face-to-face interaction between team members. These practices do not facilitate knowledge sharing in distributed agile teams but are effective for collocated and small teams.…”

“…Not satisfied (0-3), Satisfied (4)(5)(6) and Highly satisfied (7)(8)(9)(10) Dispersed teams-α, β, δ; Distributed teams-γ, ε, ζ; Hybrid team-η Though teams face different types of challenges during knowledge sharing among distributed team members, we identified successful knowledge sharing in both locally and globally distributed agile teams from the seven cases studied. Based on the seven cases the above graph (see Figure 2) has been drawn.…”

Knowledge Management in Distributed Agile Software Development

“…Chau and Maurer [14] describe that Agile teams share knowledge through several practices: release and sprint planning, pair-programming, on-site customers, cross-functional teams, daily Scrum meetings, and project retrospectives. They argue that these practices are team-oriented and rely on face-to-face interaction between team members.…”

Auto-tagging Emails with User Stories Using Project Context

“…Some of these tools offer message threads and project wiki for knowledge sharing. The use of wiki was also advised by Chau et al [11] and Auer et al [12]. However, in a case study based on suggestions from [7], Korkala et al found email to be the preferred medium for sharing knowledge in asynchronous communication [13].…”