What is it?
An event storming session to visually map out what the website and MyT platform does.
Why do we need it?
There currently isn’t a single view of everything the website and platform does in the form of users’ journeys. Having this view is important for a number of reasons:
- There will be gaps in our knowledge (and possibly or process). This will help us identify those.
- We can identify the riskiest and most valuable parts of our process. This helps with knowing what we should focus our testing, security and data protection efforts on.
- Ownership: currently it’s a little blurred as to which teams own what part of the system, this will help us identify the “bounded contexts” or our domain and assign accountability to different systems to our squads.
- The exercise will ensure we have a common language to talk about the platform, but also to highlight any areas of po-tay-to/po-tah-to. Sometimes we assume different things and understanding why is important.
We want to be able to split the platform with sensible divisions so that different squads can own different parts. Running an event storming session should allow us to identify everything the platform does, who does it and why it happens.
What will the outcome of the session be?
At the end of the session, we’ll have one wall of the office covered in sticky notes. We can then work out out the bounded contexts, make a list of questions that need answering and assumptions that need checking.
The work then begins to convert the physical board into a miro board in order to share more widely. We’ll also book in quarterly, or half-yearly sessions to ensure it’s up to date.
Who do we need there?
Representatives from various parts of the business
- Tech Seniors
- Tech PMs
- Some Tech QAs
- Ops
- B2B
- B2C
Agenda
- 0930 - 0945 - Introductions and warmups
- 0945 - 1030 - Events mapping
- 1030 - 1045 - Break
- 1045 - 1230 - Triggers and actors mapping
- 1230 - 1330 - Lunch
- 1330 - 1430 - Mop-up and review
- 1430 - 1445 - Close and next steps.