# data[].attributes.body
The combination is hard and complicated to implement, and organizations often tend to compromise agility in favor of additional control under the assumption that this is required to cope with the challenges created by the physical separation

# data[].attributes.body
the smart adaptation and alignment of standard practices in combination with tools well-accepted by the development team supports the efficient and effective operation of distributed development projects

# data[].attributes.body
In the agile software development collaboration and coordination depends on communication, which is crucial to successful software development

# data[].attributes.body
In global software development this syn chronization is dependent on KM. Some studies have identifie that knowledge sharing is difficult in distributed agile project due to the lack of face-to-face communication between team members

# data[].attributes.body
we have mapped the identified challenges to 10 knowledge areas of project management. Our mapping shows that most of the challenges are related to human resources, communication and risks knowledge areas and no challenge was mapped to procurement and stakeholder knowledge areas.

# data[].attributes.body
Software developers work with knowledge and are dependent on each other’s work.

# data[].attributes.body
we identified 19 challenges crucial to the success of GSD project management. The top ranked challenges are: ‘lack of cultural understanding in teams’ and ‘lack of communication’. A comparison of the challenges within both the literature review and the survey indicates that there are more similarities than differences between the challenges for clients and vendors.

# data[].attributes.body
Our findings show that most of the client and vendor organizations either strongly agreed or agreed with the literature review findings –indicating that there are more similarities than differences between client and vendor regarding what is a challenge.

# data[].attributes.body
Knowledge sharing needs to be prioritized to
work efficiently,

# data[].attributes.body
The adoption of common practices and tools,
among all sites, has been reported to be a
success factor

# data[].attributes.body
The survey results highlight “expertise,” “site characteristics,” and “task site dependency” as the most important factors for a task allocation decision. The interview study highlighted the importance of situation‐specific decision making during task allocation. The significance of factors varies with the characteristics of task, characteristics of organization, type of GSD, and objective of doing GSD.

# data[].attributes.body
The architectural relationships presented are categorized into 3 main categories of module view type, component and connector view type, and allocation view type

# data[].attributes.body
Differently experienced individuals are able to give valuable feedback, so we included the experience of individuals to ensure that we have respondents in each category

# data[].attributes.body
The organization’s GSD experience affects the way projects are managed. With the increase in the number of years of GSD experience, organizations move through different stages of maturation

# data[].attributes.body
Task allocation should never be performed in isolation, where the characteristics of the task, organization, site, and GSD environment affect the choice of factors. The different variations to the task allocation decision in GSD are task, expertise, organization, and site.

# data[].attributes.body
Careful task allocation is key to achieving an optimal communication level, minimizing connections between sites. This will ease task performance, lead to fewer meetings, fewer emails sent and fewer misunderstandings due to cultural differences. Tasks, and the connections between them, are derived directly from the dependencies within software, which are dictated by the software architecture.

# data[].attributes.body
To share knowledge among distributed sites, team members practice different type of techniques: repositories, pair programming, version control, screen sharing, daily scrums, weekly sprint status, common chat rooms, technical forums, discussion forums, electronic boards, online conferences, rotations/visits etc.

# data[].attributes.body
Difficulties in synchronizing tasks

# data[].attributes.body
Difficulties evaluating work input due to distribution

# data[].attributes.body
Increased needs for coordination when using experts from different sites

# data[].attributes.body
increased amount of effort with modifications involving several developers across different sites

# data[].attributes.body
while work items are, where possible, often kept separate between sites in a distributed setup, multiple sites may be developing large modules which ultimately need to fit together for the final product.

# data[].attributes.body
Task allocation in a distributed setting easily becomes challenging if dependencies between tasks and subsequently between teams are not identified

# data[].attributes.body
how a virtual work environment has been crafted by continuously improving practices and carefully selecting technologies to allow each team member to fully participate regardless of the actual physical location.

# data[].attributes.body
Modern technology helps distributed virtual teams collaborating.

# data[].attributes.body
Communication, coordination and collaboration are the keys to fostering knowledge sharing between team members in agile software development.

# data[].attributes.body
In agile software development most of the knowledge
is tacit, which resides in the human mind rather than documentation.

# data[].attributes.headline
Members of the team should care about customer feedback. 

# data[].attributes.subject
Members of the team should care about customer feedback. 

# data[].attributes.headline
A willingness to record past experiences and create new mechanisms for exchanging knowledge. Innovating ideas are stored in tacit knowledge in the human mind

# data[].attributes.subject
A willingness to record past experiences and create new mechanisms for exchanging knowledge. Innovating ideas are stored in tacit knowledge in the human mind

# data[].attributes.headline
Transparency in peer programming, scrum meetings, and sprints will help scale knowledge acquired during the project while building trust.

# data[].attributes.subject
Transparency in peer programming, scrum meetings, and sprints will help scale knowledge acquired during the project while building trust.

# data[].attributes.headline
Knowledge sharing is enabled by informal communication and interaction. Through daily discussions, team members share their thoughts and create knowledge.

# data[].attributes.subject
Knowledge sharing is enabled by informal communication and interaction. Through daily discussions, team members share their thoughts and create knowledge.

# data[].attributes.headline
Attending weekly or monthly seminars facilitates common understanding and communication between team members. 

# data[].attributes.subject
Attending weekly or monthly seminars facilitates common understanding and communication between team members. 

# data[].attributes.headline
Being open-minded to peer learning and community learning. In peer learning, team members start learning through interacting and collaborating with team members

# data[].attributes.subject
Being open-minded to peer learning and community learning. In peer learning, team members start learning through interacting and collaborating with team members

# data[].attributes.headline
 Agile teams contribute to knowledge sharing through practices such as pair programming, release and sprint planning, customer collaboration, cross-functional teams, and daily scrum meetings.

# data[].attributes.subject
 Agile teams contribute to knowledge sharing through practices such as pair programming, release and sprint planning, customer collaboration, cross-functional teams, and daily scrum meetings.

# data[].attributes.body
Decoding is another pathway to create story-sized portions and send requirements as storyboards directly that can be allowed for more participation while focused on the theme.

# data[].attributes.body
When working with a remote team member, the requirements delivery process might be more difficult because teams are often given large specifications to look through.

# data[].attributes.body
Continuous integration by putting everyone on the same code base helps stay connected to the mainline, no matter where they are.

# data[].attributes.body
How distributed teams can adequately explain the logic of functionality, even with the finest efforts put out in creating it which is nearly impossible

# data[].attributes.headline
How are the tasks prioritized and assigned between the team members in a distributed agile project?

# data[].attributes.subject
How are the tasks prioritized and assigned between the team members in a distributed agile project?

# data[].attributes.headline
What are the challenges faced by the team members when sharing knowledge in a distributed agile project?

# data[].attributes.subject
What are the challenges faced by the team members when sharing knowledge in a distributed agile project?

# data[].attributes.headline
How do team members share knowledge in a distributed agile project?

# data[].attributes.subject
How do team members share knowledge in a distributed agile project?

# data[].attributes.headline
How do team members contribute to knowledge creation in a distributed agile project?

# data[].attributes.subject
How do team members contribute to knowledge creation in a distributed agile project?