Introduction to ADRs

In software projects, it's important to write down why we make certain big decisions about how the software is built. These written records are called Architecture Decision Records (ADRs). They help us remember why we made these choices, especially when new team members join or when we need to make future decisions. This talk will introduce ADRs and explain why they are so useful. We will cover what ADRs are, why we need them, and how they help teams work better together. This is great for anyone who wants to keep track of important decisions in a simple and organized way. Join me to learn how ADRs can make your software projects smoother and more successful.

Accelerate learning with Event Storming

Product owners and domain experts are the ones who possess the knowledge necessary for the team to achieve your goals. However, spreading that knowledge from a few people effectively is a big challenge with direct impact upon the quality of the product or service, as well as the timeline of delivery. Event storming is one of the techniques that address the challenge. In this presentation, I’ll explain how it works, how to use different colours and how it helps to eliminate the knowledge gap.

One Does Not Simply Make Architecture Decisions Alone

Architecture is more than just diagrams. It is a set of important decisions. Many teams struggle with how to make these choices without a single "architect" becoming a bottleneck. This talk introduces the Architecture Advice Process. It is a simple way to let anyone make a decision as long as they seek advice from the right people. We will look at how to use Architecture Decision Records (ADRs) to document the "why" and keep everyone on the same page. Join me to learn how to give your team more autonomy while keeping your system's design clear and consistent.

Target audience: anyone who makes or wants to make architectural decisions.