The way agile software teams gain knowledge about what to build is either by the product owner or business analyst serving as a proxy to domain knowledge. Domain knowledge usually ends up as second-hand news in either functional design documents or as user stories in some scrum tools like Jira.
Second-hand knowledge is a significant risk when building software. Each time information is transferred just like doing the telephone game, the story is changed, and people make assumptions. Because as Alberto Brandolini said: ‘It is not the domain expert’s knowledge that goes into production; it is the developer’s assumption of that knowledge that goes into production’.
Even when these stories are shared first hand, they usually are discussed sitting around a table looking at a screen showing the user stories. Addressing complex problems without visualisation is impossible for most humans to solve. Doing so resolve in making a lot of assumptions again, which will stop us from building the right thing.
Join us in this session where I will explain how visual collaborative modelling can help you write and deliver better software. Through proper preparation and facilitation, we can co-create solutions. Co-creating solutions by visual collaborative modelling make sure we have buy-in from the entire team. You will end up knowing how to start your visual collaborative modelling journey with tools like EventStorming and Example Mapping.
