I came over a blog talking about being a software architect in an agile world (codebetter.com/…). Agile missionaries weren’t very fond of the term “architect” as it too many times ment a person drawing up som schemes for the developers to implement, a part of the waterfall-dinosaur development process, soon to be extinct. Still, is there a place for architects in todays software development?

“Architect” is a fancy title many use, often just to make a customer comfortable. Titles like “senior product architect” or “business solution architect” are also heard. Still, as the agile manifesto  talks about, working software is the primary goal. Not some fancy documents and diagrams of how a solution might be.

But I believe, as blogger states, there’s room for the “architect” term in an agile world. But it’s not about designing the system up front. It’s about using your technical knowledge, patterns and best practice when developing together as a team. Allowing the team to make improvements, always keeping the big picture in mind, using agile modelling to have the overall model.

I can’t think of a better team than a bunch of agile architects.