Dynamikrobuste Softwareentwicklungsteams sind cross-funktional und fokussieren möglichst unabhängig von anderen Teams auf eine kognitiv bewältigbare (fachliche) Domäne. Um dies optimal tun zu können, benötigen sie Unterstützung von Plattform-Teams, die ihnen entlastende (Self-)Services anbieten.

Um von einem klassischen OPS-Team zu einem Plattform-Team zu werden, muss zum einen eine gewisse Kundenorientierung und Dienstleister-Mentalität etabliert werden, zum anderen braucht es ein passendes Angebot von Services und Produkten für die Entwicklungsteams. Im Optimalfall sind die Nutzung der Deployment-Plattform und die der unterstützenden Services für Entwicklungsteams freiwillig.

Welche Haltung, Rollen und Methoden es dafür braucht, beleuchten wir in diesem Vortrag.

Zielpublikum: Architekt:innen, OPS/Plattform-Teams, Führungskräfte, Menschen, die Dynamikrobustheit anstreben
Voraussetzungen: Keine
Schwierigkeitsgrad: Basic

Eigentlich definiert Architektur „nur“ die Struktur der Software. Aber das Gesetz von Conway weist schon auf den Zusammenhang zwischen Architektur und Organisation hin. Durch das Inverse Conway Maneuvre ist klar geworden, dass die geschickte Aufstellung der Organisation die Architektur maßgeblich beeinflussen kann.

Dieser Vortrag zeigt auf, dass Team Topologies auch erhebliche Konsequenzen für die Architektur-Arbeit hat: Team Topologies fungiert nicht nur als Werkzeug für Architektur, sondern muss auch in die architektonische Planung einbezogen werden.

Zielpublikum: An Softwarearchitektur und Organisation Interessierte
Voraussetzungen: Grundlegendes Verständnis von Softwarearchitektur und Entwicklung im Team
Schwierigkeitsgrad: Basic

If you have worked in the software industry for a while, you’ll have a hunch that technical skills are often not what stands between us and our success. Around software systems, there are always complex human systems, whose runtime dynamics seems full of fixes that don’t work. As software professionals, can we just tell jokes about SAFe, about being able to copy the Spotify Model, but not paste it? Or should we give the usual shrug – “it’s the system’s fault”?

Xin has been a design and architecture practitioner for more than a decade. Drawing on her own developmental journey, Xin makes a case for the rising relevance of sociotechnical design in a post-modern world, where aging companies struggle with aging software, while adding new software and complexity to their IT portfolio.

This talk weaves together experience reports that illustrate different facets of complexity in software and human systems. It highlights the sociotechnical principles and practices that lie at the center of Domain-Driven Design (DDD) and adjacent practices such as Systems Thinking and Constraints Framework.

From a systems standpoint, we are part of the same mess. If we can become better at seeing and naming the elephants in the room, not as random events, but as systemic patterns described through a consistent systems language, then the current messy reality is no longer our enemy but our ally. It can become a generative force for us to identify leverage and sustain influence, making better impact with our craft.

Join Xin to reflect together on, how we can leverage a multi-dimensional, sociotechnical design toolbox to help us see the system, share the system, and build the system in a reality of vast complexity and constant change.

Target Audience: Architects, Developers, Product Professionals, Engineering Managers, UX Designers
Prerequisites: Prior knowledge of Domain-Driven Design is beneficial for in-depth understanding but not a must
Level: Expert

Creating high-quality software is challenging due to a focus on solutions over understanding organizational context. Developers need to engage with stakeholders across contexts. However, stakeholder communication can lead to misunderstandings and conflicts, disrupting knowledge sharing. This often results in autocratic decisions by architects. Achieving sustainable and design decisions, it's more effective to employ visual techniques, improving collaboration with stakeholders.

This talk explores collaborative modeling, a technique for analyzing complex decisions with all stakeholders. Inclusive sessions and skills like observing, listening, neutrality, and empathy are key. The goal is for teams to understand stakeholder needs, guiding software architecture through collaborative design.

Target Audience: Technical leaders, decision makers, software engineers, architects
Prerequisites: None
Level: Advanced

Disclosure - this is a talk about people - not about AI. This is a talk about how we will continue to apply our humans strenghts in a world enhanced by AI.

One of the LLM engines I work with seems to think it can take over my job as an architect. I say with some confidence that for the next few decades, my job will be heavily influenced by AI, but not replaced by AI. For example I am presenting and OOP and *it* is not.

Software architects and system architects will not be replaced anytime soon by Generative AI or LLMs. They will be replaced by software architects that know how to leverage Generative AI and LLMs, and just as importantly, know how NOT to use Gen AI. For the last two years, Avraham has been on a journey exploring the use of AI to augment the way he does architecture and makes architecture decisions as well as assimilate the architectural understanding within the organization.

Along the way, Avraham has learned so much both about generative AI's abilities and limitations, and even more about himself as an architect and as a person. For example, Avraham has learned that AIs can propose tradeoffs along with convincing suppporting arguments, but only a human Architect can be held accountable. An AI might be able to create a drawing and talk you through it, but only a human architect will appriciate the look of confusion on your face and emphasize that one dotted line that makes everything clearer.

In the talk, Avraham invites you to join him on his journey. This talk will equip you with the knowledge and very practical tools to start on your own adventure to leverage the power of GAI, elevate your architectural practice, and hopefully stay ahead of the curve.

Target Audience: Software Architects, Developers, Decision Makers
Prerequisites: Basic Curiosity about AI and machine learning
Level: Advanced