ddd-crew / core-domain-charts

A tool for collaboratively finding your core domains - strategic business differentiators
Creative Commons Attribution Share Alike 4.0 International
526 stars 38 forks source link

Basic advice for measuring complexity and differ. #19

Closed NTCoding closed 2 years ago

NTCoding commented 2 years ago

A common question I get is how to measure the complexity and differentiation of domains in order to visualize them on a core domain chart. So I've shared my basic list of clues here.

yellowbrickc commented 2 years ago

I have another question for you all, unrelated but triggered by this PR: I have never used this chart at work. Did you and in what context?

NTCoding commented 2 years ago

I have another question for you all, unrelated but triggered by this PR: I have never used this chart at work. Did you and in what context?

I'm using this with most of my clients these days. Yesterday I had a call with a new client and they already had a core domain chart they wanted to share and get my feedback on.

The most common use case is to map out the domain landscape and decide where to focus, what to do next, where I might be able to help.

Some of the examples in this post are based on work with real clients https://medium.com/nick-tune-tech-strategy-blog/turning-domain-discovery-into-product-and-organizational-improvements-with-a-ddd-exemplar-9e759c365a9e

Max-Git commented 2 years ago

I like this list and all the improvements/fixes made by @emgsilva and @yellowbrickc 👍 I'd also add in the organizational indicators of complexity something like "How long would it take for a newcomer to ramp up and be efficient?" but that might sound like redundant with the latest indicator in the list 🤔

Max-Git commented 2 years ago

@yellowbrickc I'm also using this chart with my clients. It really helps to focus on what's important. It's quite helpful when you want to refine the scope of an MVP or take build vs buy vs outsource decisions. It also been very helpful for one of my clients that wanted to rewrite his platform. The as-is architecture was not aligned with business and what they had identified as core domains, were actually technical stuff. When we identified new sub-domains, aligned with business, it became obvious that some of those were the real core domains. We used the chart to visualize that the old ones were moving from core to support and new ones were core. Visualising it helped them a lot to change their minds.

NTCoding commented 2 years ago

How long would it take for a newcomer to ramp up and be efficient?

I think it's a great addition. Added.