Bruno Boucard
Empower IT teams to deliver products customers love
Donnez aux équipes IT les moyens de fournir des produits que les clients adorent
Paris, France
Actions
My long experience in IT has allowed me to design better collaborative approaches to create high-impact products.
Like the hummingbird, everyone does their part to create software that will better impact its users. By leveraging a domain-driven design approach, I facilitate more transparent communication between stakeholders and software creators through collaborative modeling and deep democracy, decoding complexities, resolving conflicts, and ensuring that software remains agile in the face of business demands.
As a consultant for OCTO Technology, a technical manager and software architect, and an agile and technical coach, I catalyze organizations and teams toward the design and construction of sustainable and clean software architectures.
Ma longue expérience en informatique m'a permis de concevoir de meilleures approches collaboratives pour créer des produits à fort impact.
Comme le colibri, chacun fait sa part pour créer un logiciel qui aura un meilleur impact sur ses utilisateurs. En tirant parti d'une approche de conception axée sur le domaine, je facilite une communication plus transparente entre les parties prenantes et les créateurs de logiciels grâce à une modélisation collaborative et une démocratie profonde, décodant les complexités, résolvant les conflits et garantissant que les logiciels restent agiles face aux demandes de l'entreprise.
Dans mes rôles de consultant pour OCTO Technology, responsable technique et architecte logiciel, et coach agile et technique, je catalyse les organisations et les équipes vers la conception et la construction d'architectures logicielles durables et résilientes.
Links
Area of Expertise
Topics
Trivialization of DDD or not?
Many developers consider Domain Driven Design (DDD) the most essential element of DDD (aggregate, entity value object, etc.). But what about modeling oriented toward the business domain?
How to model a complex problem without getting lost in the complexity of the code.
After reviewing approaches to understanding the problem space, we'll dive into the art of DDD modeling at the code level. Domain-driven Design is not a treat but an approach to modeling the heart of a product that aligns with the expectations of experts in the field.
I'll make sure to remember the techniques for understanding the problem space before introducing you to the deep modeling approach at the code level: Model-Driven Design.
Deep Dive into Model-Driven Design: Refining Domain Models in Code
Most software products begin with an initial software model that is typically naive and superficial, grounded in basic understanding. This initial phase is natural, aligning with the early stages of discovering and exploring a new product with stakeholders. Initially, the process involves identifying nouns and verbs to create our code's first objects and methods. While this early model enables quick feedback for the product, it often becomes less effective over time. As more feedback is gathered, the model usually needs to accurately reflect the main concerns of domain experts, becoming less relevant for the product's development. The absence of a model that mirrors the domain's core aspects can prevent adjustments to the code based on changing stakeholder needs, potentially blocking product innovations. Additionally, the gap between the code and the domain model leads to missed opportunities for insights, as the code no longer represents our domain knowledge accurately.
Join us in this hands-on modeling and coding session focused on the significance of continuously refining your core domain models in code. We will introduce you to the context by guiding you through collaborative modeling techniques such as Eventstorming, Domain Storytelling, Context Mapping, CRC cards, and more. Dive into coding challenges using C# and Java, where you'll witness firsthand the transformative power of supple design and a deeper model. You'll understand how continuously refactoring the model can drive product development breakthroughs by the end. Whether you prefer pairing or ensemble programming, you'll depart with enriched practical insights and a kickstart into Deep Diving into Part III of Evans’s groundbreaking work on Domain-Driven Design (DDD), specifically designed for those looking to advance beyond basic concepts like aggregates, entities, and value objects.
Deep Dive into Model-Driven Design: Refining Domain Models in Code
Most software products begin with an initial software model that is typically naive and superficial, grounded in basic understanding. This initial phase is natural, aligning with the early stages of discovering and exploring a new product with stakeholders. Initially, the process involves identifying nouns and verbs to create our code's first objects and methods. While this early model enables quick feedback for the product, it often becomes less effective over time. As more feedback is gathered, the model usually needs to accurately reflect the main concerns of domain experts, becoming less relevant for the product's development. The absence of a model that mirrors the domain's core aspects can prevent adjustments to the code based on changing stakeholder needs, potentially blocking product innovations. Additionally, the gap between the code and the domain model leads to missed opportunities for insights, as the code no longer represents our domain knowledge accurately.
We would like to join you in this live coding talk session focused on continuously refining your core domain models in code. We will introduce you to the context by guiding you through collaborative modeling techniques such as Eventstorming, Domain Storytelling, Context Mapping, CRC cards, and more. We then dive into coding challenges using C#, where you'll witness firsthand the transformative power of supple design and a deeper model. You'll understand how continuously refactoring the model can drive product development breakthroughs by the end. You'll depart with enriched practical insights and a Deep Dive of Part III of Evans’s groundbreaking work on Domain-Driven Design (DDD) that goes beyond basic concepts like aggregates, entities, and value objects.
Deep Dive into Model-Driven Design: Refining Domain Models in Code
Most software products begin with an initial software model that is typically naive and superficial, grounded in basic understanding. This initial phase is natural, aligning with the early stages of discovering and exploring a new product with stakeholders. Initially, the process involves identifying nouns and verbs to create our code's first objects and methods. While this early model enables quick feedback for the product, it often becomes less effective over time. As more feedback is gathered, the model usually needs to accurately reflect the main concerns of domain experts, becoming less relevant for the product's development. The absence of a model that mirrors the domain's core aspects can prevent adjustments to the code based on changing stakeholder needs, potentially blocking product innovations. Additionally, the gap between the code and the domain model leads to missed opportunities for insights, as the code no longer represents our domain knowledge accurately.
We would like to join you in this hands-on modeling and coding session focused on continuously refining your core domain models in code. We will introduce you to the context by guiding you through collaborative modeling techniques such as Eventstorming, Domain Storytelling, Context Mapping, CRC cards, and more. Dive into coding challenges using C# and Java, where you'll witness firsthand the transformative power of supple design and a deeper model. You'll understand how continuously refactoring the model can drive product development breakthroughs by the end. Whether you prefer pairing or ensemble programming, you'll depart with enriched practical insights and a kickstart into Deep Diving into Part III of Evans’s groundbreaking work on Domain-Driven Design (DDD), specifically designed for those looking to advance beyond basic concepts like aggregates, entities, and value objects.
Le Continuous Discovery est-il l’avenir du Continuous Delivery ?
Depuis une vingtaine d'années, le Continuous Delivery a terriblement évolué.
Consciente de cette accélération, la communauté Product Management propose de s’aligner sur les principes du Continuous Delivery avec une nouvelle approche, le Continuous Discovery.
Nous plongerons dans cette nouvelle approche orientée Produit, qui repose à la fois sur une organisation spécifique, un rythme soutenu et un atelier autour d’un arbre visuel permettant de passer de l’espace du problème à l’espace de la solution.
Le Continuous Discovery n’est pas décorrélé de l’équipe de développement, mais en fait partie.
L’objectif est limpide : permettre aux équipes de développement de délivrer encore plus vite des besoins du métier calibrés avec soin pour un impact maximum auprès des utilisateurs.
Bruno Boucard
Empower IT teams to deliver products customers love
Paris, France
Links
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top