Stop Coding, Start Asking Questions - Kenny Baas-Schwegler, Gien Verschatse

Software Testing Unleashed - Better Teams. Better Software. Better World.

Use collaborative software design to break down silos

"We try to make it visual because then you focus the conversation on what's actually there, what's in front of you." - Gien Verschatse

In this episode I talk to Gien Verschatse and Kenny Baas-Schwegler about the challenges of collaborative software design, especially the disconnect between development teams and business stakeholders. Both Gien and Kenny shared stories of communication gaps, assumptions in requirements and the constant struggle to build shared understanding. They gave practical tips for breaking down silos and making modeling sessions actually work - not just as visual exercises, but as real opportunities for teams to learn together.

Gien Verschatse is an experienced consultant and software engineer that specialises in domain modelling and software architecture. She has experience in many domains such as the biotech industry, where she specialised in DNA building lab services. She's fluent in both object-oriented and functional programming, mostly in .NET. As a Domain-Driven Design practitioner, she always looks to bridge the gaps between experts, users, and engineers. As a side interest, she's researching the science of decision-making strategies, to help teams improve how they make technical and organisational decisions. She shares her knowledge by speaking at international conferences. And when she is not doing all that, you'll find her on the sofa, reading a book and sipping coffee.

Kenny Baas believes in collaborative software design where ‘every voice shapes the software’. Leveraging a domain-driven design approach with Team Topologies, he facilitates clearer communication between stakeholders and software creators by collaborative modelling and deep democracy, decoding complexities, resolving conflicts and ensuring software remains agile to business demands. As an independent software consultant and trainer, he is specialised in technical leadership, software architecture, and sociotechnical system design. He works with organisations and teams to design and build sustainable and resilient software architecture.

Highlights:

• Direct communication with stakeholders prevents costly misunderstandings in software projects.
• Collaborative modeling breaks down silos and creates shared understanding.
• Simple, visual tools like event storming foster effective team collaboration.
• Continuous feedback and involvement outperform handoffs and isolated work.
• Shared understanding is more valuable than the physical model or documentation produced.

챕터

1. Stakeholder Communication in Software Development (00:00:00)

2. Domain Expertise Over Scrum Misuse (00:04:40)

3. Alignment Gaps in Company Strategy (00:08:19)

4. Improving Communication Across Teams (00:11:12)

5. Cross-Disciplinary Mapping Tools (00:15:15)

6. Designing Evolving Software Boundaries (00:18:01)

7. Navigating Social Science Challenges (00:23:12)

8. Start Small, Inspire Change (00:26:22)

9. Facilitating Shared Understanding (00:27:50)

10. Efficient Collaboration Over Scrum (00:32:00)

11. Continuous Stakeholder Conversations in Agile (00:34:23)