Introducing EventStorming

Description

Table of Contents Preface - 25% About this book Who is this book for Notation Acknowledgments How to read this book Version What does EventStorming look like? - 85% Challenging corporate processes Kicking off a startup Designing a new feature for a web app Quick EventStorming in Avanscoperta A deep dive into problem space A closer look to the problem space - 80% Complexity in a nutshell, or less Organization silos Hierarchy The shape of the problem Pretending to solve the problem writing software - 50% It's not about `delivering software' The illusion of the underlying model The Product Owner fallacy The backlog fallacy [FIXME: definitely not the first one The backlog fallacy (rewritten) Modeling is broken Requirements gathering is broken Enterprise Architecture is broken The EventStorming approach Running a Big Picture Workshop - 98% Invite the right people Room setup Workshop Structure Phase: Kick-off Phase: Chaotic Exploration Phase: Enforcing the timeline People and Systems Phase: Problems and opportunities Phase: Pick your problem The promised structure summary Playing with value - part 1 Explore Value Explore Purpose Making it happen Managing Participant's experience Managing conflicts Preparing the workshop - 30% Choosing a suitable room Provide an unlimited modeling surface Managing invitations Workshop Aftermath -20% Cooperating domains When to stop? How do we know we did a good job? Wrapping up a big picture workshop Managing the big picture artifact Focusing on the hot spot Documenting the outcomes - TRICKY Emerging structure Big Picture Variations - 50% Software Project Discovery Organization Retrospective Induction for new hires Why is it working? What software development really is - 40% Software development is writing code Software development is learning Software development is making decisions Software development is waiting Learning is the problem, so what? - 20% Understanding our ignorance How does learning happen? The Dreyfuss model as a constraint for learning The invisible deliverable Learning without action is waste People Interaction People In Action - 25% Managing Invitations Igniting the workshop Mastering Workshop Dynamics Observing Body Language Enforcing narratives Walking Skeleton - redefined Is it really a failure? Nobody likes to be wrong Brainstorming biases facilitating the workshop - 10% The economics of a meeting with the big guys Promote questions Allow people to checkout Allow people to stay Keep your mouth shut Introverted and extroverted Breaking the space constraint - 30% Overcoming your whiteboard implicit constraint The illusion of the unlimited model Modeling processes and services A platform for cooperation Exploring value Explore Value Created and Destroyed Explore multiple currencies What to do when there is no value? Look for inconsistencies Observing global state - 10% The transaction obsession There's more to consistency than it's apparent to the eye Modeling software systems Running a Design-Level EventStorming - 10% Scope is different People are different What do we do with the Big Picture Artifact? Where are Events Coming from? Discover Aggregates How do we know we're over? The picture that explains everything - 5% Three types of blockers User Decisions Processes and policies What happened to aggregates? Design-Level modeling tips Make the alternatives visible Choose later Pick a Problem Rewrite, then rewrite, then rewrite again. Hide unnecessary complexity Postpone aggregate naming Building Blocks - 20% Why are Domain Events so special? Events are precise No implicit scope limitation Domain Events as state transitions Domain Events are triggers for consequences Domain Events are leading us towards the bottleneck Alternative approaches Wrapping everything up Commands - Actions - Decisions Color Modeling Patterns - 10% Policies Why Orange? Time Triggered Events Modeling Aggregates Discovering aggregates Event Design Patterns - 5% Discovery strategies Composite Domain Event Collaborative modeling tips and tricks Model the right problem Keep the model clean Postpone branches Finish First / Correct Later Modeling out loud Brainstorm on terms Brainstorm on context Summary From paper roll to working code Managing the design level EventStorming artifact Coding ASAP From EventStorming to UserStories - 5% A placeholder and a better conversation Defining the acceptance criteria EventStorming and User Story Mapping How to combine the two approaches? Modeling in the large - 10% Enter Bounded Contexts Bounded Contexts modeling patterns Working with Startups - 2% The focus is not on the app Leverage Wisdom of the crowd Multiple business models Working in corporate environment - 5% Invitation is crucial Manage check-in process The fog-me-fog model Nobody wants to look stupid Wrapping up What happens next? Corporate Dysfuctions Designing a product This is not a tailored solution Matching expectations Simplicity on the outside Model Storming - 0% Friends and ncestors Ancestor and relatives Remote Event Storming Ok, seriously Downgrading expectations Patterns and Anti-patterns Patterns and Anti-Patterns - 75% Add more space Be the worst Conquer First, Divide Later Do First, Explain Later Fuzzy Definitions Enforce the Timeline Guess First hot spot Icebreaker (the) Incremental Notation Go personal Keep your mouth shut Leave Stuff Around Manage Energy Make some noise! Mark hot spots Money on the table One Man One Marker Poisonous Seats Reverse Narrative The Right To Be Wrong Single Out the Alpha-male Slack day after Speaking out loud Start from the center Start from the extremes Unlimited Modeling Surface Visible Legend Anti-patterns Ask Questions First Big Table at the center of the room Committee Divide and Conquer Do the right thing Dungeon Master Follow the leader Human Bottleneck Karaoke Singer Precise Notation Religion War The Spoiler Start from the beginning The godfather RED ZONE Fresh Catering Providential Toilet Door Malfunctioning Specific Formats Big Picture EventStorming Design-Level EventStorming Next actions Value Stream EventStorming Glossary - 40% (but do you really care?) Fuzzy by design Tools Modeling Surfaces Markers Stickies Static pads Recording results Bibliography