Skip to content

Instantly share code, notes, and snippets.

@karanrai
Last active July 17, 2020 05:18
Show Gist options
  • Save karanrai/5093e5ce0f51d390f3b9689b7a5de006 to your computer and use it in GitHub Desktop.
Save karanrai/5093e5ce0f51d390f3b9689b7a5de006 to your computer and use it in GitHub Desktop.

Agenda we prepared

Introductions

Setting the goal

  • Explore the business process as a whole and identify opportunities, risks, and ideas. Marking as hotspots which require further investigation

Getting comfortable with Miro

  • Using stickies, entering text, Enabling map view - come back to center, Cmd / Ctrl D

Getting started

  • What will happen now?
  • We will start by putting an event on the board
  • Explain what is an event - in the past, immutable
  • We will add events across a timeline from left to right
  • Check if the event is already added around the area and if not then add
  • Everyone can focus on their domains which they know well
  • As we go along we will explain and answer questions

Ice breaker

  • Customer enters into store

Event storming starts

  • 30–45 min ~ until 1:15–1:45 pm

Short break - 15 min, Lunch

Sorting and merging (discussing and collaborating, marking Hot spots) - 30 min

  • Identify a strategy to sort
    • Pivotal events
    • Swimlanes
    • Temporal milestones
    • Chapters
  • Introduce users and systems at appropriate points in time

Explicit walk through of events

  • Identify missing events
  • Identify inconsistencies
  • Think from a userUnassigned perspective, ask questions, are we missing something here?

Narrate backwards

  • Why are we doing this?
  • What needs to happen to get to event Z, Z - 1, …

Short break - 15 min, Lunch

Digging deeper

  • Ask why we do something? And what value is added (safety, reputation, brand, money)? What is the risk - add stickies
  • Do we need to validate our hypothesis
  • Identify opportunities and risks

Arrow voting

  • What should we address first? most important concerns to clarify / solve - 3 votes each

Plan next steps

  • We refine certain areas more as they are more uncertain
    • Internal discussions
    • Second event storm with a larger group
    • Research initiatives
  • We identify build vs buy vs partner vs manual decisions
  • If we decide to build something, we plan the team and finer details of the product
  • This feeds into the software design process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment