Balances between the big picture and now – an agile software architect has to think about what is happening during the development together with aligning it with the big picture of the entire system. Hands-on experience – an agile software architect is also a developer and works on the implementation of the system. 


  • Balances between the big picture and now – an agile software architect has to think about what is happening during the development together with aligning it with the big picture of the entire system.
  • Hands-on experience – an agile software architect is also a developer and works on the implementation of the system. This gives first-hand feedback on the taken architectural decisions.
  • Produces prototypes to make informed decisions – when an important technical decision has to be made, a quick prototype could reveal whether this decision is feasible and how it would affect the existing system. Furthermore, communication with the entire development team is essential as it is a collaborative effort, rather than a single-man activity.
  • Focus on sustainability – it is extremely important that architectural decisions lead to a sustainable software architecture – one that will support the project in the long term. An essential part of this is the personal responsibility and empathy. The agile software architect is part of the development team, so he gets first-hand feedback by his decisions as described above. This increases the level of personal responsibility in contrast to the waterfall approach, where decisions are transferred to the development team to implement.

They are also responsible for working with Tech Leads on the high-level designs, giving technical input on Epics and Features, initial t-shirt estimates, architecture guidance to the Dev teams, removing impediments, mentoring, and reviewing implementation strategies.