Essential architectural thinking - why, what, when, how and how much?

The agile hype is over, leaving us with even more confusion regarding architectural work. When? How much? Who? And over all the heated debates and (often) dogmatic answers, the question why we are doing it in the first place completely faded into oblivion.

But wait, we know it: "Architecture is about the important decisions!" - which starts the next set of heated discussions: Is it? What kind of important decisions? Does that mean all other decisions are irrelevant? And still the question why we are doing architectural work remains in oblivion.

Therefore, in this session we will try to unearth the forgotten question and rediscover the essence of architectural thinking. We will ask ourselves: Why do we need architectural work? Which problem(s) does it address?

After shedding some light on this question, we will move on and ask ourselves: How can we do it best? What are the key activities of architectural work and how can we fill them with life?

Finally, we will ask ourselves: When should we do what and how much, depending on the given context - and how can we tackle the question of sustainability?

After this session, you will have a better understanding what architectural work actually is about and how to do it without hypes or dogmas, but stripped down to its essence.

>>> Speaker Bio >>>

Uwe Friedrichsen travels the IT world for many years. As CTO and fellow of codecentric AG he is always in search of innovative ideas and concepts. His current focus areas are (distributed) system design and the IT of (the day after) tomorrow. Often, you can find him on conferences sharing his ideas, or as author of articles, blog posts, tweets and more.

>>>