Well, well, well, job description woes? Who needs permission to model effectively? Master Secret & Guerrilla Modelling! Sketch silently, ask sharp questions, then watch collaboration naturally unfold. Prove its worth, not just your role.
Read the full advice: buff.ly/84Wsoev
XoXo CoMo
Well, well, well. Stuck between neutral facilitator and screaming expert? The "Hat Switch" is your key! Declare: "Architect hat ON, now OFF." Share critical insights without manipulation. Keep the team driving, not blindly crashing.
Read the full advice: buff.ly/VaqNSGc
XoXo CoMo
How many people should I invite for a collaborative modelling session? It depends! Go wide for discovery, but for decision-making, the magic number is 5-7. Learn how to manage group sizes for divergence and convergence in the latest Dear CoMo.
We scheduled a new session with Andrew Harmel-Law on anarchist thought & socio-technical design. A look at alternatives to top-down hierarchy for building better teams.
📅 23 Sept at 19:00 NZST
#DDD #SocioTechnical
buff.ly/Bmvoiwe
#DomainDrivenDesign #SocioTechnicalSystems #SoftwareArchitecture
Here is the video:
youtu.be/xOHax5k_wJo?...
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?
-->
@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.
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 -->
Check-out the episode here: www.richard-seidl.com/en/blog/coll...
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.
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.
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.
Chec-out the full video here: www.youtube.com/watch?v=Q9-L...
