Have you ever faced difficulties during sprint refinement, trying to get on the same page with your team? Perhaps, after implementing a solution, it turned out that it should look a bit different?

If any of these situations have occurred, or if you're wondering how to define the scope of work without getting too technical, Event Storming might be a great fit for you. Whether you're new to the domain or just need some alignment, the "Big Picture" type of workshop is a valuable tool I've used on several occasions, making my job a lot easier. However, while the high-level overview provides clarity, it lacks the necessary details for implementation. In this blog post series, I'll guide you through conducting such a session, enabling you to translate Event Storming output into your codebase.