Most people introduced to Domain-Driven Design usually start with the first parts of the book, a very tactical approach treating DDD as a programming discipline. Then people begin discovering the architecture ideas in it, telling DDD is more than code. That is where they get introduced to the more strategic approach. But tactical vs strategic thinking can quickly turn into a polarity discussion where one is perceived as more important than the other. But with any polarity, both have up and down-side, you cannot do the one without the other. But when do we invest in one, and when into the other? Join us in this collaborative modelling session, where through dialogues we can discover signals when either strategy or tactical is not helpful anymore, and explore heuristics together to move to the other side, keeping the balance, doing tactical AND strategic design when we most need it!
The paradox or polarity between decentralised and centralised decision-making
When it comes to giving software teams the autonomy to make their own decisions, trust can be a delicate thing. This is particularly true when those decisions can have a wider impact on other teams and the overall system. If organizations are shifting towards...
