Abstract
Over the recent years, we’ve seen a constant stream of tutorials and workshops on "agile architecture" in conferences and there seems to remain a variety of suggested answers to this question - how should agile methods and architecture relate to each other and whether evolutionary design should include architecture or stick to what’s inside the boxes?
The idea of emergent design through Test Driven Development and Refactoring has been a popular concept in discussions ever since Extreme Programming Explained was published but many consultants suggest that we shouldn’t let it all emerge from code and rather carry out some up-front design in the form of iteration design workshops, for example. Some even suggest that TDD tends to lead to downright bad architectures.
What is the answer? Can we reach agreement? Can we agree on a good approach for a given scenario? Or is architecture the software community’s wild west where whoever holds the gun is right?
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsAuthor information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2008 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Koskela, L. (2008). Architecture and Agility Are Not Mutually Exclusive. In: Abrahamsson, P., Baskerville, R., Conboy, K., Fitzgerald, B., Morgan, L., Wang, X. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2008. Lecture Notes in Business Information Processing, vol 9. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-68255-4_45
Download citation
DOI: https://doi.org/10.1007/978-3-540-68255-4_45
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-68254-7
Online ISBN: 978-3-540-68255-4
eBook Packages: Computer ScienceComputer Science (R0)