Dear CoMo - Collaborative Software Design

It's a common aspiration, Collaborative software design leading to wonderfully autonomous teams and truly decentralized decisions. Yet, the reality, as ‪@evelynvankelle.bsky.social‬ and ‪@kenny.weave-it.org‬ so thoughtfully discussed at Fast Flow Conf NL, central decisions don't just disappear.

The idea of collaborative modeling flourishing within a company is something many of us strive for. But is it a guaranteed success, and where do you even begin to plant those seeds?

Watch and listen to ‪@gienverschatse.com‬ and ‪@evelynvankelle.bsky.social‬ as they explore these very questions.

If these challenges resonate with your own experience and you're ready to embark on this journey yourself, we invite you to explore our website! - 7/7
collaborative-software-design.com

While two days was just the beginning of their journey, it undeniably sparked the right conversations and forged a shared understanding, empowering them to continue on their own. - 6/7

smaller groups to brainstorm ideal future models. We wrapped up with a 'pro, con, fix' walk-by, not just to highlight differences, but to uncover those crucial similarities – the golden threads that can help untangle a 'Big Ball of Mud' and start extracting those much-needed boundaries. - 5/7

Well, that's when the value diminishes and the correctness of the software itself becomes suspect, making every change a Herculean effort and dragging down your time to market. Sound familiar? Our workshop kicked off with a full day of Big Picture EventStorming, then shifted to - 4/7

Communication becomes a muddled mess, slowing down vital refinements and leaving everyone scratching their heads. And when the design doesn't truly reflect the domain model? - 3/7

They spent two intense days with 24 engineers and stakeholders, guiding them through the labyrinth of domain modeling.

You see, without those well-defined boundaries, engineers often shoulder an immense cognitive load. - 2/7

Oh, the tangled web we weave when our software domains lack clear boundaries! Last week, our brilliant authors, ‪@gienverschatse.com‬ and ‪@kenny.weave-it.org‬ , tackled this very predicament head-on. - 1/6

Dear CoMo, My Team Clings to Their Ideas – Help!

Well, well, well, isn't that a familiar feeling? Collaborative modelling should be a place where brilliant minds come together, stickies fly, and shared understanding *should* blossom.. Read more : collaborative-software-design.com/dear-como/te...

collaborative software design, drawing right from their book. It sounds like an incredibly rewarding few days for them!

For anyone interested, I'd gently suggest keeping an eye out for the conference recordings once they're released. There's bound to be plenty of food for thought in there.

extended an invitation for a Team Topologies panel alongside the very bright @lina-plummer.bsky.social, @simon.bvssh.com, Carola Lilienthal, @esilva.net and facilitated by @bitboss.bsky.social . Plus, our authors got to share their passion and knowledge during a talk on ...

lovely mix of humility and sheer excitement bubbling underneath. For one of them, it was even the fulfillment of a long-held childhood dream – isn't that something?

We're so grateful to the wonderful team at Agile Meets Architecture who made this happen. And as if that weren't enough, they also ...

Sometimes you just have to share a bit of good news that makes you smile. Picture this: the bustling @amaconf.bsky.social conference, and right there, our own authors are hosting a book signing session. A real pinch-me moment! While they managed a calm exterior, I can tell you there was a ....

If we leave the judging to the cats, how can we address the shadows in collaborative modelling sessions? My authors were recently asked that question at the Agile Meets Architecture conference, where they talked about the book.

Read the answer here: collaborative-software-design.com/dear-como/le...

Dear CoMo, Why does my colleague never contradict me?

It sounds like your colleague might be dealing with a classic case of conflict avoidance. Now, don’t get me wrong—I don’t say that to be unkind. Read all about it at the latest Dear CoMo collaborative-software-design.com/dear-como/co...

Stop treating software design decisions like they're written in stone! There's no real 'point of no return.'

You can always change your mind later. The key is having tight feedback loops to spot a wrong turn ASAP and adapt quickly, before the cost balloons. Design isn't static, neither is context.

There has been a focus on autonomy in information technology, From autonomy in code, autonomy while coding, and autonomous systems with microservices to auto... Autonomy, is that what we really want?

Chec-out the full video here: www.youtube.com/watch?v=Q9-L...

Hot take maybe? Architects swapping between Enablement and Platform teams seems like a smart move. They learn the real-world collaboration stuff with Enablement, then build platform tools that don't force teams into awkward workflows for sharing architecture. Just build it the way teams need it.

There has been a focus on autonomy in information technology, From autonomy in code, autonomy while coding, and autonomous systems with microservices to auto... Autonomy, is that what we really want?

Design it together through collaborative modelling!

Check-out the full talk here:
www.youtube.com/watch?v=Q9-L...

"Autonomy" is basically just a container concept we throw around. So, can we stop telling teams to simply "be autonomous"?

It means something different to everyone! Real autonomy needs clear boundaries and context defined for specific teams/situations. Otherwise, you're just inviting confusion.

In the morning, you’ll have the opportunity to have your book signed, and in the afternoon, you can attend their talk to understand more about collaborative software design and how to facilitate domain modeling decisions.

What behaviours are you actually observing? Because sometimes, what appears to be resistance is merely a desire for clarification or a different approach.

Why not join Evelyn and Kenny at Agile Meets Architecture today?

It’s a common scenario in the world of architecture—decisions are made, and suddenly, you find yourself facing a wall of resistance. But let’s pause for a moment. Are your colleagues truly resisting the decision, or could it be that your own assumptions are clouding your judgment?

And for a web-friendly version see wirfs-brock.com/rebecca/pape...

Check-out @rebeccawb.bsky.social her paper called Traces, tracks, trails, and paths: An Exploration of How We Approach Software Design: wirfs-brock.com/PDFs/Traces,...

By embracing and applying design heuristics, you can gain significant guidance, make more informed decisions, and ultimately steer your team towards more effective and sustainable software architecture. 11/12

This practice will enable you to refine your existing heuristics and cultivate new ones over time, effectively building your own invaluable toolkit of design wisdom.

So, dear reader, please don't feel overwhelmed by the intricate nature of software design. 10/12

It's crucial to recognise, my dear, that your personal collection of heuristics will be unique to you, shaped by your individual experiences, observations, and acquired knowledge. It can be immensely beneficial to maintain a record of your insights and reflections following each design session. 9/12

These heuristics can prove particularly valuable when defining bounded contexts, which are specific areas within your software where a particular model and vocabulary are consistently applied and understood.
8/12