We also have multiple, agile teams (some do Kanban, some Scrum), and architects. The architects are responsible for infrastructure that spans all of our products (helper libraries, authentication, build infrastructure) etc. They make technical decisions, but also implement things, mostly infrastructure components.
This works well, and there's usually no conflict. I believe one crucial point is:
The architects have no formal authority over the teams, and cannot just overrule them. Normally, the architects make decisions that apply to all products, and the teams make decisions for their product. If there is a conflict, then architect & team just need to reach an agreement, or escalate to management (though that rarely happens).
I think it's really important to make architects and developers peers. Both work towards a common goal, just in different areas. If no one can just "overrule" the other, cooperation will be better.
ron burgundy millennial media nit championship transcendentalism bells palsy channel 5 news uc berkeley
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.