Please use this identifier to cite or link to this item:
|Scopus||Web of Science®||Altmetric|
|Title:||Agility and architecture: can they coexist?|
|Citation:||IEEE Software, 2010; 27(2):16-22|
|Pekka Abrahamsson, Muhammad Ali Babar, Philippe Kruchten|
|Abstract:||Agile development has significantly impacted industrial software development practices. However, despite its wide popularity, there's an increasing perplexity about software architecture's role and importance in agile approaches. Advocates of architecture's vital role in achieving quality goals for large software-intensive systems doubt the scalability of any development approach that doesn't pay sufficient attention to architecture. This article talks about software architecture being relevant to the basis of aspects such as communication among team members, inputs to subsequent design decisions, documenting design assumptions, and evaluating design alternatives. In a large software organization, implementing agile approaches isn't a straightforward adoption problem. Most likely, it will take several years to shorten the feedback cycles to benefit from the adaptability and earlier value-creation opportunities. Failure is a natural part of process improvement.|
|Description:||Guest Editor's introduction|
|Rights:||© 2010 IEEE|
|Appears in Collections:||Computer Science publications|
Files in This Item:
There are no files associated with this item.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.