The most effective, lowest cost, lowest risk way to build an effective product is incrementally, one small bit at a time. That thinking applies to everything from product design to architecture. Nonetheless, some still think that a waterfall approach—you must have a product design before you pick an architecture; you must have an architecture before you start coding—is mandatory. It's not. In fact, that approach pretty much guarantees a product that does nothing useful built on top of an overcomplex architecture that slows development and is resistant to change. When agility is required, a big up-front architecture slows you down to the point that even trivial changes are insanely difficult.

In this hands-on workshop, you'll learn how to develop a coherent architecture incrementally as the product definition also evolves in small increments.

You'll learn how to build around a domain-focused metaphor that allows for incremental changes while maintaining coherence throughout. You'll learn a complete process for designing incrementally, starting with user stories and ending up with code. You'll come away with a solid understanding of how to build incremental-friendly architectures (and products).

You'll learn:
* The inspect and adapt cycle.
* The MVP
* The Architecture/Product-Design fit (they are the same thing)
* Using the domain for architectural coherence.
* User Stories (are not what you think)
* Architectural TDD
* Design by Coding and Declarative APIs
* Domain-Focused approaches (including Domain-Driven Design)
* Event Storming for creating choreographed systems.
* Incrementally friendly architectural pattern