Simon Brown discusses the role of the software architect, challenging some of the current assumptions and trying to redefine it in the context of Agile development.
Simon Brown is an independent consultant based in Jersey, the founder of Coding the Architecture and either a software architect who codes or a software developer who understands architecture. Having successfully delivered a variety of projects on the .NET and Java platforms, Simon now uses his experience to train and coach teams in delivering better software.
GOTO Aarhus is the enterprise software development conference designed for team leads, architects, and project management and is organized by developers, for developers. As software developers and architects ourselves, we wanted to craft the ultimate conference. The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community, staged in an intimate environment needed to support as much learning and networking as possible.<a href="http://gotocon.com/">http://gotocon.com/</a>
One Architect v.s. Many Architects
The conference mentions the explicit case where there is a single architect in a project, and suggest to migrate to explicitly developers sharing the architecture role.
But, it didn't mention that , in real world, many projects, doesn't have an explicit architect, and instead, implicitly every programmer performs its own architecture.
A plus for mentioning the "shinning new toy sindrome".
The Frustrated Former Software Engineer
Regardless, I suspect that within 10 years software architecture will be relegated to the now emerging platforms-as-a-service, and mobile OS's. Abstractions are becoming more "first class" by the day. But for now, I suppose it makes sense to bring these issues to light as a counter-revolutionary buffer/reminder against uncontained Agile revolution.