Agile and Architect Roles

Discussing roles and responsibilities is always hard in an agile context. One of the principles of agile is self-organization where the number of roles should be kept low. In fact, agile advocates the idea of “generalizing specialists”, where each individuals specialist skill is of less importance than the certain individuals ability to get out of his own comfort zone and the eagerness to learn new things.

Scrum, for instance, has only three roles defined, Scrum Master, Product Owner, and the Team itself. In a self-organized cross-functional team there’s little room for specialist roles like project managers, testers, business analysts, and definitely no ivory tower architects.

However, what agilists might not know is that an IT architect is a generalizing specialist by definition. Although we speak of architect roles and specializations, the basic foundation of skills covers the whole spectra of IT, not only software development, regardless of specialization. That is how Iasa define a business technology strategist.

Iasa architect roles and specializations as of today, together with some main competencies and responsibilities, could be summarized in a picture like the one below:

roles_specializations

How could these roles engage within an agile context…..

 

specializations_agile_engagement

The business architect for instance might be the perfect fit for the product owner role….