I see 2 layers, which should fit very well: a technical and a human component. DDD (the book, the theory i.e.) focuses mostly on the technical one but the whole transformation or product can fail if the human component is ignored or not focused enough.
I have some hints and hope to collect together with you a lot of others. The goal would be to have a list at the end which can be used as a guide for how to decide about BC boundaries when both aspects are taken into account. My other goal would be to find out, what can go wrong when the boundaries are wrongly chosen and how high would be the costs?
Question 1 for @Marco or @Kenny: are you moderating?
Question 2: what do you think about a "whiteboard", to visualize this list?
- feature branches: why are they needed? how often they block other features? how often they lead to merge conflicts?