Event Storming Session: Retail Order Management System

Date: [Insert Date]
Facilitator: [Your Name]
Participants:

1. Product Owner
2. Business Analyst
3. Software Engineers
4. UX Designer
5. Customer Service Representative
6. Warehouse Manager
   Tools Used: Sticky notes and a large whiteboard (if in-person) or an online tool like Miro or MURAL (if remote)

---

Objective

1. Identify and map out the key events, commands, and processes involved in managing a retail order from start to finish.
2. Understand the flow of information and how different components of the system interact.
3. Uncover gaps, inefficiencies, and opportunities for automation or improvement.

---

Preparation

1. Prepare a brief overview of Event Storming for participants who may not be familiar with the concept.
2. Gather materials, such as colored sticky notes or set up the digital collaboration space.
3. Define the main goal: Designing a comprehensive flow for the Order Management System.

---

Agenda

1. Introduction (10 minutes)
   • Welcome participants and explain the purpose of the Event Storming session.
   • Provide an overview of the order management process and the key outcomes expected from the session.
   • Explain the use of different colored sticky notes:
     • Orange: Domain events (e.g., “Order Placed”)
     • Blue: Commands (e.g., “Process Payment”)
     • Yellow: External systems (e.g., “Payment Gateway”)
     • Pink: Issues or questions (e.g., “What if the payment fails?”)
2. Identify Domain Events (30 minutes)
   • Ask participants to brainstorm and write down events that occur in the order management process on orange sticky notes.
   • Place events on the whiteboard in chronological order.
   • Examples of Domain Events:
     • “Order Created”
     • “Payment Processed”
     • “Inventory Reserved”
     • “Order Shipped”
     • “Order Delivered”
   • Discuss and refine the event order, ensuring everyone agrees on the flow.
3. Add Commands (30 minutes)
   • Identify the commands that trigger these events and write them on blue sticky notes.
   • Examples of Commands:
     • “Submit Order”
     • “Charge Credit Card”
     • “Reserve Inventory”
     • “Dispatch Order”
   • Place commands before the corresponding events on the whiteboard.
4. Identify External Systems and Actors (20 minutes)
   • Discuss which external systems or actors are involved and add them using yellow sticky notes.
   • Examples:
     • “Customer” (actor)
     • “Payment Gateway” (system)
     • “Warehouse Management System” (system)
   • Draw lines or arrows to show interactions between events, commands, and external systems.
5. Uncover Issues and Questions (20 minutes)
   • Encourage participants to identify any potential issues, risks, or questions and write them on pink sticky notes.
   • Examples of Issues:
     • “What happens if the payment is declined?”
     • “How do we handle out-of-stock items?”
   • Place these issues near the relevant events or commands and discuss possible solutions.
6. Identify Business Rules and Policies (20 minutes)
   • Discuss any rules or policies that influence the process, such as return policies or inventory thresholds.
   • Document these on the whiteboard and discuss how they impact the event flow.
7. Review and Refine the Flow (30 minutes)
   • Walk through the entire flow from start to finish, making sure everything makes sense and there are no gaps.
   • Make any necessary adjustments based on participant feedback.
   • Take photos of the completed whiteboard or export the digital board for documentation.
8. Wrap-Up and Next Steps (10 minutes)
   • Summarize the key findings and decisions made during the session.
   • Discuss the next steps, such as creating detailed user stories, refining the process further, or beginning development.
   • Thank participants for their valuable contributions.

---

Key Outputs

1. Event Flow: A comprehensive visual map of all events, commands, and interactions in the order management process.
2. Identified Issues: List of potential issues or questions that need further investigation.
3. Business Rules: Documentation of rules and policies that influence the system.
4. Next Steps: A clear plan for refining requirements and moving forward with design and development.

---

Example Flow from the Session

1. Event: “Order Created”
   • Command: “Submit Order”
   • External System: Customer
2. Event: “Payment Processed”
   • Command: “Process Payment”
   • External System: Payment Gateway
3. Event: “Inventory Reserved”
   • Command: “Reserve Inventory”
   • External System: Warehouse Management System
4. Event: “Order Shipped”
   • Command: “Dispatch Order”
5. Event: “Order Delivered”
   • Command: “Confirm Delivery”

---

Follow-Up Actions

1. Document the results of the Event Storming session and share them with the team.
2. Schedule a follow-up meeting to address unresolved issues or questions.
3. Begin creating detailed requirements and design documents based on the event flow.