FLOWCON 2025

From Wild Bets to Solid Forecasts: Mastering Predictability

Tired of unreliable forecasts and missed deadlines? This workshop will show how managing the age of your WIP can stabilize cycle times and improve delivery predictability. Together, we'll tackle common forecasting pitfalls and uncover actionable ways to make your work more predictable.

Sum up the session in only 1 sentence
In this workshop, we’ll explore how controlling the age of work in progress can help teams improve predictability, avoid delays, and make more reliable forecasts.

What are the 3 top takeaways from your session or workshop?
Key Takeaways from My Workshop: 1. Controlling the age of work in progress (WIP) is the simplest, most effective way to improve predictability. By keeping WIP age in check, teams can reduce cycle times and avoid delays. 2. Predictability starts with improving single-item forecasting. Instead of guessing delivery dates for large groups of work, focus on accurately forecasting one item at a time. 3. Stable cycle times make forecasting easier and more reliable — for both single items and larger projects. By managing WIP age and stabilizing cycle times, teams can confidently make both short-term and long-term delivery predictions.

Painting the software green: A GreenOps approach!

In the fast-paced world of digital product development, the quest for sustainability is more than just painting the UI green or fighting for the efficiency of programming languages.

Green Ops merges sustainability principles with DevOps methodologies, emphasising efficient resource management, resilience, lifecycle sustainability, collaborative culture, and measurable impact.

It goes beyond superficial changes, focusing on optimising resource use, building resilient systems, and fostering a sustainability mindset throughout the development lifecycle. By embracing Green Ops, organisations can achieve better outcomes without overhauling their entire infrastructure, driving innovation while making a positive impact on the planet.

Sum up the session in only 1 sentence
The world can be a better place if you wish to, so start painting the software green!

What are the 3 top takeaways from your session or workshop?
1. Lifecycle Sustainability – Sustainability spans the entire product journey, from design to decommissioning. Every stage offers opportunities to reduce environmental impact and build long-lasting, efficient systems. 2. Code vs Operational Efficiency – Writing efficient code is just one piece of the puzzle. True sustainability comes from balancing optimised software with resource-efficient infrastructure and runtime environments. 3. Starting the Conversation– Change begins with awareness. Embedding sustainability into engineering discussions ensures it becomes a core consideration, driving greener decisions at every level.

DORA, Flux et Engagements : Le Cadre de Performance des Équipes Produits chez Cdiscount

Sum up the session in only 1 sentence
Engineering Value : Mesurer et Maximiser la Performance des Équipes Produit

What are the 3 top takeaways from your session or workshop?
L'importance de l'Engineering Value dans la performance des équipes produits Les outils et indicateurs pour mesurer la performance des équipes La fiabilité et la prédictibilité comme piliers du succès dans un environnement B2B

Impact Mapping Workshop

"Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and stakeholders visualise roadmaps, explain how deliverables connect to user needs and communicate how user outcomes relate to higher-level organisational goals." (source: https://www.impactmapping.org/)

Impact Mapping is a unique technique (described in a book by Gojko Adzic) which enables every organisation or team facing a new problem, a new challenge to not only find unexpected ideas but also to make sure that these ideas address those challenges instead of fulfilling other interests.
By following the steps, Impact Mapping helps find ways to experiment, innovate, and compare possible ideas by focusing on the outcome rather than the output. It gives the group the means to verify the progress the whole time - to fail fast or stop investing because they have reached their goal.

In this workshop, we will discuss and map a fictive problem. At the end of the workshop, you will know how the technique works and when to use it, how much fun such Impact Mapping can be and how creative people are when the only constraint is time :)

Sum up the session in only 1 sentence
We will learn how to analyse and manage to prove that our assumptions about the users' problems are correct before investing a lot of work in fixing the wrong problem.

What are the 3 top takeaways from your session or workshop?
1. The method is easy. The key is asking the right questions outside of our silo. 2. The right questions and the right metrics. 3. Assumptions are hindering, experiments are enabling.

L'entreprise, un terrain politique comme les autres ?

Sum up the session in only 1 sentence
Si l'entreprise était un sujet politique, lequel serait-elle ?

What are the 3 top takeaways from your session or workshop?
1) L'entreprise est un acteur politique, au sens où elle participe à l'organisation de la vie dans la cité 2) Les salariés de l'entreprise sont des citoyens qui ont des valeurs et des convictions 3) Les sujets politiques ne doivent pas être tabou, tout au contraire !

Title: Non-Blocking Continuous Code Reviews, a Case Study

The problem with the current most commonly accepted way of running code reviews using Pull Requests is that they have the nasty habit of blocking the flow of delivery. They introduce a cost of delay. Delays reduce feedback and drive down quality.

The usual way to achieve fast efficient and effective Continuous Code Reviews without disrupting the flow of delivery is through Pair Programming or Team Programming. However, for various valid reasons, these are often a cultural stretch for many teams and organisations.

In 2012, a novice team practising trunk-based development set up a fairly uncommon but efficient alternative to implementing continuous code reviews on mainline without ever blocking the flow of delivery. This team went from a bunch of rag-tags to becoming a reference team in the organisation, with auditors falling on the floor because of the amount of quality the team delivered.

