I ran a half-day workshop yesterday at the Software Architecture Summit in Berlin, where we crowdsourced the answers to a number of questions, focussed around why some agile software teams don't think about architecture and how we can change this situation. Of course, much of what we discussed can be applied to *any* team, but the focus was agile here.
1. What is architecture?
2. What is agile?
3. Is architecture important?
4. Why don't some agile teams think about architecture?
5. How can we reintroduce agile teams to architecture?
You can view my slides online. Thanks to everybody that came along, I really enjoyed it.
Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.