Olivier Jauze

Olivier is a Senior Fellow at Michelin with almost 20 years of experience in software engineering and architecture. Passionate in finding solutions to users’ problems with technology, Olivier coaches teams in their journey to deliver incredible products and for a couple of years now platforms too. Involved in many initiatives around Michelin core business, he is also working in the service & solution and consumer experience areas. Recognized as a disrupter, he’s continuously pushing organizations to adopt new business models and new ways of working. Recently he worked on an open source project to help software architect dealing with the continuous nature of today’s software delivery.

Architecture for flow case study

A case study from the industry to see how Domain Driven Design & Team topologies can be used to architect for fast flow

Using our Miro templates

Download the latest release of the miro board you want to use. As of now, we provide: Team Topologies Miro template Event storming Open Miro and click on Upload from backup. This will create a new board called Restored SOMETHING Then simply rename the board and start using it by copy and pasting the different shapes as required Making changes to the Miro templates and share it You are absolutely free to change our board to make it more useful in your context. If you want to share those templates, there are several ways to share templates in Miro

Start your journey

Start your journey The deployment of the new ways of working (practices, rituals, framework) described in the Continuous Architecture Framework and Toolbox is a major change journey. There is no single pathway to move your enterprise (or part of it) from its current state to the ideal state (or north star) we recommend and which is embodied in the key tenets of the Continuous Architecture Manifesto - edition 1.

Order to cash domain

Context and background Several years ago, we revisited our information system supporting order to cash processes. We used to have a legacy monolith (hosted on a mainframe) and supporting most of these processes. We decided to adopt a best of breed approach: several solutions were implemented to support the different part of these end to end processes: from order capture to transportation optimization up to logistic delivery … This move, helped us to

Re-architecture our curing solution

Domain Driven Design is set of concepts and practices aiming to align the structure and language of the software code with the business domain the code is supporting. It was popularized by Eric Evans and gets lots of traction in the last couple of years. One of the main difficuties when you’re trying to adopt DDD to model and design your solution is “Where the hell should I start from?”