The call for your proposals

Agile meet Architecture is back under a new name.
The AmA has a new name: AOmA. But why? In today’s turbulent world the adaptability and antifragility of organisations matter more than ever before. The term agile on the other hand has become so diverse that it lost most of its meaning. We want to have a conference where we talk about what really matters: How the efforts to sustain adaptable and antifragile organizations intersect with the things we need in good software architecture. Hence the name Adaptive Organizations meet (software) Architecture – AOmA.
Become part of the people shaping the 2027 AOmA-Conf in Berlin on April 6th and 7th 2027 by [submitting your proposal] (link to sessionize here) before the 15th of November 2026 23:59 CEST.

Feedback and program building

We will build the program from mid November through to December 10th 2026. Since we build the program from your proposals we might contact you during that time to fine tune content and program. Final notice to all people who submitted proposals will be sent out by December 20th 2026.

The conference

The conference continues to be the place where people and ideas from professional software architecture and real-world adoption of contemporary ways of working congregate/mingle/come together.

With two conference days, there will be plenty of time and opportunity to spread your ideas on how to bring those worlds together.

The term adaptive organizations is gaining traction recently because it describes very well what the intention behind many of the efforts of the last decades was. Giving more agency to the people within organizations while simultaneously making the organization more resilient to change and faster to adopt to the changes of the markets.  

The convergence of software architecture and modern organizational development is a critical aspect of modern product development. 
This is the place to address the questions you deem most important in this realm and suggest your answers.

The sessions – delivering tangible insights

We want the program to reflect today’s tough questions and their answers in a representative and actionable way.
We actively curate the program and the idea is to have only one introductory talk per concept and then some in depth talks for those topics, so you can submit proposals for both kinds of sessions.

Range of proposal topics

We want to create a program built upon your input around the main topic of the conference: How do modern approaches to process and organizational design and software architecture complement or counteract each other and how do we best handle that?

To get you started, here are some broad topics we, the program committee, would like to see at the conference:

!!!!!!!!THE TOPICS HAVE TO BE CHECKED!!!!!!

- Contemporary development methods and architecture in the context of
    - software that’s older than you are
    - legacy systems
    - (big) architecture improvements

- Lightweight software development and large environments
    - Architectural governance
    - Participative  decision-making in large organizations
    - Architectural decision-making in non-hierarchical organizations 

- Culture clashes between "Agilists" and "Architects"
    - The troubles modern approaches have with architects (and vice versa)
    - Role of managers and management in agile organizations

- Practical issues
    - DevEx or developer productivity
    - Delete Your Backlog
    - Pair programming/ensemble programming

- The learning organiSation
    - Teaching and didactics
    - Communicating architecture to Teams

- Implications of the use of Artificial Intelligence and LLMs
  (In the scope of organiSational impact and software architecture, not coding, prompt-design or    AI-Basic)
   - How does it influence team structures
   - Building architectures for AI
   - Dangers and pitfalls of AI adoption
   - How does AI shape requirements engineering
   - Collaboration between business and IT in the age of AI

- Adaptive and Antifragile Organizations
    - Betacodex
    - The Semco model
    - …

- (New) Trends and their impact on process- and organizational-design and architecture
    - No Code; Low Code
    - The ShapeUp approach
    - …

Session timing

The session should be 40 Minutes including Q&A. We're especially looking for sessions with a well balanced mixture of lecture style content and hands on experiences for the participants.

Speaker travel and accommodation

Accommodation is covered up to 300 EUR (for those from outside Berlin). Travel is covered up to a certain amount (depending if you’re traveling within Europe or from out of Europe).

Your Submission

We use [Sessionize] (Real conference link here) to collect your submission and to help us evaluate the submissions and create a program. You will need to register with Sessionize to submit. In order to submit we will ask you to provide the following:

• Title of the session
• An abstract describing the session
• Type of the session (introductory or deep dive)
• Tags, how you would characterize your talk
• Your name
• Your title
• A short bio
• Your photo
• Your email
• Optionally more contact information like your LinkedIn page or other socials
  

All submitted sessions are expected to be in English.

We also love to see proposals written by real people, but if you got help from an AI writing the abstract, please proofread and edit it in such a way, that you wouldn’t be embarrassed if you had written it yourself.