Domain-Driven Prototyping Build your product backlog the Aristotelian way: bottom-up, outside-in and from the future
Some say βpeople donβt know what they want until you show it to themβ. Ready to challenge this famous quote?
Imagine you could play a role in a mob-driven design experiment using a progressive example either from your own life or your prefered DDD book. What if youβre invited to suggest, elicit, design and test features in an unpredictable order?
Then how bold would it be to bring together knowledge crunching and bounded contexts, domain modeling and proof-based acceptance criteria, handmade diagrams, event-based living specs and #no/lowcode while exploring the 3 Aristotelian unities: time, space and plot?