The conference
Agile meets Architecture is designed to be the premier gathering where professionals from the realms of software architecture and real-world agile adoption can come together, exchange ideas, and collaborate.
With two conference days, there will be plenty of time and opportunity to spread your ideas on how to bring those worlds together.
As outlined in our Code of Conduct, we are committed to creating a truly inclusive and welcoming environment. For example, if you are a parent, we will do our best to accommodate your needs. This commitment extends to any other requirements as well. When registering, please let us know in the “Notes” field, and we will reach out to discuss the details.
Despite decades of professional software architecture and 20 years since the Agile Manifesto, many questions still remain about the various approaches and their trade-offs. Agile meets Architecture is the place to address the most important questions and propose your solutions.
The call for your proposals
The "Agile meets Architecture" is back for it’s fourth instalment, and the first years were amazing (if we should humbly say so ourselves). Have a look at what happened on our YouTube channel and read what participants and speakers said.
Become part of the people shaping the 2026 AmA-Conf in Berlin on March 10 and 11, 2026 by submitting your proposal before October 5, 2025, 23:59 CEST.
Feedback and program building
We will build the program from early October through to mid November, 2025. 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 November 22, 2025.
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.
After decades of professional software architecture and more than 20 years after the Agile Manifesto, there are still many questions left unanswered when it comes to different approaches and their tradeoffs. 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 on those topics so that 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 IT organizations, products, and projects 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:
- 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 organization
- Teaching and didactics
- Communicating Architecture to Teams
- Implications of the use of Artificial Intelligence and LLMs
(In the scope of organizational 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
- (New) Trends and their impact on agility and architecture
- Betacodex
- No Code; Low Code
- The Semco model
- Open-Space Agility
- Serverless approaches
- The ShapeUp approach
Session timing
A 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 to collect your submissions 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
- Your high-resolution photo
- Your email
- Optionally more contact information like your LinkedIn address
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.
Accommodation is covered up to 300 EUR (for those from outside Berlin). Travel is covered up to a certain amount (depending if you’re travelling within Europe or from out of Europe).
If you haven't logged in before, you'll be able to register.
Using social networks to login is faster and simpler, but if you prefer username/password account - use Classic Login.