FLOWCON 2022

L'Event Storming est un atelier permettant de modéliser les domaines métier présents dans une application, voire même une entreprise au global. Cet atelier permet d'aligner le langage et les concepts d'une équipe entière autour de ces concepts métiers. Nous utiliserons les différents éléments de l'event storming, autour d'un sujet simple mais pas simpliste, qui permettra d'utiliser toutes les techniques présentées par Alberto Brandolini dans son livre.

(This is a hands-on lab with limited capacity)
Level: advanced
Max attendees: 20 in one room

"It is not the domain experts knowledge that goes into production; it is the assumption of the developers that goes into production". This famous quote from Alberto Brandolini is very accurate, and it points in the right direction: we need to bring domain knowledge into our decisions and our software to offer the best solution in the given context.

One of the reasons why software solutions become messy and hard to maintain is that we tend to jump to solutions before really understanding the problem. They may work out for now, but how do we ensure that they will fit in the future? This is where the paradigm of Domain-driven Design can help us out: DDD gives us the option to change our model when the business is changing. The workshop is not only for engineers but for everyone involved in product development.

In these two hours, we will dissect a business problem and experience how to solve it by using various techniques and tools in the day-to-day business. We will learn how to ensure that our decisions and implementations are driven by the Domain, which pitfalls to avoid and which principles to follow. After the workshop, every participant should have a good idea of how to start using the techniques and tools at work.

Venez apprendre la véritable recette du welsh du Nord et en (re)découvrant Kanban et accelerate

When we build products, we always strive to have a steady flow through our software lifecycle. One key aspect coming from Domain-Driven Design is that we must base our communication during that software lifecycle on a ubiquitous language. A language designed and used around a domain model to communicate and explore requirements with stakeholders and domain experts and what the code is based on. But how can we collaboratively design that domain model with a ubiquitous language that we can represent in our code base?

Join us in this hands-on workshop where we will provide the outcome of an EventStorming session and dive deeper to design our domain model. We will use Example Mapping to flush out all our acceptance criteria and business rules. With these rules, we can start designing our domain model, and we will do that with responsibility mapping. Responsibility mapping is based on CRC cards and will make us collaboratively design a Domain Model. You will leave the session with collaborative modeling techniques that will help you design and maintain a ubiquitous language for implementing software.

Ever wondered why sometimes you feel like you are getting a lot of work done, but still your customers and stakeholders aren't happy?
Why is it that, even if your team is awesomely agile, people still complain about how long it takes to get their stuff done?
It feels like no matter how hard you work, no matter how busy you are, people are never satisfied.
What's going on?
In this practical session Jose Casal show how when we visualise our waitflows, we can start improving the flow of work to our customers.

Join Daniel and Jose in a session running TWiG, the Kanban simulation engine. Experience Kanban in action and the power of using Flow Metrics. Participants need to bring laptops to the session.