Refactoring organisations for flow

While building products, we introduce new silver bullets that promise to increase innovation and productivity. We see over-bloated "agile" frameworks or massive changes in architectural and data processing trends. Instead of focusing on the right problem and improving the value to our users, we chase new concepts that will solve these problems magically do it for us. Too often, we end up in silos, focusing too much on methodologies that are all but agile and adaptive, and we lose fine details without looking into a broader picture. There is a better way - to use well-proven and well-known tools.

To achieve that, we don't need to invent new frameworks. We can combine a lot of existing engineering concepts for business strategy (Wardley Mapping), product design and architecture (Domain-driven Design), and team interactions and organisation (Context Maps, DevOps and Team Topologies).

In this talk, we'll start with ways to identify the proper business boundaries and align our teams together with them. We'll see which ready-to-use engineering practices and tools we can utilise and how these affect and improve product engineering, data processing, and analytics teams. As a practitioner, I will share some real stories and leave you with excellent follow-up materials.