Sum up the session in only 1 sentence
How to run code reviews with trunk-based development when pair programming is a cultural stretch?

What are the 3 top takeaways from your session or workshop?
Be able to explain how Pull Requests disable the benefits of Continuous Delivery. Be able to enumerate the key ideas behind non-blocking code reviews. Understand how non-blocking code reviews are an enabler for Continuous Delivery.

Dompter la Dette Technique : de fardeau à atout stratégique

La "dette technique" — on en entend parler partout, et nombreux sont ceux qui en subissent le poids. Mais soyons honnêtes : n’est-il pas temps d’arrêter de la voir comme un fardeau insurmontable ? Et si nous transformions ce concept souvent perçu négativement en un moteur de progrès ?

Dans cette session de 45 minutes, inspirée par la méthodologie concrète développée chez TheFork, nous plongerons dans les défis réels de la dette technique et vous montrerons comment la gérer sans perdre pied — ni ralentir l’élan de vos équipes.

Nous aborderons :

Ce qu’est réellement la dette technique (indice : ce n’est pas juste du vieux code que vous détestez).
Comment la localiser et la mesurer : Pas de jargon flou, juste des idées claires et actionnables.
Des façons concrètes d’agir : Des petites victoires avec la "Règle du scout" aux migrations complexes.
Les outils qui rendent tout ça possible : Automatisation, tableaux de bord, et même un bon vieux document Notion pour passer du chaos à la clarté.
Il ne s’agit pas de solutions miracles ou de théories abstraites, mais de faire face aux imperfections de votre système et d’en tirer le meilleur parti. Rejoignez-nous pour apprendre à affronter la dette technique, en faire un atout stratégique, et peut-être même commencer à apprécier le processus.








Sum up the session in only 1 sentence
Apprenez à transformer la dette technique, souvent perçue comme un obstacle, en un levier stratégique grâce à des outils pratiques, des méthodologies claires et une culture d'amélioration continue.

What are the 3 top takeaways from your session or workshop?
Redéfinir et mesurer la dette technique : comprendre que la dette technique est un choix stratégique et apprendre à la qualifier, quantifier et localiser pour en faire un atout exploitable. Adopter des outils et des pratiques efficaces : découvrir comment des outils comme Beacon, des tableaux de bord visuels, et des processus automatisés peuvent simplifier la gestion et la priorisation de la dette technique. Fédérer une culture d'amélioration continue : créer un environnement où équipes techniques et dirigeants collaborent pour intégrer la gestion de la dette technique dans la stratégie globale de l’entreprise.

Cf. Didier Girard

Sum up the session in only 1 sentence
cf. Didier Girard

What are the 3 top takeaways from your session or workshop?
cf. Didier Girard

Titre : Les standards de travail Lean/TWI pour développer l'autonomie et l'apprentissage

Résumé : Comment permettre à chacun de s'assurer que le travail réalisé est bon ou pas ? Comment donner les moyens à chacun d'être acteur dans l'amélioration du processus manipulé ? En utilisant les standards de travail !

Sum up the session in only 1 sentence
Redonner de l'autonomie aux personnes avec les standards de travail Lean / TWI.

What are the 3 top takeaways from your session or workshop?
- Le manque d'autonomie est un des risques psychosociaux - Le standard de travail permet à chacun de savoir si son travail est OK ou KO - Le standard de travail est la meilleure pratique d'une équipe à un moment donné

“If you hate OKRs, someone is doing them wrong. Maybe you, maybe your boss.” -Christina Wodtke.

Many organisations struggle with OKRs, often finding them frustrating and ineffective. But the problem isn’t the framework—it’s how it’s implemented. Cascading goals, task-focused execution, and rigid structures create silos and disengagement, stifling the true potential of OKRs.

In this talk, we’ll start by uncovering common dysfunctions that derail OKR initiatives and demystify why they fail to deliver results. Then, we’ll introduce a fresh, proven approach: the OKR Solar System. This dynamic model replaces top-down cascades with cross-team collaboration, enabling strategic alignment that adapts to your organisation’s evolving needs.

You’ll learn how the OKR Solar System fosters aligned autonomy, breaks down silos, and empowers teams to focus on shared outcomes. Real-world case studies will showcase its transformative impact on strategy execution. Whether you’re just starting with OKRs, scaling them, or looking for a reset, this session will inspire you to reimagine what’s possible.

Key Takeaways:

- Why cascading OKRs fails and how to avoid it.
- Introduction to the OKR Solar System with practical examples.
- Models for creating cross-team collaboration and strategic alignment.
- How to prevent or fix common OKR implementation challenges.

Let’s turn frustration into inspiration and make OKRs work for you!

Sum up the session in only 1 sentence
Why cascading OKRs fails, and how the Solar System can help you break silos, align strategically, and adapt dynamically.

What are the 3 top takeaways from your session or workshop?
- Why traditional OKR approaches often fail to deliver results.
- How to implement the OKR Solar System for strategic alignment.
- Practical models for fostering cross-team collaboration and innovation.