The agile hype is over. DevOps took over, driven by the need to speed up the IT value chain. At the same time, the second wave of digitization is rolling, turning IT systems into an essential ingredient of our business models. In this context, good architectural work is crucial. But instead we often observe a perfect confusion without clear direction – ranging from BDUF over several flavors of hype-driven, lots of one-size-fits-all to dogmatic pseudo-agile „no architecture“. Yet, we have been told that architecture is about those decisions that really hurt if you get them wrong. How can we minimize the risk of getting hurt, especially if we need to go fast? Which approach is right?
In this workshop we will first discuss the challenges of architectural work in a post-agile IT world. Then, after rediscovering why we need architectural work at all, we will set up a surprisingly simple down-to-earth approach for implementing it. After that, we will fill the building blocks one by one. Finally, we will complete the picture by discussing questions like: When should we do what? How much should we do in which context? How can we create a sustainable architecture and where are the limits? Plus some more topics. All this will happen in a mix of bits of theory, lots of interaction and hands-on, plus room for questions, discussion, tips, tricks and more. After this workshop, you will have a better understanding what architectural work actually is about, what is important, what is not, and how to tackle it in practice.