Agile vs. plan-driven perceptions of software architecture

Hadar, Irit; Sherman, Sofia

doi:10.1109/chase.2012.6223022

Cited by 9 publications

(12 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As several authors agree, the role of a software architects in an agile team should significantly differ from the traditional one, because architects must continuously be engaged throughout the whole development process. Their role must involve coordination throughout the whole development of the software solution [44,[49][50][51]. However, the respondents stated that the architect's only role is the coordination of detailed design.…”

Section: Interview Resultsmentioning

confidence: 99%

“…Hadar and Sherman [49] also stated that is important to include the software architect into the entire agile development process, while Blair et al [44] stress the need for the architect's close collaboration with the development team, with continuous exchange of ideas throughout the whole project. Hopkins and Harcombe [50] believe that the software architect's role is indispensable in the development and delivery of large, complex systems, which typically necessitate development and integration of multiple systems and coordination of hundreds of individuals.…”

Section: Theoretical Backgroundmentioning

confidence: 99%

“…Results of the literature review suggest that a great portion of problems arises from one additional essential conflict: requirement of minimalism in agile processes and the need for well-documented architecture in complex systems [49]. Evidences from the industry reveal that, in most cases, architectural documentation is either excessive, or completely absent [55].…”

Section: Theoretical Backgroundmentioning

confidence: 99%

See 2 more Smart Citations

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: Interview Resultsmentioning

confidence: 99%

Section: Theoretical Backgroundmentioning

confidence: 99%

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

show abstract

“…This angered Vendor A's management because their fixed price bid was based on the Big Design Up Front (BDUF) requirements and they were concerned about the impact to their profitability. BDUF is where the architecture phase is accompanied with a vast amount of documentation [10].…”

Section: Confusionmentioning

confidence: 99%

Lessons Learned from a Failed Attempt at Distributed Agile

Rajpal

2016

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. What do you do when you have endured an Agile experience where things didn't go so well? You can abandon Agile altogether or you can take those lessons learned and apply them to future Agile projects. This paper discusses the journey travelled from that painful experience to becoming a more confident and experienced Agile practitioner. We will also look at some of the challenges that I still encounter today.

show abstract

“…It is reported that about 31% of the industry practices agile methodology, including tailored versions [7]. Agile methodology has been found to be of great value to software development, improving quality and shortening time-to-market of software products [8].…”

Section: Introductionmentioning

confidence: 99%