The architect is dead. Long live architecture!
As an agile coach I am often confronted with an odd folk named "software architects". Actually I have been one of those guys for a long time myself. I just had an interview where a group of my current company wanted to hire me as a co-architect. Feeling honored on the one hand I still couldn't really explain an annoying feeling on the other hand. Something was disturbing me and I tried to get a grasp on it. I noticed I'm in constant struggle with these architects since I began to breathe agile air. So why is that, what is really behind this sudden resentment towards the job title "architect"? Is the architect outdated in an agile world? Should we get rid of them? I say "yes" (just to do some shocking). But does that mean that in an agile world there's no place for architecture? Of course not. That would be silly. Even if we claim that software architecture should be evolving out of the teams and that means along stories or epics it