Sustaining Agility through Architecture: Experiences from a Joint Research and Development Laboratory

Weitzel, Balthasar; Rost, Dominik; Scheffe, Mathias

doi:10.1109/wicsa.2014.38

Cited by 4 publications

(2 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Planning that is limited to one iteration leads to design degeneration and loss of flexibility, which may hinder the agility of the whole project [39]. The main reason for this is that functional requirements cannot be analyzed and developed completely separately, since they are interdependent [36].…”

Section: Theoretical Backgroundmentioning

confidence: 99%

See 1 more Smart Citation

Traditionalisation of agile processes: Architectural aspects

Matkovic¹,

Maric²,

Tumbas³

et al. 2018

COMSIS J

View full text Add to dashboard Cite

Mechanisms of agile processes, suited for cost reduction and timely reaction to dynamic market changes, have also been recognized as useful in the development of complex software solutions. Recent studies focused on expansion of agile processes point to a viable possibility for coexistence and integration of complementary elements of agile and traditional development. Within the scope of this paper, this phenomenon is referred to as traditionalisation of agile processes. Software architecture modeling is one of the most sensitive issues associated with incorporation of elements of traditional development into agile processes. The goal of this paper was to determine how suitable particular explicit architectural practices are for incorporation into agile development processes. A mixed method research was carried out for this purpose. Qualitative component of the research resulted in identification of explicit architectural practices suitable for application in agile development processes. Their significances were determined by means of the quantitative component, realized in the form of an empirical research. The research confirmed that emergent architecture in agile processes is not sufficient for the development of complex software solutions, and that agile processes need to incorporate certain explicit architecture practices. Research results revealed that the agile community has an affirmative attitude towards the idea of incorporating explicit architectural practices into agile development processes, with overall agreement on the significances of particular explicit architectural practices for the development of architecture of complex software systems.

show abstract

Section: Theoretical Backgroundmentioning

confidence: 99%

“…Weitzel, Rost, and Scheffe [39] have coined the term "epic architectures" to denote widening the scope of architectural planning beyond one iteration in Scrum. Epic architecture is an architecture designed for a coherent group of functional requirements.…”

Section: Theoretical Backgroundmentioning

confidence: 99%