Visual and Collaborative Modelling

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.

01abe62e641a626ed2dccc08ea2f8a14?s=128

Kenny Baas-Schwegler

February 05, 2020
Tweet

Transcript

  1. Visual and collaborative modelling @kenny_baas

  2. 2 @kenny_baas

  3. 3 @kenny_baas

  4. 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
  5. 5 @kenny_baas Domain Experts Developers 1 2 3 4

  6. @kenny_baas

  7. 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
  8. 8 @kenny_baas

  9. @kenny_baas

  10. 10 @kenny_baas

  11. 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
  12. @kenny_baas Photo by Campaign Creators on Unsplash

  13. 13 @kenny_baas

  14. 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
  15. 15 @kenny_baas

  16. 16 @kenny_baas

  17. 17 How many beans? @kenny_baas

  18. 18 @kenny_baas

  19. 19 How many beans? @kenny_baas

  20. 20 @kenny_baas

  21. 21 How many beans? @kenny_baas

  22. @kenny_baas

  23. @kenny_baas Visual and Collaborative modelling Photo by Kaleidico on Unsplash

  24. Creating a shared sense of reality Photo by Matt Noble

    on Unsplash @kenny_baas
  25. @kenny_baas

  26. 26 @kenny_baas https://www.eventstorming.com/

  27. 27 @kenny_baas https://baasie.com/2019/05/08/eventstorming-tools-what-is-in-my-flight-case/ https://baasie.com/2019/04/30/a-quest-in-finding-the-perfect-e ventstorming-backpack/

  28. 28 @kenny_baas https://www.eventstorming.com/

  29. 29 @kenny_baas Chaotic Exploration

  30. 30 @kenny_baas

  31. 31 @kenny_baas Enforcing the timeline

  32. Photo by Shane Rounce on Unsplash @kenny_baas Only talk about

    visible things!
  33. 33 @kenny_baas

  34. 34 @kenny_baas

  35. 35 @kenny_baas

  36. 36 @kenny_baas Business process modelling for the as-is situation

  37. 37 @kenny_baas Big Picture for finding emerging bounded context

  38. @kenny_baas You had to be there!

  39. Planning a wedding https://xebia.com/blog/eventstorming-the-perfect-wedding/

  40. 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
  41. 41 @kenny_baas

  42. 42 Visual collaboration tools @kenny_baas

  43. 43 @kenny_baas https://cucumber.io/blog/bdd/example-mapping-introduction/

  44. 44 @kenny_baas

  45. 45 @kenny_baas

  46. 46 @kenny_baas

  47. Photo by Frederic Köberl on Unsplash This is not a

    democracy! - Pim Smeets @kenny_baas
  48. @kenny_baas Romeu Moura - Bourdieu’s social theory and our work

    in tech: https://vimeo.com/342450313
  49. foto: Hideta Nagai) credit: Corporate tribe book by Danielle Braun,

    Jitske Kramer @kenny_baas
  50. @kenny_baas Photo by Jay Wen on Unsplash Check-in / Check-out

  51. @kenny_baas Photo by Cytonn Photography on Unsplash Agreements

  52. @kenny_baas Photo by Clem Onojeghuo on Unsplash Spread

  53. 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
  54. 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:
  55. @kenny_baas Virtual Domain-driven design https://virtualddd.com

  56. #CatTax @kenny_baas Strategic software delivery Domain-Driven Design Continuous Delivery Socio-technical

    thinker Collaborative modeller Deep Democratic facilitator @kenny_baas baasie.com