Four Types Of The Software Architect's Role in Product Teams
This post contains four types of the software architects role in product teams. Which do you prefer?
![Four Types Of The Software Architect's Role in Product Teams](/content/images/size/w1200/2023/10/1-3-1.png)
I often have the discussion about the ๐๐๐๐ of the software architect in product teams.
๐น Is there one person ๐๐๐ software architect?
๐น Is the software architect role ๐
๐๐๐๐๐๐๐๐๐๐
across the team?
๐น How do you make architecture and technology decisions?
๐น Who is responsible for software architecture decisions?
Based on these questions, I have tried to summarize four different types of roles that can determine the work of software architecture in a product team ๐๐ผ
The Benovelent Dictator
"Architect decides, Team executes" (Source)
![](https://www.workingsoftware.dev/content/images/2023/10/2-2.png)
The Architecture Owner
"Architect as just-another Dev-Team Member"
![](https://www.workingsoftware.dev/content/images/2023/10/3-2.png)
Architecture Agents
"Divide the role of the architect on the specific know-how"
![](https://www.workingsoftware.dev/content/images/2023/10/4-2.png)
Architecture Democracy
"Independent and collaborative coordination in all architectural decisions."
![](https://www.workingsoftware.dev/content/images/2023/10/5-2.png)
Which of these do you implement in your product teamโ
Which do you preferโ
By the way, in coming up with these role descriptions, I was heavily influenced by the following great blog posts and books ๐๐ป:
![](https://architectelevator.com/assets/img/doing_architecture_og.png)
![](https://images.bannerbear.com/direct/lPOmJb1YEaE160g4Ga/requests/000/043/304/906/kW7yv9eBdzp9ZeA86NLRwa5Px/4bf5fd87402df3d50397ab443a4f5dee32853f35.jpg)
Past thoughts about the positioning of a software architect by analyzing different agile organisation frameworks.
Comments ()