This Wednesday, after the training course and as a part of Skills Matter's London Agile Month, we'll be running a session entitled "How much architecture is enough?". Although this is billed as "In the Brain of Simon Brown", it's actually going to be an "In *our* Brains" session where a few of us will be facilitating a group discussion.
As for how much architecture is enough, well we've touched upon this question before, particularly with respect to the level of design detail you should put in your architecture document and the need for just enough quality. While I don't think that software development is a relay sport, if you are planning on handing off your architecture, how much do you need to do to ensure that this exercise is successful? And on the subject of sharing architectures, how much should you share and are there more creative ways of efficiently delivering your message?
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.