Here are takeaways of everything we wrote about Remote Event Storming: Why go remote, 7 essential practices, step-by-step preparation, leveraging the time between sessions, and making it fun and produ...

Tired of passive attendees and multitasking during remote Event Storming? Discover how to transform virtual workshops into high-energy experiences. We cover breakout room roles, ‘remote-first hubs’, a...

Learn how to make the most of breaks in remote Event Storming sessions. Discover practical tips for facilitators and participants to boost engagement, adapt on the fly, and improve outcomes between se...

Having a badass developer onboard will help to get sponsorship for a large scale refactoring. If you don’t have a badass developer nearby, or / and if you want to become one yourself, read on. Here are a five mistakes to avoid in order to become a badass developer.

A collection of side projects best practices I learned from past experience

Event Storming and DDD are great at identifying bounded contexts. It’s even more valuable to identify the core contexts to focus on, and the generic ones to buy. This activity will help your team to prioritize more valuable work, and to reduce maintenance by choosing the good software to build or buy.

Event Storming is a group design activity that uses a lot of post its. Unfortunately, post-its are not for every culture! After going through why post-its work, we’ll go over 2 alternatives: homework & feedback and walking skeleton. Could we also use these techniques to complement Event Storming?

As software people, we live in a complex-system world. To leverage on its non-linear effects, we need to multiply weird experiments. Here is the story of how our hacked-up fruit basket at work contributed to exploratory testing, a #zeroBugs policy and eventually increased productivity by 25%.

Although incredibly effective, DDD is overlooked by developers because of its abstractness. Here is a set of hacks to introduce DDD during an Event Storming workshop. Ex: Alternatives to convoluted DDD names, Group activities to pass a concept through, Presentation material for tricky notions

What would eXtreme Programming look like if it was invented today ?

After going over the typical problems in large scale Agile transformations, I add transparency of vision and information to the pre-requisite

Injecting DDD or Event Storming in your organization can be tricky. Here are some techniques to onboard your domain experts, one step at a time! 1st: practice on your side. 2nd: build trust with the cheaper example mapping.

Full-time pair programming is awesome, except that it burns introverts out. Part-time mob programming yields the same benefits but is sustainable. Plus, it is easier to sell to management, works great for remote teams and supports diversity! How to start mob programming? Try a few coding dojos!

Software is mostly built according to experts opinions. These 7 data driven software engineering books show us another way to a productive and sustainable pace. Ex: measuring the impact of a feature on the bottom line, forecasting the impact of a refactoring on the bottom line, etc.

The story of our culture book and how it emerged from disparate documents

The problems I got into on a side project after using too much mocking. This is the first post of a series about how to avoid mocks.

The story of how I discovered Design by Contracts, and how my use of it changed through time

Ideas about how to push your team coding dojo further in order to improve teamwork and production code.

What would eXtreme Programming look like if it was invented today ?

Things to do to become better at code refactoring

An explanation of why large systems tend to favor the emergence of mocks and what Hexagonal Architecture can do against that. Illustrated with Ruby on Rails code examples.

A study on the practice of throwing code away, and of how and when it could be made to work

Understanding is key to building quality software. In this guest post, fluentcpp blogger Jonathan Boccara presents 3 levels of understanding we should go through before we start coding. #1 Why something doesn’t work. #2 Why something works. #3 Why you do this project of feature.

Inverting your Kanban board columns is a cheap way to reduce multitasking and stress. Eventually, it contributes to a more sustainable pace. By adapting Kanban boards setup to our culture, we can make them highlight what can be finished instead of what can be started!

A DIY yourself workshop to quickly train your team on Event Storming and the Delegated Missions.

Identify events on stickies to make sure they happen as you wish. This is what event storming is about. Read this post and get an overview of the technique and its benefits.

Learn how to make the most of breaks in remote Event Storming sessions. Discover practical tips for facilitators and participants to boost engagement, adapt on the fly, and improve outcomes between sessions.

Mob programming with a team is a great way to do technical agile coaching. Unfortunately, a dysfunctional mob makes coaching impossible! Getting a team to mob correctly is a challenge of its own! So here is a workshop for team members to try and find the mob programming rules that work for them.

Infographic showing how Scrum with component teams is not sustainable. Interdependent component teams + Scrum => Painful integration => Request for better specifications => More time specifying => Later Delivery & More Big Design Up Front => Waterfall Agile => Painful integration…

An explanation of how immutable value objects helps developers to remote mocks from their tests

A walkthrough of a few strategies that can be used right now to get your team to do regular code reviews

Running a DDD Design-Level Event Storming is easy. Running a great one is hard! This post is here to help you. It contains facilitation tricks to maximize the return on invested time. It also details workshop-closing activities to decide what to do next.

The story of how my team came to do remote energizers the way they do them, and tips for your remote energizers

Getting all the team to code review can be a real challenge. Here is the story of how a simple random review assigning tool nudged everyone to code review. It’s also a story of continuous improvement. From painful manual code reviews to shared reviews to eventually synchronous pair programming.

Big Picture Event Storming and DDD let us build a shared architecture vision. By mixing in incremental refactoring techniques, we can realize the vision through evolutionary architecture and emergent design. This enables early delivery of features, without sacrificing the long term architecture.

Discussion over different flavors of TDD and in what situation they are best suited

An introduction to ‘complexity_assert’, an experimental ruby open source unit testing gem that I wrote, which uses linear regression asserts the complexity of an algorithm

A walk through of the Fizz Buzz kata using immutable value objects to remove mocks.

The story of how I learned TDD, and advises for the aspiring TDD apprentice

A fiction about how developer Joe managed to keep programming while he became a manager

After a Big Picture Event Storming, you can use its Design-Level cousin to dive into an important bounded context. Use Design-Level Event Storming to identify Aggregates, UX mockups, and other design elements. Just follow this agenda through your first facilitation!

Here are 7 things to do before you run your remote Event Storming: get the right tool, find a co-facilitator, book the sessions, prepare the board, rehearse, send invites, and run a “get-ready” session. Follow these steps to set your workshop up for success!

Here are step by step adaptations for a remote Event Storming. Events Generation, Sorting, Actors and External Systems, Storytelling, and beyond: you will find what to change to make each step work like a charm.

Here are step by step adaptations for a remote Event Storming. Events Generation, Sorting, Actors and External Systems, Storytelling, and beyond: you will find what to change to make each step work…

This post reveals a practical method to simplify complex workflows by counting the links between variables. Discover how to pinpoint the most influential factors and focus your actions for maximum impact, making your workflow smoother and more efficient.

Turn your workflow insights into real progress! This post shows how to pick key areas to improve, create simple, clear actions, and follow up to see results. Learn how small steps can lead to big, lasting changes in how your team works.

Here are 7 key practices for remote Event Storming: short sessions, breakout rooms, collaboration roles, silent sorting, clean board, rehearse practice, and co-faciliation. These practices increase delegation, reduce fatigue, improve documentation, and boost autonomy for any workshop.

Discover the surprising benefits of running Event Storming remotely! Save time, cut costs, and boost inclusivity while achieving great results. Also meet unexpected benefits like: leveraging digital tools, fostering deep thinking, and improving facilitation skills.

This post reveals a practical method to simplify complex workflows by counting the links between variables. Discover how to pinpoint the most influential factors and focus your actions for maximum impact, making your workflow smoother and more efficient.

Turn your workflow insights into real progress! This post shows how to pick key areas to improve, create simple, clear actions, and follow up to see results. Learn how small steps can lead to big, lasting changes in how your team works.