Architecture is a process. Teams should not think about getting to an architecture, but rather practising it on an ongoing basis.

In this talk, we are sharing recommendations for agile teams about how to practice architecture, and do it well. To practice architecture, you involve all the relevant roles and functions in this process as software architecture is impacted by everyone: engineers, product owners, UX designers, tech leads, DevOps engineers.

In order to do architecture well, you must have a well balanced system without weak points. For that, you need to apply architecture consistently. Therefore, we provide recommendations about implementing “coordination” between the roles to get to a very fluid state where consistency comes naturally from team and their interactions