

Racing with Two Engines: Navigating Trade-offs in a Large-Scale Legacy Transformation
Commercial enterprises, public organizations, civil institutions, and governmental partners typically require heavy upfront planning and operate within strict hierarchical structures - conditions that resemble a waterfall mindset and often clash with the agile, fail-fast approaches that dominate modern software engineering. This tension has shaped much of our work: while we advocate for adaptive, iterative delivery, our partners cannot simply switch their processes overnight, and we must constantly navigate the gap between two worlds.
We present a case study from a decade-long partnership in the Hungarian public sector. The system in question is critical for the daily life of millions of citizens: a large-scale enterprise application that began as a monolith and is now gradually being renewed into a microservice architecture. This migration represents one of the most complex modernization efforts we ever faced.
The heart of the story lies in the contradictions. As a technically skilled team, we strive to design robust architecture and deliver high-quality code. Through this case, we demonstrate clashes between agilists and architects, the governance of large-scale environments, the co-existence of legacy and modern systems, and the challenges of communicating architectural decisions to non-technical stakeholders.
In this talk, we share lessons learned from a project that feels like racing down the highway in a car powered by two engines, as the legacy and the renewed applications are running side-by-side. Our takeaway is that in such context success does not come from applying agile practices by the book, but from tailoring them carefully to the problem at hand meanwhile constantly improving the teams’ practices. The lessons we share are not abstract principles, but insights from building and evolving a system without which much of a country’s daily life would grind to a halt.
Speaker: László Merckle
7 Architectural Sins: Why We Keep Making Them and How We Can Stop
youtu.beRenovate or Rebuild? Architectural techniques for the million euro tradeoff – Eoin Woods
youtu.beFrom flocks to pyramids: Balancing self-organization and architecture
Nature is full of systems that thrive without central control. Flocks of sparrows turn in perfect synchronization, fungi finding the shortest path through a maze. All without planning. The ultimate self-organizing systems but still complex, adaptive and resilient. In software Spotify squads are a good example of this, but not every company is Spotify.
History shows us the opposite. Pyramids, sky scrapers, space stations require blue prints and coordination. In tech, banking and government represent this deliberate, explicit side of architecture.
Most companies fall somewhere in between. In a place where the tensions between self-organizing teams and intentional design are constant. Both are right, both are necessary. But balancing them is one of the hardest challenges we face today.
In this talk we'll explore that balance, with metaphors and real-world adoption stories. We'll cover:
- When to trust self organizing teams
- When architecture must be explicit
- How to spot the difference
- Examples when self-organization thrived and where it failed without constraints
This is an introductory session aimed at anyone that wrestles with the push between agility and architecture. You'll leave with insights to decide when to let teams find their own way and when to step in.
Speaker: Jos van Schouten
Debiasing Your Software Design Decision-Making
Every significant software design choice—whether you're designing a bounded context, deciding on the system boundary, settling on an architectural style, selecting a complex system integration approach, and even evaluating a block of AI-generated code—has a moment where one path just feels right.
Speaker: Kenny (Baas) Schwegler & Evelyn van Kelle