Disentangle the Data Enterprise Spaghetti to continuous delivery, a Domain Driven Design Story

Disentangle the Data Enterprise Spaghetti to continuous delivery, a Domain Driven Design Story

Are you working Agile but not doing twice the work in half the time? Does your Enterprise Architecture look like a spaghetti? Or is continuous delivery not working for you? Well, this is often the case at most enterprises… And, it is perfectly explainable why this happens.

Join me in this talk, about an enterprise trying to move faster with agile and continuous delivery, but actually finds itself slowed down and getting more entangled because of Conway’s Law. We will show how we used Event Storming to create a Context Map to get grip on the language and communication within the company. Then, we show by using the inverse of Conway’s Law how we disentangled the spaghetti into teams that can deliver continuously.

01abe62e641a626ed2dccc08ea2f8a14?s=128

Kenny Baas-Schwegler

March 20, 2018
Tweet

Transcript

  1. Disentangle the Data Enterprise Spaghetti to Continuous Delivery a #DDDesign

    story
  2. Kenny Baas @kenny_baas Baasie.com blog.xebia.com/author/kbaas/

  3. None
  4. None
  5. “ Most people make the mistake of thinking design is

    what it looks like. People think it’s this veneer – that the designers are handed this box and told, “Make it look good!” That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works. — STEVE JOBS
  6. Questions about whether design is necessary or affordable are quite

    beside the point: design is inevitable. The alternative to good design is bad design, not no design at all. — DOUGLAS MARTIN
  7. None
  8. None
  9. None
  10. Conway’s Law "Any organization that designs a system (defined more

    broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization's communication structure."
  11. None
  12. Agile Transformations

  13. https://martinfowler.com/articles/microservices.html

  14. None
  15. Changing elements usually has the least effect; changing interconnections or

    purpose is usually more dramatic.
  16. "Software Development is about learning, working code is a side

    effect" Alberto Brandolini @ziobrando
  17. Big Picture Process Modelling Software Design Formats

  18. None
  19. None
  20. Big Picture

  21. Chaotic Exploration

  22. Enforce the Timeline

  23. Facilitate Constraints

  24. Structure starts to emerge

  25. Add external systems and persons

  26. Show the value

  27. Opportunities and problems

  28. Arrow the constraint

  29. None
  30. Problem Space Solution Space Problem & Solution Space

  31. Problem Space

  32. Solution Space - Context Map

  33. None
  34. None
  35. Process Modelling

  36. None
  37. http://eventstorming.com/

  38. storytelling

  39. Software modelling

  40. Boundries Ticket Bought Reserve ticket Reservation Timeout <- when, then

    ->
  41. Reservation Payment Tickets Reserve ticket Ticket Bought

  42. Pain & Tricks

  43. Inverse Conway maneuver https://martinfowler.com/articles/microservices.html

  44. None
  45. Onion/Hexagonal/Port-Adapter Architecture

  46. None
  47. None
  48. None
  49. Slide theme by: slidescarnival.com

  50. Questions #CATTAX