Abstract
At present, software organizations are developing software products that employ global software development (GSD) teams. Organizations tend to adopt new methodologies for global software development, among which is the use of agile in the GSD industry, which yields both benefits and challenges. However, software development teams do not consider situational needs that delay software delivery, resulting in the late discovery of incompatible assumptions and architecture level rework. In this study, we conduct a systematic literature review (SLR) to identify the situational factors that need to be considered by software development teams before developing a software product. We further present taxonomical classification and comprehensively map the situational factors that impact design development and advancement in the proposed Situational Agile Distributed Development (SADD) model. We propose 18 directed hypotheses against each situational factor that supports our SADD model. In order to evaluate our directed hypotheses, statistical analysis method is used, and the level of confidence of each directed hypothesis is validated. The result of our study confirms that global software development teams are highly reliant on the SADD Model. Our study will largely contribute by devising a multilevel taxonomy of situational factors that elevate the performance of global software development teams. This taxonomical classification will allow to better map the relationships between multiple situational factors and elevate the process of creating a holistic model to handle situational needs in the context of Agile Distributed Software Development (ADSD).
Highlights
Over the years, global software development (GSD) has taken over the co-located software development model because of the former’s increased benefits, such as increased quality and decreased cost [1]
Agile Distributed Software Development (ADSD) groups ought to have the option to look at situational factors, which should be utilized in making new situational approaches, in order to approach the up-and-coming entrepreneur
It proposes a Situational Agile Distributed Development (SADD) model of situational barriers, which presents the key categories of the situational barriers that can serve as knowledge for academics, researchers, and practitioners working on situational method engineering and software architecture in the agile distributed software development
Summary
Global software development (GSD) has taken over the co-located software development model because of the former’s increased benefits, such as increased quality and decreased cost [1]. We first conducted a systematic literature review (SLR) [10] for the period of 2013 to 2019 to analyze the current state-of-the-art approaches regarding situational factors and needs of ADSD teams. The objective of this SLR was to systematically identify the situational factors that need to be considered by software development teams before developing the software product. This will help to analyze and present a taxonomical classification and comprehensively map the situational factors that impact design, development, and advancement in the proposed SADD.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
