1/ I'm doing some reflection on how #DDD can help you spot a Platform as a Product Team from @TeamTopologies wrongly applied 
2/ Indeed, I think we created a Platform Team because the intention was to reduce cognitive load on teams on a specific part.
BUT, on the recent learnings, we think it might be a Bounded Context by itself, a Supporting Subdomain at least.
BUT, on the recent learnings, we think it might be a Bounded Context by itself, a Supporting Subdomain at least.
3/ This is one of the cases in which using different perspectives to the same problem space helps you find the best team composition.
4/ What helped us identify this scenario has been using Big Picture Event Storming to boost fast learnings about the tribe identifying new _business capabilities.
A missed knowledge about the domain we are working on, and an important one.
A missed knowledge about the domain we are working on, and an important one.
5/ What's interesting is that, at first, it seemed to be an effort to reduce cognitive load, it evolved into a supporting business capacity that shares trades of Platform as a Product AND a supporting bounded context. BOTH!
6/ More to be explained when I figure this out!
7/ As always, involving Business and doing some discovery together can help you on learning that sooner when the decision was made.
Yet, we learned about the Business Domain and we understood better the situation.
Identifying Bounded Context is still the challenge
Yet, we learned about the Business Domain and we understood better the situation.
Identifying Bounded Context is still the challenge
8/ I have been able to identify that we were applying the Platform as Product approach because of Strategic M&M from @VaughnVernon and @tjaskula
In chapter 2 talks about business capabilities, focusing on _What_ business does
goodreads.com/book/show/5947…
In chapter 2 talks about business capabilities, focusing on _What_ business does
goodreads.com/book/show/5947…
@VaughnVernon @tjaskula 9/ It triggered a thought of... we didn't explore beyond the Stream-Aligned Teams Bounded Contexts...
Are we reducing the cognitive load on them... or they are actually developing two different bounded contexts. One _Core_ and the other _Supportive_?
Are we reducing the cognitive load on them... or they are actually developing two different bounded contexts. One _Core_ and the other _Supportive_?
@VaughnVernon @tjaskula 10/ Damn right. Looks like the second team started with the hypothesis of reducing the cognitive load as Platform Team but the reality is that they are just handling the _Supportive Bounded Context_.
I don't know which TT type they are. But looks like they aren't Platform.
I don't know which TT type they are. But looks like they aren't Platform.
11/ My take is:
Platform Team to reduce cognitive load as part of a Bounded Context can hide a Supportive Bounded Context that should be addressed properly.
Here Stream-Aligned Team with Context Mapping can serve better.
Use each approach properly 😄
Platform Team to reduce cognitive load as part of a Bounded Context can hide a Supportive Bounded Context that should be addressed properly.
Here Stream-Aligned Team with Context Mapping can serve better.
Use each approach properly 😄
• • •
Missing some Tweet in this thread? You can try to
force a refresh
