Storystorming DDD Wroclaw

Ten colors, six tools, one goal: Storystorming is a very lightweight approach for understanding your organisation's problems, designing suitable solutions and transparently planning their implementation. Storystorming seamlessly integrates impact mapping, event storming, domain storytelling, user story mapping, collaboration modelling and example mapping into one cohesive approach using ten colors of sticky notes. Using these six tools, rooted in agility, domain-driven design (DDD) and behavior driven development (BDD), Storystorming fosters an intensive collaboration between business and technology experts. Now they can connect the dots and discover what your organisation needs to remain successful.

Transcript

1. Storystorming Wroclaw, Sep 30th 2019 with @martinschimak
2. Storystorming Hands On
3. Event Storming Domain Storytelling Story Mapping Storystorming Impact Mapping Process Modelling Example Mapping
4. Understand the bigger picture of your domain Storystorming goes Event Storming
5. Storystorming goes Impact Mapping Define goals, strategic and tactical options Event Storming
6. Easily explore specific domain scenarios Impact Mapping Storystorming goes Domain Storytelling Event Storming
7. Read the blogpost? https://medium.com/plexiti Storystorming goes Domain Storytelling Explore your domain—by literally watching your language @martinschimak
8. Ticketing screen plan available seats Customer Cashier confirms reservation available seats reservation number recommends asks for screen plan reservation finds seats in confirm seats in generates tells 1 2 3 4 5 6 7
9. Storystorming goes Domain Storytelling
10. Attention Annotation Basic building blocks of Domain Storytelling Actor Work Object Activity + + + Context @martinschimak
11. Verb Subject Making Storytelling as simple as it really is Object @martinschimak Subject "A story consists of sentences. A sentence consists of three basic building blocks!" ✓ ✓ Subject Verb Object ✓ ✓
12. asks for Customer reservation @martinschimak A very first sentence Subject Verb Object ✓ ✓ ✓ ✓
13. Cashier reservation asks for Customer @martinschimak A very first sentence Subject Verb Object ✓ ✓ ✓ ✓
14. Cashier reservation asks for Customer @martinschimak A very first sentence using a bit less space Subject Verb Object ✓ ✓ ✓ ✓
15. finds seats in screen plan Seats are available Ticketing 1 2 A B C Cashier reservation asks for Customer @martinschimak Subject Verb Object Partner Subject 2nd Sentence 1st Subject's Lane Assumed Behavior ✓ ✓ ✓ ✓ ✓ ✓ 2 A ✓ "Tell and record story from left to right, sentence by sentence. Refactor and improve!"
16. recom- mends available seats confirms offered seats confirms seats generates reservation tells reservation number Customer likes seats Seats are available finds seats in screen plan Ticketing Cashier reservation asks for Customer Seats are available Current system does not block seats
17. recom- mends seats 14 and 15, sector A2 confirms seats 14 and 15, sector A2 confirms seats 14 and 15, sector A2 generates reservation #THQB for seats 14 and 15, sector A2 tells reservation number #THQB Customer likes seats Seats are available finds seats 14 and 15, sector A2 in screen plan Ticketing Stadium cashier Andrew reservation of two football tickets for sector A2 calls by phone and asks for Football fan Samantha Seats are available Current system does not block seats
18. A real life case from a bird's eye view @martinschimak
19. Hands On! Verb Object Machine 2 Human Object Verb Human Behavior assumed Attention required 1 @martinschimak We are a family of four (two parents, two teenagers) and have to take care of shopping on a regular basis. Everybody should help a bit from time to time! Therefore we use a mobile ToDo App with a shared shopping list. All family members can add shopping items to this list, such as e.g. "1 loaf of bread". Items may be marked to be urgently needed on a certain date. The shopping list will then inform all family members about such an urgently needed item. Whoever has time or comes by a suitable shop just marks any bought item as Done in the shopping list. Please model a VERY SPECIFIC KEY EXAMPLE SCENARIO by means of Storystorming! 1 2
20. adds 1 glass of Nutella Shopping List Fabia 10 cans of corn adds Kathi Early Friday morning marks Nutella as due on Friday Martin 2 liters of milk adds reminds to buy 1 glass of Nutella 1 glass of Nutella 1 glass of Nutella buys 1 glass of Nutella 2 l milk buys 10 cans of corn are too heavy Fabia can't live without One possible scenario …
21. My take on some strengths of the approach - Record natural language (even without immediate full understanding) - Improve upon single terms and prepare your ubiquitous language (DDD) - Work close to some individual's human perspective, perfect for interviews - Focus on just one single example sequence of all possible activities - Clarify problems and exceptions - by adding assumptions or more stories - Discuss alternatives – just by taking a picture and rearranging stickies
22. Strengths and Weaknesses? :-)
23. Storystorming Background
24. EventStorming is an inspiring part of Storystorming
25. … thanks to the creative energy of my customers and countless meetups like the awesome EventStorming Summit in Bologna! Storystorming slowly developed here ... :-)
28. © Paul Rayner‘s „Essential DDD“ workshop in Denver 2018 `s three pillars
29. Alberto Brandolini's Understand the bigger picture of your domain!
30. Easily explore specific domain scenarios! Stefan Hofer's and Henning Schwentner's
31. Plan deliverables and priorities with overview! © https://mozaicworks.com/blog/3-uses-story-maps-build-better-product/ Jeff Patton's
35. Storystorming likes simple sticky notes
36. Storystorming's 10 basic building blocks Behavior (chosen) "Command" (given) ! "Exclamation" (made) ! "Question" (asked) ? "Statement" (made) . Machine Human <Event> (happened) Deliverable (considered) Attention (required)
37. Easily explore specific domain scenarios Impact Mapping Storystorming goes Domain Storytelling Event Storming
40. Plan deliverables and priorities with overview Impact Mapping Storystorming goes Story Mapping Domain Storytelling Event Storming
41. Storystorming goes Process Modelling Story Mapping Design fine-grained workflows for participants Impact Mapping Domain Storytelling Event Storming
42. Storystorming goes Example Mapping Specify rules and detailed software behavior Story Mapping Impact Mapping Domain Storytelling Event Storming Process Modelling
43. Event Storming Story Mapping Storystorming Impact Mapping Example Mapping Domain Storytelling Process Modelling
44. Storystorming Understand the bigger picture of your domain Easily explore specific domain scenarios Plan deliverables and priorities with overview Design fine-grained workflows for participants Specify rules and detailed software behavior Define goals, strategic and tactical options
45. 4x Super Sticky Post-It Bangkok Collection • orange 'event' (2) • magenta 'attention' (2) • blue 'command' (2) 3x Super Sticky Post-It Marrakesh Collection • dark green 'statement' (2) • red 'machine' (1) • blue 'command' (1) • lilac 'behavior' (1) • dark yellow 'human' (1) 2x Super Sticky Post-It Miami Collection • blue 'command' (2) • light green 'question' (2) • light pink 'exclamation' (1) plus one other color 3x Super Sticky Post-It Standard Collection • light yellow deliverable' (6) Storystorming Yourself @martinschimak
46. Storystorming Learn six collaborative modelling tools in two days, using ten sticky colors working through one challenge! Open workshop in Vienna? Visit https://techtalk.at/trainings/storystorming And in-house workshops? Everywhere! Contact martin.schimak@plexiti.com
47. Open workshop in Vienna? Visit https://techtalk.at/trainings/storystorming And in-house workshops? Everywhere! Contact martin.schimak@plexiti.com Storystorming Learn six collaborative modelling tools in two days, using ten sticky colors working through one challenge!