In the realm of Agile and DevOps, architecture is omnipresent, whether explicitly articulated or not. The question arises: must architecture undergo a transformation to align with the prevailing Agile and DevOps ethos?

Within the agile movement, the role of the "Architect" and what "architecture" means began to be discussed. Is it still relevant? What does a person do? What even means "architecture"? And is DevOps technology a culture or a mindset?

With this talk, I take a structured approach to uncovering what DevOps and Architecture mean by using existing sharp and easy-to-understand definitions. I go further by building up a universal approach to supporting DevOps with any architectural method by using a scientific paper that distilled commonly used architectural frameworks.

The journey goes from non-functional requirements derived from DevOps and abstract suggestions about supporting them as part of the architecture - ready to be translated into technical measures on different layers of abstractions (From enterprise, over the system to software architecture).