Introducing EventStorming
Introducing EventStorming
$9.99
Minimum price
$19.99
Suggested price
Introducing EventStorming

This book is 66% complete

Last updated on 2018-06-06

About the Book

At first look, EventStorming is deceptively simple: just have a long paper roll available, and a virtually unlimited stock of coloured sticky notes and start modelling problems that looked too big to be modelled. But the ability to visually mastering large scale complexity opens the way to many interesting outcomes.

Better business processes: once you see the process, impediments and correlations are vividly displayed. You can't avoid tackling them.

- Better software architectures: see the areas where stakeholders needs are in conflict, resolve coflicts by leveraging bounded contexts.

Better learning: exploration of complex domain is now question-driven and with a visible collective sketch. Your team will never be so wise.

Better interactions: trigger the right conversation between the right people.

In this book you'll find guidance about how to leverage the potential of EventStorming.

Disclaimer: work in progress

The book is still in progress. There's holes and FIXME section. And there's a great need for feedback.

I 've set up a trello project in order to collect some feedback. Don't know yet if that's a good idea or not, but here's the link.

About the Author

Alberto Brandolini
Alberto Brandolini

I am helping teams and companies to develop brilliant solutions to complex problems. Sometimes this involves writing software. Sometimes this involves working with people. I like both ways, especially when it leads me into unexplored territories.

I've been coding since 1982, experimenting since ...forever? This led me into Agile, Domain-Driven Design, Lean, Complexity, Management 3.0 and everything needed in order to solve the problem.

I am a father, a husband, an entrepreneur, a consultant, a developer, a teacher, a public speaker, a cook, a drummer... now it's time to be a writer.

A glimpse of what I am into can be found on my blog, and I've been speaking in quite a few places lately. My presentation track is available here.

I run avanscopertaone of the coolest places on earth to teachlearn and experiment

Table of Contents

  •  
    • Preface - 25%
      • About this book
      • Who is this book for
      • Notation
      • Acknowledgments
      • How to read this book
      • Version
    • 1. 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
    • 2. A closer look to the problem space - 80%
      • Complexity in a nutshell, or less
      • Organization silos
      • Hierarchy
      • The shape of the problem
    • 3. 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
    • 4. 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
    • 5. Playing with value - part 1
      • Explore Value
      • Explore Purpose
    • 6. Making it happen
      • Managing Participant’s experience
      • Managing conflicts
    • 7. Preparing the workshop - 30%
      • Choosing a suitable room
      • Provide an unlimited modeling surface
      • Managing invitations
    • 8. 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
    • 9. Big Picture Variations - 50%
      • Software Project Discovery
      • Organization Retrospective
      • Induction for new hires
  • Why is it working?
    • 10. What software development really is - 40%
      • Software development is writing code
      • Software development is learning
      • Software development is making decisions
      • Software development is waiting
    • 11. 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
    • 12. 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
    • 13. 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
    • 14. Breaking the space constraint - 30%
      • Overcoming your whiteboard implicit constraint
      • The illusion of the unlimited model
  • Modeling processes and services
    • 15. A platform for cooperation
    • 16. Exploring value
      • Explore Value Created and Destroyed
      • Explore multiple currencies
      • What to do when there is no value?
      • Look for inconsistencies
    • 17. Observing global state - 10%
      • The transaction obsession
      • There’s more to consistency than it’s apparent to the eye
  • Modeling software systems
    • 18. 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?
    • 19. The picture that explains everything - 5%
    • 20. Three types of blockers
      • User Decisions
      • Processes and policies
      • What happened to aggregates?
    • 21. 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
    • 22. 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
    • 23. Color Modeling Patterns - 10%
      • Policies
      • Why Orange?
      • Time Triggered Events
    • 24. Modeling Aggregates
      • Discovering aggregates
    • 25. Event Design Patterns - 5%
      • Discovery strategies
      • Composite Domain Event
    • 26. 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
    • 27. From paper roll to working code
      • Managing the design level EventStorming artifact
      • Coding ASAP
    • 28. 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?
    • 29. Modeling in the large - 10%
      • Enter Bounded Contexts
      • Bounded Contexts modeling patterns
    • 30. Working with Startups - 2%
      • The focus is not on the app
      • Leverage Wisdom of the crowd
      • Multiple business models
    • 31. 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
    • 32. Designing a product
      • This is not a tailored solution
      • Matching expectations
      • Simplicity on the outside
    • 33. Model Storming - 0%
    • 34. Friends and ncestors
      • Ancestor and relatives
    • 35. Remote Event Storming
      • Ok, seriously
      • Downgrading expectations
  • Patterns and Anti-patterns
    • 36. 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
    • 37. 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
    • 38. RED ZONE
      • Fresh Catering
      • Providential Toilet Door Malfunctioning
  • Specific Formats
    • 39. Big Picture EventStorming
    • 40. Design-Level EventStorming
      • Next actions
    • 41. Value Stream EventStorming
    • Glossary - 40% (but do you really care?)
      • Fuzzy by design
    • Tools
      • Modeling Surfaces
      • Markers
      • Stickies
      • Static pads
      • Recording results
    • Bibliography
  • Notes

The Leanpub 45-day 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms...

Write and Publish on Leanpub

Authors, publishers and universities use Leanpub to publish amazing in-progress and completed books and courses, just like this one. You can use Leanpub to write, publish and sell your book or course as well! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub