Why we continue to hear about a common behavioral pattern in a job title so called “software architect”: ?
It’s that kind of super senior / ex developer that now is doing fancy n types of diagrams (UML, CRC models, DFD, contract model, …),
well in Agile not that many as in a traditional Unified Model like RUP|
but when it’s time to deliver “something” they fail because they are only diagrammers who don’t write code code at all, or the last time they wrote some code it was when they were promoted from a Senior Dev position.
If you want to be a software architect, not a diagrammer boy, you have to get your hands dirty and understand what works and what doesn’t, get a continuous feel of the current technologies and tools available, read and play with the frameworks, understand the latest IT trends and risks, keep an eye on performance and scalability issues, and again , play play play with the code.
Owning a small piece of functionality (not piece of code, piece of functionality :) , so feature not layer) will keep you in the loop in all the sprints, you will get a feeling of what is going on in the real world and help you come down from the ivory tower .
A reading recommandation for today (oldies but goldies), is linked to some big extends with our subject : http://www.agilemodeling.com/essays/agileArchitecture.htm
Happy ”prove it with your code” architecture !