Please log in to watch this conference skillscast.
DDD is about understanding and communicating complexity. We have long recognized that the most effective way to communicate complexity is via human language. But language poses a challenge when working in a team comprised of members of different (sub)cultures and nationalities, each with a native language that might not be the same as the language we are communicating in. Each of these cultures has a different perception about how to communicate effectively.
By way of example, in some cultures, it is considered appropriate and respectable to use the tentative voice “perhaps we should consider trying X”. Whereas in other cultures it is the assertive voice that is valued “This is how we should do it”.
Assuming that everybody in the room wants to communicate effectively, what aspects can we define that impact our design? What organizational culture fits better with what type of architecture (microservices, monolith)? And what cultural needs must these architectures and boundaries address to succeed? Join us in this interactive talk where we together explore these challenges!
YOU MAY ALSO LIKE:
- Does Culture Impact Software Design? (SkillsCast recorded in October 2021)
- Domain Models in Practice with Marco Heimeshoff (Online Workshop on 6th - 10th June 2022)
- Certified Agile Team Coaching with Ben Maynard & Jon Spruce (Online Workshop on 15th - 19th August 2022)
- P3X People Product Process eXchange: Online (Online Conference on 21st September 2022)
- P3X People Product Process eXchange: In Person (in London on 21st September 2022)
- LDN Talks May 2022 - Quickwit Takeover (in London on 30th May 2022)
- Software Architecture in a DevOps World (SkillsCast recorded in February 2022)
- Communication & Influence for Techies: An Unconventional Look at conversations (SkillsCast recorded in January 2022)
Does Culture Impact Software Design?
A lot of knowledge is lost when designing and building software — lost because of hand-overs in a telephone game, confusing communication by not having a shared language, discussing complexity without visualisation and by not leveraging the full potential and wisdom of the diversity of the people. That lost knowledge while creating software impacts the sustainability, quality and value of the software product. Kenny Baas-Schwegler is a socio-technical architect. He blends IT approaches like Domain-Driven Design and Continuous Delivery and facilitates change through using visual collaboration practices, the Cynefin framework and Deep Democracy. Kenny empowers and collaboratively enables organisations, teams and groups of people in designing and building sustainable quality software products.
Chief Architect LTTS Israel