Dear CoMo - Collaborative Software Design

Collaboration, by nature, is about working with others, which means we bring our whole selves to the table—not just our technical skills. Often, the biggest challenges in collaborative software design aren't technical, they are human. In this video from @amaconf.bsky.social -->

These 'shadows' are a natural part of any group dynamic and can significantly affect how we work together. What are some of the hidden challenges you've encountered in your own collaborative sessions?

Collaboration, by nature, is about working with others, which means we bring our whole selves to the table—not just our technical skills. Often, the biggest challenges in collaborative software design aren't technical, they are human. In this video from @amaconf.bsky.social -->

@evelynvankelle.bsky.social and @kenny.weave-it.org discuss how a lot of what's going on in a team is like the unseen part of an iceberg. We only see the surface—the ideas being shared—but beneath the waterline are individual perceptions, emotions, and disagreements.

Software development isn’t just about writing code; it’s about understanding the problem you're solving. A while ago @gienverschatse.com and @kenny.weave-it.org went on the Software Testing Unleashed podcast, hosted by @richard-seidl.com.

We discussed why we need to move away from rigid handoffs and embrace a more collaborative approach. The conversation explored how to build a shared understanding across teams, which ultimately leads to better outcomes and a healthier work environment.

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

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

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

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

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

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

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 ....

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 ...

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 ....

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.

"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.

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?

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?

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12

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

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/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

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12

> Similarly, give consideration to structuring your bounded context based on the existing departments or teams within your organisation. Their defined responsibilities and areas of expertise can frequently mirror logical divisions within the models. 7/12

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12

past experiences to address common design dilemmas. Here are a few examples of these helpful guiding principles that can illuminate your design path: 5/12

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12

Now, I can almost hear your concerns echoing across the digital waves: won't relying on these so-called "shortcuts" compromise the quality of our work? Rest assured, dear friend, that employing design heuristics doesn’t inherently lead to inferior results compared to 3/12

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12