Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Why Agile needs more Collaborative Modeling (CoMo)

Avatar for Daniel Sack Daniel Sack
September 15, 2022

Why Agile needs more Collaborative Modeling (CoMo)

Avatar for Daniel Sack

Daniel Sack

September 15, 2022

More Decks by Daniel Sack

Other Decks in Business

Transcript

  1. learning discovering exchanging knowledge creativity working together making experiments creating

    modeling innovating evaluating options deciding Collaborative Modeling exploring including brainstorming leveraging diversity strategizing
  2. ?

  3. Soon after the tickets for the upcoming game are released,

    a customer calls and asks the cashier for a ticket reservation. The cashier tries to find suitable seats in the ticketing system's screen plan and suggests any available seats to the customer, which confirms the suggested seats. The cashier then blocks the confirmed seats in the ticketing system, which now generates a reservation for the seats. The cashier informs the customer about the reservation number, who is happy to hear that the tickets for the upcoming game are now reserved in the system.
  4. Cashier finds suitable seats Cashier Ticketing System Customer calls and

    asks for ticket reservation tries to find suitable seats suggests available seats
  5. Cashier finds suitable seats Cashier Ticketing System Customer calls and

    asks for ticket reservation tries to find suitable seats suggests available seats confirms suggested seats blocks confirmed seats generates reservation informs about reservation number Tickets for upcoming game reserved Customer likes the seats Suggested seats are still available
  6. Support Case Creation Skill based Routing of Support Cases to

    Staff Members Forwarding, Redistribution of Support Cases to other Staff Members More Information on Support Case needed from Customer Tracking of Cases and following up on Cases Closing cases
  7. Support Case Creation Skill based Routing of Support Cases to

    Staff Members Forwarding, Redistribution of Support Cases to other Staff Members
  8. Order information entered Inventory Updated Warehouse notified Shopping cart updated

    Input checks performed Additional offers identified Payment processed Order submitted Multiple offers bundled Tax and shipping calculated Order information entered Inventory Updated Warehouse notified Shopping cart updated Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Example output after identifying missing events (outlined in red) after putting them in sequence Order information entered Inventory Updated Warehouse notified Shopping cart updated Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Example output after identifying what triggers the events, the users and systems involved Webpage User Originations-​ system Offers accepted Offers declined User Accept Decline Add to chart User Offer System Checkout User Inventory System Process payment Fulfill order Warehouse System Visa, MC, American Express Order information entered Inventory Updated Warehouse notified Shopping cart updated Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Example output with aggregates added in and bounded context applied Webpage User Originations-​ system Offers accepted Offers declined User Accept Decline Add to chart User Offer System Checkout User Inventory System Process payment Fulfill order Warehouse System Visa, MC, American Express Order Inventory Order Order Shopping cart Offer Address Payment Inventory Order captured Shopping cart Offers Checkout process Payment processing Order fulfillment EventStorming EventModeling Create a plausible story made of these events Align wireframes or mockups of the story to address those that are visual learners
  9. Order information entered Inventory Updated Warehouse notified Shopping cart updated

    Input checks performed Additional offers identified Payment processed Order submitted Multiple offers bundled Tax and shipping calculated
  10. Order information entered Inventory Updated Warehouse notified Shopping cart updated

    Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Example output after identifying missing events (outlined in red) after putting them in sequence
  11. Order information entered Inventory Updated Warehouse notified Shopping cart updated

    Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Example output after identifying what triggers the events, the users and systems involved Webpage User Originations-​ system Offers accepted Offers declined User Accept Decline Add to chart User Offer System Checkout User Inventory System Process payment Fulfill order Warehouse System Visa, MC, American Express
  12. Order information entered Inventory Updated Warehouse notified Shopping cart updated

    Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Example output with aggregates added in and bounded context applied Webpage User Originations-​ system Offers accepted Offers declined User Accept Decline Add to chart User Offer System Checkout User Inventory System Process payment Fulfill order Warehouse System Visa, MC, American Express Order Inventory Order Order Shopping cart Offer Address Payment Inventory Order captured Shopping cart Offers Checkout process Payment processing Order fulfillment
  13. Focus on details Focus on big picture Big Picture Event

    Storming Process Level Event Storming Design Level Event Modeling Order information entered Inventory Updated Warehouse notified Shopping cart updated Input checks performed Payment processed Multiple offers bundled Tax and shipping calculated Check inventory Order added to chart Promotional offers identified Promotional offers provided Checkout selected Mailing address provided Billing address provided Webpage User Originations-​ system Offers accepted Offers declined User Accept Decline Add to chart User Offer System Checkout User Inventory System Process payment Fulfill order Warehouse System Visa, MC, American Express Order Inventory Order Order Shopping cart Offer Address Payment Inventory Order captured Shopping cart Offers Checkout process Payment processing Order fulfillment Promotional offers identified Promotional offers provided Offers accepted Offers declined User Accept Decline Offer System Offer Offers Shopping cart updated Shopping cart Promotional offers identified Promotional offers provided Offers accepted Offers declined User Accept Decline Offer System Offer Offers Shopping cart updated Shopping cart From "Sopping cart updated" to "Offer accepted" From "Sopping cart updated" to "Offer declined"
  14. Strategic Alignment Big Picture Event Storming Parallel, "chaotic" exploration and

    discovery Large group (5-20 people) from diverse backgrounds Domain & Knowledge Discovery Small focus group (1-3 people) Which result can I expect? What do I need to achieve Which people do I need? Which style can help me? Which method can I use? Customer or User Perspective Domain Story telling Customer or User Journey Simple, end user centric requirements gathering Process Details Process Level Event Storming Process Model Sophisticated, flexible and extensible modeling Dev team with domain expert (3-7 people) Executable Software (Iteration) Design Level Event Modeling Tactical Design Single flow focused design Cross-​ functional team (3-7 people) Solution overview Context Mapping Strategic Design Collaborative mapping of contexts & dependencies Team of teams (3-7 people)
  15. Which result can I expect? What do I need to

    achieve Which people do I need? Which style can help me? Which method can I use?
  16. Strategic Alignment Big Picture Event Storming Parallel, "chaotic" exploration and

    discovery Large group (5-20 people) from diverse backgrounds Domain & Knowledge Discovery
  17. Small focus group (1-3 people) Customer or User Perspective Domain

    Story telling Customer or User Journey Simple, end user centric requirements gathering
  18. Process Details Process Level Event Storming Process Model Sophisticated, flexible

    and extensible modeling Cross-​ functional team (3-7 people)
  19. Dev team with domain expert (3-7 people) Executable Software (Iteration)

    Design Level Event Modeling Tactical Design Single flow focused design
  20. Daniel Sack [email protected] Martin Schimak [email protected] Q&A Architect, Mentor, Coach,

    Developer, ... Expert in Domain Modelling, Solution Design, ... miro.com Agile Tour Vienna 2022 Why Agile Needs More Collaborative Modeling https://bit.ly/atv22CoMo
  21. Cashier finds suitable seats Cashier Ticketing System Customer calls and

    asks for ticket reservation tries to find suitable seats suggests available seats