Systematic Literature Review of Knowledge Sharing Barriers and Facilitators in Global Software Development Organizations Using Concept Maps <s> 4) TRAININGS AND WORKSHOPS <s> Knowledge management (KM) is essential for success in global software development. Software organizations are now managing knowledge in innovative ways to increase productivity. In agile software development, collaboration and coordination depend on the communication, which is the key to success. To maintain effective collaboration and coordination in distributed agile projects, practitioners need to adopt different types of knowledge sharing techniques and strategies. There are also few studies that focus on knowledge sharing in distributed agile projects. This research identified the knowledge sharing techniques and strategies applied by the practitioners in distributed agile projects. Challenges faced by the practitioners during knowledge sharing in distributed agile projects are also identified and discussed. <s> BIB001 </s> Systematic Literature Review of Knowledge Sharing Barriers and Facilitators in Global Software Development Organizations Using Concept Maps <s> 4) TRAININGS AND WORKSHOPS <s> Knowledge Management (KM) and knowledge sharing (KS) have become crucial tasks for both Middle Managers and Top Managers of many organizations, especially those who highly rely on the type of knowledge which is difficult to transfer from one person to another, or what is called "Tacit Knowledge". The objective of this case study is to review the practical knowledge transfer techniques, the main motivators and demotivators of a tacit knowledge transfer process, and the measures that can be taken to overcome the demotivation factors. Siemens is chosen for this case study because it has been recently rated as one of the top Knowledge-Management-driven companies. We present here our own observations on some of the KM practices that Siemens strives to implement in its branches in the Middle East countries and the barriers which are challenging such practices. <s> BIB002 </s> Systematic Literature Review of Knowledge Sharing Barriers and Facilitators in Global Software Development Organizations Using Concept Maps <s> 4) TRAININGS AND WORKSHOPS <s> We present systematic literature review of 61 primary studies (2000September 2014) that empirically reported knowledge sharing challenges and practices in Global Software Development (GSD).We found knowledge sharing challenges and practices in GSD could be classified in 6 main themes: management, team structure, work processes/practices, team cognition, social attributes and technology.Regarding contextual settings, we found empirical studies were mainly conducted in offshore outsourcing collaboration model distributed between two sites. Most of the studied organizations were large enterprises. ContextGlobal Software Development (GSD) presents significant challenges to share and understand knowledge required for developing software. Organizations are expected to implement appropriate practices to address knowledge-sharing challenges in GSD. With the growing literature on GSD and its widespread adoption, it is important to build a body of knowledge to support future research and effective knowledge sharing practices. ObjectiveWe aimed at systematically identifying and synthesizing knowledge sharing challenges and practices. We also intended to classify the recurrent challenges and most frequently reported practices in different contextual settings. MethodWe used Systematic Literature Review (SLR) for reviewing 61 primary studies that were selected after searching the GSD literature published over the last 14 years (2000September 2014). We applied thematic analysis method for analysing the data extracted from the reviewed primary studies. ResultsOur findings revealed that knowledge sharing challenges and practices in GSD could be classified in 6 main themes: management, team structure, work processes/practices, team cognition, social attributes and technology. In regard to contextual settings, we found empirical studies were mainly conducted in an offshore outsourcing collaboration model distributed between two sites. Most of the studied organizations were large enterprises. Many of the studies did not report any information for several contextual attributes that made it difficult to analyse the reported challenges and practices with respect to their respective contexts. ConclusionWe can conclude: (a) there is a higher tendency among researchers to report practices than challenges of knowledge sharing in GSD. (b) Given our analysis, most of the reported knowledge sharing challenges and practices fall under the theme of work practices. (c) The technology related knowledge-sharing challenges are the least reported; we discussed the available technologies for supporting knowledge sharing needs in GSD. (d) The organizational contextual information is missing from a large number of studies; hence, it was not possible to investigate the potential relations between knowledge sharing challenges/practices and the contextual attributes of GSD teams. We assert the need of exploring knowledge sharing in the context of small/medium sized organizations to avoid the risk of findings being biased by specific empirical setting (e.g., large enterprises distributed between US and India). <s> BIB003 </s> Systematic Literature Review of Knowledge Sharing Barriers and Facilitators in Global Software Development Organizations Using Concept Maps <s> 4) TRAININGS AND WORKSHOPS <s> Empirical findings from ten software teams from two large-scale software development projects in Ericsson and ABB demonstrated that teams receive and share their knowledge with a large number of contacts, including other team members, experts, administrative roles, and support roles.Along with human and organizational capital, social capital and networking are also necessary for participation in large-scale software development, both for novice teams and for mature teams working on complex, unfamiliar, or interdependent tasks.Social capital has the potential to compensate for gaps in human capital (i.e., an individual's knowledge and skills).The team network size and networking behavior depend on the following factors: company experience, employee turnover, team culture, need for networking, and organizational support.Along with investments in training programs, software companies should also cultivate a networking culture to strengthen their social capital and achieve better performance. ContextLarge software development projects involve multiple interconnected teams, often spread around the world, developing complex products for a growing number of customers and users. Succeeding with large-scale software development requires access to an enormous amount of knowledge and skills. Since neither individuals nor teams can possibly possess all the needed expertise, the resource availability in a team's knowledge network, also known as social capital, and effective knowledge coordination become paramount. ObjectiveIn this paper, we explore the role of social capital in terms of knowledge networks and networking behavior in large-scale software development projects. MethodWe conducted a multi-case study in two organizations, Ericsson and ABB, with software development teams as embedded units of analysis. We organized focus groups with ten software teams and surveyed 61 members from these teams to characterize and visualize the teams knowledge networks. To complement the team perspective, we conducted individual interviews with representatives of supporting and coordination roles. Based on survey data, data obtained from focus groups, and individual interviews, we compared the different network characteristics and mechanisms that support knowledge networks. We used social network analysis to construct the team networks, thematic coding to identify network characteristics and context factors, and tabular summaries to identify the trends. ResultsOur findings indicate that social capital and networking are essential for both novice and mature teams when solving complex, unfamiliar, or interdependent tasks. Network size and networking behavior depend on company experience, employee turnover, team culture, need for networking, and organizational support. A number of mechanisms can support the development of knowledge networks and social capital, for example, introduction of formal technical experts, facilitation of communities of practice and adequate communication infrastructure. ConclusionsOur study emphasizes the importance of social capital and knowledge networks. Therefore, we suggest that, along with investments into training programs, software companies should also cultivate a networking culture to strengthen their social capital, a known driver of better performance. <s> BIB004
Weekly and monthly workshops and seminars helped in understanding project knowledge between ''business teams'', ''technical teams'' and ''customers'' in distributed agile teams BIB001 . In a survey it was reported that 74% of employees preferred meetings/workshops as a method for sharing knowledge between employees. It was also found that tacit knowledge was easily shared through seminars via socialization BIB002 . Formal training arrangements facilitated KS between team members BIB003 . Employees participation in forums facilitated the interaction between team members in the organization BIB004 .