For many years, the waterfall model was the standard way of developing software. Engineering teams could spend months or even years on the architecture of a new project, before even a single line of code was written. Nowadays we know that this approach is flawed, and working in small iterations and continuous delivery have become the norm. But does that mean that we should just skip making architecture decisions altogether? Of course not!

In this talk we will look at how the Agile Manifesto and the principles behind it actually promote the making of conscious architectural decisions, and how we can include architecture in our software development process while avoiding Big Design Up Front. We will look at practical tools such as Architectural Decision Records which will help to make architecture decisions in a structured way, and document them so that we will still remember the reasoning behind them in a few years from now.

So join me in this talk to find out how you can make good architectural decisions that allow you to deal with changing requirements, while delivering working software to your customers as early as possible!


Please login to leave a comment

Really nice talk with some good insights.
Maybe could do with a bit shorter intro in order to get the solutions faster and with more detail.

Bas de Ruiter at 13:58 on 15 Mar 2024

Dit praatje kwam op een heel mooi moment. Ik ben net in de situatie 's war ik dit nodig heb. Je bent een goede, relaxte spreker die duidelijk weet waar die het over heeft.
Omdat je erom vroeg heb ik nagedacht over verbeterpunten
De uitleg van waterfall aan het begin hoeft misschien niet zo uitgebreid. Ook zou een extra voorbeeld waar je agile moest zijn met je architectuur dat onderdeel mogelijk iets meer verduidelijken.

Tim Hofman at 14:15 on 15 Mar 2024

Very clear talk with one specific goal. And I'm nspired to talk to my team if we could use ADR's in our codebase.

Ivan Herak at 17:08 on 15 Mar 2024

Great and useful - stuff that can be easily applied in the real world. Love stuff like that in a talk.

Airton Zanon at 12:26 on 17 Mar 2024

Loved the way that Nic delivered the content, he used story telling and practical ways of implementing how to keep architectural decisions for the future people that will touch the project and how to be a good technical leader.