Thanks to everybody that came along to my "Pitfalls for new software architects" talk at DevWeek 2009 last week ... I hope you found it a useful look at some of the traps that I've seen people (including myself!) fall into over the years. The pitfalls are structured into a number of different areas as shown in the diagram below.
Each of these areas is part of our view of what a hands-on software architect should do, and the talk itself compliments a session I delivered at Software Architect 2008 called "Why software projects fail". You can download the slides for both sessions below.
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.