Agile meets Architecture Berlin 2023
2023-10-05..2023-10-06
Berlin, Germany
[Agile meets Architecture Berlin 2022, Agile meets Architecture Berlin 2023]
as the organisers put it
The conference encouraging conversation between practitioners of agile software development and architecture. Let’s find new ways for modern organizations!
| title | author | length |
|---|---|---|
| The Case for Technical Excellence | Kevlin Henney | 46m |
Argues that continuous technical excellence materially increases agility by lowering cost of change, and that technical debt is an effect caused by neglect… | ||
| Adaptive Socio-Technical Systems with Architecture for Flow | Susanne Kaiser | 43m |
Argues that combining Wardley Mapping, Domain-Driven Design and Team Topologies lets teams turn a monolithic “big ball of mud” into modular bounded contexts… | ||
| On Teaching and Learning | Aino Vonge Corry | 39m |
Explains how expertise follows the Dreyfus skill stages from novice to intuitive expert and why teaching accelerates mastery; cites a chess experiment where… | ||
| Software Architecture for Humans! | Eberhard Wolff | 45m |
Argues that architecture must match the people working on it, not just the dependency graph, and shows concrete fixes: run behavioral code analysis (who edits… | ||
| Practices from trenches for embracing evolutionary architecture in wild | Vivek Juneja | 40m |
Shows concrete practices: codify a decision matrix (fast vs slow) and FAQ, embed architecture-as-code and ADR templates into pull requests, and convert… | ||
| Sustainable architecture in an agile organisation | Nanna Lumholt Vangkilde | 41m |
EU CSRD forces mandatory sustainability reporting (first filings in 2025), data centers already emit ~2.5–3.7% of global CO2 and ICT could reach 14% by 2040… | ||
| From Domain Boundaries to Software Architecture | Maxime Sanglan-Charlier, Nick Tune | 39m |
Claims a repeatable path from messy monoliths to loosely coupled modules using Event Storming, Domain Message Flow Modelling, and the Bounded Context Canvas… | ||
| You don't talk about that at work. | Sophie Küster | 47m |
Personal account of diagnosed depression, anxiety and an eating disorder plus a later breast cancer diagnosis that shows therapy and meds help and that telling… | ||
| The Unbearable Stupidity of Social Sciences | Gerrit Beine | 43m |
Claims that software repeatedly reinvents century-old social science findings and misses contingency, using concrete models: Thorngate's G‑A‑S tradeoff and… | ||
| Agile and Architecture: a meeting of the undead | Einar W. Høst | 41m |
Argues that architecture was “murdered” by Agile and Agile in turn becomes ritualized, then diagnoses the real, persistent problem as change over time: code is… | ||
| Agile Coach meets Manager | Gitte Klitgaard | 43m |
Experience shows managers get promoted for craft, not people skills, and often lack training for difficult conversations, salary reviews and conflict… | ||
| Cloud computing and carbon emissions | Erik Doernenburg | 44m |
Explains measurable claims and tools: a reproduced methodology (now open source as Cloud Carbon Footprint) estimates cloud usage → kWh → CO2 using… | ||
| A puppy dies when agile meets reality | Luxshan Ratnaravi | 47m |
Weekly comic strips expose concrete anti‑patterns: keep 70% capacity not 100% commitment, never compare team velocities, treat knowledge sharing as an… | ||
| Let’s Stop Making Each Other Feel Stupid | Clare Sudbery | 49m |
Claims that gossip and jargon drive impostor syndrome and that withholding knowledge creates bottlenecks; recommends pair programming and ensemble work… | ||
| Modern Enterprise Architecture: architecting for outcomes "Modern Enterprise A..." | Simon Rohrer | 43m |
Claims that many legacy EA practices no longer work and proposes five concrete practices labeled ABCDE: continuous alignment (use Conway and reverse-Conway… | ||
| The Story of Knut - retrospective of an agile transformation in non-agile... | Pirita Johnsen | 35m |
A five‑year agile transformation inside a 70‑person IT organization moves a legacy Delphi app to Azure using Azure DevOps and a Scrum framework; teams… | ||
| Towards Architecture Organization Topologies for Sustainable Fast Flow of Change | Eduardo Da Silva | 45m |
Presents a concrete model called Architecture Organization Topologies and shows how one retailer moves from centralised “Ivory Tower” architects to enabling… | ||
| Fitness Functions for Your Architecture – in Practice | Thomas Much | 42m |
Concrete code examples use ArchUnit and jMolecules to encode fitness functions that assert module dependencies, layered ordering and absence of cycles. A live… | ||
| What is stopping us? A legacy code question | Lorraine Steyn | 41m |
Legacy code rot comes from systems not stupidity: management incentives, noisy environments, bad processes (example: a Jira board that spawns duplicates)… | ||
| Transforming ivory tower architecture to enabling teams | Michael Plöd | 39m |
Centralized architecture teams convert into enabling team roles by coaching stream-aligned squads, using Team Topologies as the framework, pairing and… | ||
| The monolith must die! - How to convince managers | Anja Kunkel | 40m |
Argues that Google DORA metrics (deployment frequency, lead time, change failure rate, time to restore) provide business-grade reasons to break parts out of a… | ||
| Cultivating Architecture in an Agile World | David Leitner | 41m |
Argues that teams choose distributed services mainly for autonomy, claiming about 80% ownership driver rather than modularization, and warns that availability… | ||
| Panel Discussion «Is it true that "The best architectures emerge from self-organized teams"»? | Clare Sudberry, Eduardo Da Silva, Vivek Juneja, Tim Ottinger | 52m |
Panel argues that architectures can and often do emerge from self‑organizing teams when teams experiment, share learnings and follow principles rather than… | ||
| From Software to Systems: Modern Agility | Diana Montalion | 36m |
Argues that agility scales only when teams shift from feature work to designing socio-technical systems and teaches five concrete practices: share expertise by… | ||
| Granularity and Communication in Microservice Architectures | Neal Ford | 44m |
Introduces the architecture quantum as a metric, gives five disintegrators (functionality, volatility, scalability, fault tolerance, security) and three… | ||
| nothing matches | ||