2021
DOI: 10.1109/access.2021.3090098
|View full text |Cite
|
Sign up to set email alerts
|

A Study on Mitigating the Communication and Coordination Challenges During Requirements Change Management in Global Software Development

Abstract: Global Software Development (GSD) is widely used by software development organizations to ensure the development of a cost-effective software product. GSD has now become a common engineering practice adopted by a significant number of multinational software development organizations, and even individuals (freelancers) are seeking numerous benefits including low development cost, highly skilled workers, and access to better development ideas. However, communication and coordination challenges remain a prominent… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
6
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(11 citation statements)
references
References 51 publications
0
6
0
Order By: Relevance
“…The first phase addressed cultural, language, and time zone difficulties. In the second step, the requirement elicitation approach was used, and requirements were acquired from stakeholders 8 . Good specification debate and negotiation is a significant hurdle to overcome in GSD, but it is impossible to hold good requirements discussions due to the aforementioned issues, such as time gaps, language limits, and cultural differences 9 .…”
Section: Related Workmentioning
confidence: 99%
“…The first phase addressed cultural, language, and time zone difficulties. In the second step, the requirement elicitation approach was used, and requirements were acquired from stakeholders 8 . Good specification debate and negotiation is a significant hurdle to overcome in GSD, but it is impossible to hold good requirements discussions due to the aforementioned issues, such as time gaps, language limits, and cultural differences 9 .…”
Section: Related Workmentioning
confidence: 99%
“…In rst phase, solution for cultural, language and time zone difference were proposed. In second phase, requirement elicitation method was selected and requirements are gathered from stakeholders [9]. Proper debate and negotiation of speci cations in GSD is a vital obstacle to resolve, but it is impossible to have proper discussions on requirements due to the above di culties such as time gaps, language limitations, and cultural differences [10].…”
Section: Related Workmentioning
confidence: 99%
“…Temporal, geographical, and cultural distance are the sub-factors of communication. Temporal distance risk has been identified as a significant risk [10]. According to studies [1], [15], and [30], time zone differences [12], delayed responses [13], incorrect technology selection, improper communication, synchronous communication, and minimal time discussion [1] create temporal distance risks among team members.…”
Section: Related Workmentioning
confidence: 99%
“…In Figure 1, the benefits of GSD are shown. On the other side, there are numerous challenges and risks that global software development must overcome [1][9] [10]. This study's contribution is an SLR conducted in the past [11] to recognize entirely temporal issues in GSD and its mitigation strategies.…”
Section: Introductionmentioning
confidence: 99%