Software Architects and Autonomous Teams

How Does a Software Architect Fit into Autonomous Teams?

Photo by You X Ventures on Unsplash

Social aspects of developing software

Functional Teams vs. Cross Functional Teams

Functional teams are knowledge silos
Cross functional teams

Cross Functional Teams vs. Autonomous Teams

  • takes decisions regarding the software architecture as well on some hardware related topics
  • is more related to the C-levels
  • is responsible for the quality of software
  • enforces technical standards, tools and platforms

Architect as a role in a team

Architect as role in a team

Architect-as-a-service

Architect-as-a-service
  • Due to the meta-involvement in all teams, an architect is able to spread success stories across the teams.
  • Having a dedicated instance to identify common requirements (standards). No need to reinvent the wheel multiple times.
  • Communicational overhead is not directly within the teams, whereby this primarily is true for social interactions and knowledge sharing across teams. The architect-as-a-service can moderate and foster communication paths, where it is vital for the project’s success.
  • The architect has a less emotional relationship to a team’s product which facilitates more pragmatic decisions/ advice.
  • Being not a full-time team member, the architect can focus more on specific topics and architectural work than a developer who implements features.

Recap

References

--

--

Software-Engineer and DevOps-Enthusiast, AWS Solutions Architect Professional, GCP Professional Cloud Architect

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Pascal Euhus

Software-Engineer and DevOps-Enthusiast, AWS Solutions Architect Professional, GCP Professional Cloud Architect