Wednesday, January 27, 2010

Agile Discussion - Part 2 of X [Role of An Architect in an Agile World]

So here i am writing this second blog post in series on Agile Posts (read the first one here).

As promised in my last post, and after reading my friend Ron's post I am going to try and answer the following important question. :-


Whats the role of an Architect in an Agile team?

Contrary to the common believe that Agile doesn't need architecture (or an Architect role for that matter), Agile (or specifically XP) doesn't imply Design Is Dead (as Martin Fowler puts it).


Since Agile doesn't believe in BDUF (Big Design Up Front Paradigm), its opponents tend to claim that Agile doesn't require architects which i should say is not the case in reality. (Note: Agilists may say that they don't need Architects sitting in silos segregated from the developers (aka Ivory Tower Architect). Which IMHO is a right thing to say)


So, Agile does indeed emphasize on importance of Architecture, the only difference is, instead of planned design (BDUF) it focuses on evolutionary design. In practice evolutionary design doesn't mean Zero design in the beginning, but rather 'just enough design that is easy to evolve/change/maintain' with passage of time. Obviously, purists on both side of the camp would argue that, BDUF= planned design and Evolutionary Design = Zero Up front design. Since no one can foresee the future and requirements are always changing, reality perhaps lies somewhere in between. What I am suggesting is that from my experience i have seen evolutionary design tend to work better in general (yes, there are no silver bullets here). I can go on talking about this, but I'd rather focus on the role of an Architect in an Agile world and for that i believe following are some key activities (in addition to vanilla responsibilities) an Architect needs to own and be responsible for:


  • Agile Architect is hands-on and participates in day-to-day development

  • Agile Architect is very keen on maintaining the code-quality ( through Code Analysis , Reviews etc.)

  • Agile Architect understands all the stake holders and works towards maximising their value

  • Agile Architect works towards understanding the business domain

  • Agile Architect can not predict the unseen future but can anticipate volatile areas and provide design guide lines accordingly ( a la: Design for Change)

  • Agile Architect makes sure that everyone follows Agile Principles, specially the ones outlined by Uncle Bob)

I think the most important take-away is that Agile Architect is hands-on and participates in the team through out the development life cycle rather than a big bang contribution in the beginning.

IMHO only special agile developers can become Agile Architects and not all software architects are Agile by default.

I think i will leave this discussion at it at the moment and would take it further depending upon your comments/feedback....

Its 3 AM in the morning and i should get some ZZZZ...

ps: also check out the following links:

http://stackoverflow.com/questions/177764/does-a-software-architect-have-a-role-in-agile-esp-scrum

http://www.joelonsoftware.com/articles/fog0000000018.html

http://www.agilearchitect.org/agile/role.htm

4 comments:

Mehroz said...

Great series going on here!! Can't wait to see more of it coming.

Sajjad Rizvi said...

Thanks hammad bhai for great article
i have some reservation on architect role, practically architect just responsible for software design & architecture of the software etc but not involve in coding... so how Agile architect participate in day to day development ??? (can u more elaborate his role ?)
also what level of code review is require ??? (should he use some software for code review ?? )

Hammad said...

@Mehrooz. Thanks for the appreciation. I definately intend to write a couple of more posts. cheers.

Hammad said...

@ Sajjad. Thanks for liking this.
id Architect doesnt get involved in coding then he is what they generally call 'ivory tower architect' which is obviously not the way to go.
I will try to cover code-review in a separate post.
stay tuned.