Role of Situational Agile Distributed Model to Support Modern Software Development Teams

Abstract

ADSD (Agile Distributed Software Development) is a growing trend for software development organizations to develop quality software with limited cost and time. However, it gives rise to additional situational challenges. Situational variations result in unstable agile architecture which gets highly affected. Although the present literature focuses on agile architecture but effect of situational variation on the agile architecture still needs consideration. One possible solution is development of conceptual model and incorporation of multiple situational factors. This research study aims to identify the most relevant situations and propose situational ADSD approach for the development of situation-based software architecture framework for agile distributed projects. The study focuses on agile methods, rendering identified situational variations. The approach is developed through analyzing data from literature and their associated work documents. Comprehensive survey helps to bridge the gaps from conceptual to architecture model. The experimental results are acquired through both practical and statistical analysis. The results support Conway’s law, e.g. correlation that maps architecture with the communication and coordination needs. Correlation results show that architecture has major contribution in ADSD and validate the relationship among conceptual model and architecture model. The results also suggest that stable architecture in ADSD can positively affect the product.

Towards Scrum Based Agile Framework for Global Software Development Teams

“…It is becoming widely acknowledged in the software industry [13]. DSD [4,[12][13][14][15][16][17][18][19][20]. The measures should be taken to manage and mitigate these issues by monitoring the system development closely [5].…”

Dynamic Agile Distributed Development Method

“…The result was an unstable software architecture. To address this problem, a situational ADSD (agile distributed software development) framework [18] was proposed, which can handle different requirement challenges for different situations. The gaps in situational ADSD also motivated us to propose a dynamic and generic DADDM, which applies to all kinds of distributed software development processes to complete on time and budget.…”

Towards Taxonomical-Based Situational Model to Improve the Quality of Agile Distributed Teams

“…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]. In GSD projects, both the development teams and stakeholders may be located in different time zones [2]- [5]. However, because of the culture variance and communication barrier between the development teams, software development can become difficult in GSD [6].…”

“…Agile methodology is one of the adaptive methods that can overcome the issues of GSD, such as culture variance and communication barrier. By contrast, emerging releases of agile makes it questionable to achieve a one-size-fits-all strategy [2]. Whereas agile techniques may seem to be the ''silver bullet'' for complex software development having tight constraints [7], the issue with this ''silver bullet'' is amplified when agile software development is used in a distributed environment [8].…”

“…In this research, situational context is ''Agile Distributed Software Development''. Software development teams need to consider situational needs that highly rely on product quality [2]. Situational needs drive the context.…”