[{"data":1,"prerenderedAt":73},["ShallowReactive",2],{"content-guides-eventstorming-learn-more":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":8,"contributorPaths":9,"menuType":11,"contentName":12,"slug":13,"readingTime":14,"menu":15,"nextDocItem":72,"previousDocItem":64},"\u003Cp>This guide gave you a brief introduction to running a Big Picture EventStorming session and the\nbenefits that it can provide. There is much more to EventStorming than what's captured here. Still,\nthe content here should give you an idea of what EventStorming entails and what you can expect if\nyou are looking to gain clarity across your organization.\u003C\u002Fp>\n\u003Cp>One of the Amazon leadership principles is "Learn and be curious." Don't be intimidated or\noverwhelmed by EventStorming. You won't get it "right" the first or 15th time because there is no\n"right" way of doing it, only guidelines. What may be best for one group may not be for another.\nLean into the chaos and confusion that EventStorming creates and starting having conversations to\ngain clarity across your team(s).\u003C\u002Fp>\n\u003Cdiv class=\"admonition\">\n\n\u003Cp>If you are an AWS customer, ask your account team to run an EventStorming session with you! A number\nof AWS Solutions Architects and Technical Account Managers are capable facilitators and can help you\nand your team.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\n\u003Ch2>Resources\u003C\u002Fh2>\n\u003Cp>You can learn much more about EventStorming by reading the following ebooks, both on LeanPub.\u003C\u002Fp>\n\u003Cdiv style=\"text-align: center;\">\n  \u003Ch3 style=\"margin-bottom: 0;\">\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes\">Introducing EventStorming\u003C\u002Fa>\u003C\u002Fh3>\n  \u003Cdiv style=\"margin-bottom: 15;\">by Alberto Brandolini\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\n\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes\">\n  \u003Cimg alt=\"Introducing EventStorming\" target=\"_blank\" src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Feventstorming-book-cover.jpeg\" \u002F>\n\u003C\u002Fa>\n\n\u003Cdiv style=\"text-align: center;\">\n  \u003Ch3 style=\"margin-bottom: 0;\">\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes-handbook\">The  EventStorming Handbook\u003C\u002Fa>\u003C\u002Fh3>\n  \u003Cdiv style=\"margin-bottom: 15;\">by Paul Payner\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\n\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes\">\n  \u003Cimg alt=\"The EventStorming Handbook\" target=\"_blank\" src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Feventstorming-handbook-cover.png\" \u002F>\n\u003C\u002Fa>\n\n\u003Ch2>What next?\u003C\u002Fh2>\n\u003Ch3>Process modeling\u003C\u002Fh3>\n\u003Cp>After a Big Picture session is run you can dive deeper into a particular area of the board using\nprocess-level sessions. In our example, we could dive into the "payment verification" subdomain to\nadd more details, clean up any confusion, answer questions captured through hotspots and otherwise\ngo into more depth.\u003C\u002Fp>\n\u003Cp>A process-level EventStorming session introduces two additional concepts:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Policies\u003C\u002Fli>\n\u003Cli>Read\u002Fquery models\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Don't overthink or be intimidated by this. The additional detail and concepts may look and sound\ncomplicated, but they are merely tools meant to drive collaboration and discussion. EventStorming\nmay be a well-defined process, but it can (and should) be loosely applied.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\u002Fmaster\u002Fresources\u002Fprocess-picture.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cblockquote>\n  \"Process modeling Picture that explains \"Almost\" Everything\" from\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\">\n    EventStorming Glossary & Cheat sheet\n  \u003C\u002Fa>, under CC-BY-SA-4.0 license\n\u003C\u002Fblockquote>\n\n\u003Ch3>Design modeling\u003C\u002Fh3>\n\u003Cp>Once process modeling feels like it's done enough you can go another level deeper with your\ntechnical team to start thinking through how you may implementation such a process.\u003C\u002Fp>\n\u003Cp>This too introduces another concept, the often ambiguous and confusing "aggregate" or "constraint."\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\u002Fmaster\u002Fresources\u002Fsoftware-picture.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cblockquote>\n  \"Software design Picture that explains \"Almost\" Everything\" from\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\">\n    EventStorming Glossary & Cheat sheet\n  \u003C\u002Fa>, under CC-BY-SA-4.0 license\n\u003C\u002Fblockquote>\n\n\u003Ch3>Building\u003C\u002Fh3>\n\u003Cp>Once you go through the entire process from Big Picture all the way to a Design-level EventStorming\nsessions you and your team will be in a great position to start building. At this phase, you will\nhave enough information to get starting using your preferred development process: setting up a\nsprint, scrum, writing user stories or simply building a small POC.\u003C\u002Fp>\n\u003Cp>Since EventStorming models an non-trivial process and uses domain events as the language, you have a\nbig head start when adopting an event-driven architecture strategy. The boundaries you identified\nduring EventStorming should guide your design and thinking as you begin to create independent\nsystems and services that communicate through events. EventStorming and domain-driven design aren't\nsilver bullets; you (still) need to think deeply as you start and continue building. However, you\nwill have a big advantage having gone through multiple collaborative EventStorming sessions and\nhaving a shared understanding with your colleagues.\u003C\u002Fp>\n\u003Cp>\u003Cem>Now go build!\u003C\u002Fem> 🚀\u003C\u002Fp>\n\u003Cstyle>\n  .admonition {\n    background-color: rgb(230, 246, 230);\n    padding: 10px;\n    border: 1px solid darkgreen;\n    border-radius: 5px;\n    margin: 10px 0;\n  }\n\u003C\u002Fstyle>\n",{"id":6,"title":7},"learn-more","Learning more","This guide gave you a brief introduction to running a Big Picture EventStorming session and the\nbenefits that it can provide. There is much more to EventStorming than what's captured here. Still,\nthe content here should give you an idea of what EventStorming entails and what you can expect if\nyou are looking to gain clarity across your organization.\n\nOne of the Amazon leadership principles is \"Learn and be curious.\" Don't be intimidated or\noverwhelmed by EventStorming. You won't get it \"right\" the first or 15th time because there is no\n\"right\" way of doing it, only guidelines. What may be best for one group may not be for another.\nLean into the chaos and confusion that EventStorming creates and starting having conversations to\ngain clarity across your team(s).\n\n\u003Cdiv class=\"admonition\">\n\nIf you are an AWS customer, ask your account team to run an EventStorming session with you! A number\nof AWS Solutions Architects and Technical Account Managers are capable facilitators and can help you\nand your team.\n\n\u003C\u002Fdiv>\n\n## Resources\n\nYou can learn much more about EventStorming by reading the following ebooks, both on LeanPub.\n\n\u003Cdiv style=\"text-align: center;\">\n  \u003Ch3 style=\"margin-bottom: 0;\">\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes\">Introducing EventStorming\u003C\u002Fa>\u003C\u002Fh3>\n  \u003Cdiv style=\"margin-bottom: 15;\">by Alberto Brandolini\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\n\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes\">\n  \u003Cimg alt=\"Introducing EventStorming\" target=\"_blank\" src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Feventstorming-book-cover.jpeg\" \u002F>\n\u003C\u002Fa>\n\n\u003Cdiv style=\"text-align: center;\">\n  \u003Ch3 style=\"margin-bottom: 0;\">\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes-handbook\">The  EventStorming Handbook\u003C\u002Fa>\u003C\u002Fh3>\n  \u003Cdiv style=\"margin-bottom: 15;\">by Paul Payner\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\n\u003Ca href=\"https:\u002F\u002Fs12d.com\u002Fes\">\n  \u003Cimg alt=\"The EventStorming Handbook\" target=\"_blank\" src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Feventstorming-handbook-cover.png\" \u002F>\n\u003C\u002Fa>\n\n## What next?\n\n### Process modeling\n\nAfter a Big Picture session is run you can dive deeper into a particular area of the board using\nprocess-level sessions. In our example, we could dive into the \"payment verification\" subdomain to\nadd more details, clean up any confusion, answer questions captured through hotspots and otherwise\ngo into more depth.\n\nA process-level EventStorming session introduces two additional concepts:\n\n- Policies\n- Read\u002Fquery models\n\nDon't overthink or be intimidated by this. The additional detail and concepts may look and sound\ncomplicated, but they are merely tools meant to drive collaboration and discussion. EventStorming\nmay be a well-defined process, but it can (and should) be loosely applied.\n\n![](https:\u002F\u002Fraw.githubusercontent.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\u002Fmaster\u002Fresources\u002Fprocess-picture.jpg)\n\n\u003Cblockquote>\n  \"Process modeling Picture that explains \"Almost\" Everything\" from\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\">\n    EventStorming Glossary & Cheat sheet\n  \u003C\u002Fa>, under CC-BY-SA-4.0 license\n\u003C\u002Fblockquote>\n\n### Design modeling\n\nOnce process modeling feels like it's done enough you can go another level deeper with your\ntechnical team to start thinking through how you may implementation such a process.\n\nThis too introduces another concept, the often ambiguous and confusing \"aggregate\" or \"constraint.\"\n\n![](https:\u002F\u002Fraw.githubusercontent.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\u002Fmaster\u002Fresources\u002Fsoftware-picture.jpg)\n\n\u003Cblockquote>\n  \"Software design Picture that explains \"Almost\" Everything\" from\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fddd-crew\u002Feventstorming-glossary-cheat-sheet\">\n    EventStorming Glossary & Cheat sheet\n  \u003C\u002Fa>, under CC-BY-SA-4.0 license\n\u003C\u002Fblockquote>\n\n### Building\n\nOnce you go through the entire process from Big Picture all the way to a Design-level EventStorming\nsessions you and your team will be in a great position to start building. At this phase, you will\nhave enough information to get starting using your preferred development process: setting up a\nsprint, scrum, writing user stories or simply building a small POC.\n\nSince EventStorming models an non-trivial process and uses domain events as the language, you have a\nbig head start when adopting an event-driven architecture strategy. The boundaries you identified\nduring EventStorming should guide your design and thinking as you begin to create independent\nsystems and services that communicate through events. EventStorming and domain-driven design aren't\nsilver bullets; you (still) need to think deeply as you start and continue building. However, you\nwill have a big advantage having gone through multiple collaborative EventStorming sessions and\nhaving a shared understanding with your colleagues.\n\n_Now go build!_ 🚀\n\n\u003Cstyle>\n  .admonition {\n    background-color: rgb(230, 246, 230);\n    padding: 10px;\n    border: 1px solid darkgreen;\n    border-radius: 5px;\n    margin: 10px 0;\n  }\n\u003C\u002Fstyle>\n",[10],"content\u002Fcontributors\u002Fbrian-zambrano.json","LIST","EventStorming","\u002Fcontent\u002Fguides\u002Feventstorming\u002Flearn-more","4 min",[16],{"title":12,"content":17},[18,26,33,39,45,51,58,64,70],{"title":19,"order":20,"youtubeVideoID":21,"time":22,"path":23,"id":24,"link":25},"Introduction",1,"FG4UOoEJvBc","5 min","introduction","introduction.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fintroduction",{"title":27,"order":28,"time":29,"path":30,"id":31,"link":32},"Step 1 - Invitations",10,"2 min","invitations","invitations.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Finvitations",{"id":34,"title":35,"order":36,"time":29,"path":37,"link":38},"events.md","Step 2 - Crowdsource events",20,"events","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fevents",{"title":40,"order":41,"time":29,"path":42,"id":43,"link":44},"Step 3 - Sequence events",30,"timeline","timeline.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Ftimeline",{"title":46,"order":47,"time":29,"path":48,"id":49,"link":50},"Step 4 - People",40,"people","people.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fpeople",{"title":52,"order":53,"time":54,"path":55,"id":56,"link":57},"Step 5 - Hotspots",50,"1 min","hotspots","hotspots.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fhotspots",{"title":59,"order":60,"time":29,"path":61,"id":62,"link":63},"Step 6 - External systems",60,"systems","systems.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fsystems",{"title":65,"order":66,"time":54,"path":67,"id":68,"link":69},"Step 7 - Pivotal events",70,"boundaries","boundaries.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fboundaries",{"id":71,"title":7,"time":14,"path":6,"link":13},"learn-more.md",null,1792665264675]