Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Visual and Collaborative Modelling

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

Visual and Collaborative Modelling

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 me in this session where I will explain how visual collaborative modelling can help you write 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.

Avatar for Kenny Baas-Schwegler

Kenny Baas-Schwegler

February 05, 2020
Tweet

More Decks by Kenny Baas-Schwegler

Other Decks in Technology

Transcript

  1. 4 To communicate effectively, the code must be based on

    the same language used to write the requirements - the same language that the developers speak with each other and with domain experts - Eric Evans @kenny_baas
  2. 7 It is not the domain experts knowledge that goes

    to production, it is the assumption of the developers that goes to production - Alberto Brandolini @kenny_baas
  3. 11 “That shallowness of knowledge produces software that does a

    basic job but lacks a deep connection to the domain expert’s way of thinking.” - Eric Evans @kenny_baas
  4. Photo by Jean-Frederic Fortier on Unsplash The Magical Number Seven,

    Plus or Minus Two: Some Limits on Our Capacity for Processing Information George A. Miller “ @kenny_baas
  5. Photo by Rikki Chan on Unsplash Who to invite is

    about thinking in perceptions instead of people. Invite especially people with annoying perceptions. @kenny_baas
  6. Photo by Frederic Köberl on Unsplash This is not a

    democracy! - Pim Smeets @kenny_baas
  7. Visual and collaborative modelling ➔ Reduce handovers, get first-hand knowledge

    by collaboration! ➔ Visualise complexity and be aware of cognitive bias! ➔ Only talk about visual things ➔ Room Setup is important ➔ Keep spreading by asking: Who recognises…...? ➔ Start by doing in a safe environment, else get an experienced facilitator. ➔ There are no Silver Bullets! Pick your tool for the job! @kenny_baas
  8. Learn more…. @kenny_baas Ruth Malan @ruthmalan Dawn Ahukanna @dawnahukanna Rebecca

    Wirfs-Brock @rebeccawb Evelyn van Kelle @EvelynvanKelle https://www.visualcollaborationtools.com/ The Collaborative Modeling Unconference 2020 Upcoming book community book: Leanpub:
  9. #CatTax @kenny_baas Strategic software delivery Domain-Driven Design Continuous Delivery Socio-technical

    thinker Collaborative modeller Deep Democratic facilitator @kenny_baas baasie.com