I had the pleasure of delivering the opening keynote at the Agile Software Architecture Symposium that took place in The Netherlands last week. My talk was called "Agility and the essence of software architecture" and the slides are available to view online.
My keynote at the conference last year primarily focussed on the perceived conflict between software architecture and agile approaches, specifically related to the role of software architects and how much up front thinking should be done when undertaking a software project. This year I focussed more on what agility means, how to create a software architecture than is "agile" and some of the practices that support this. I finished by sharing my experience of how teams can influence change by introducing, or sometimes reintroducing, these practices.
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.