Giovanni Asproni shows how to create a software architecture with just the right amount of design that can be incrementally evolved (or changed) as the system grows and changes.
Kovas Boguta, David Nolen discuss embracing demand-driven architectures to be able to more flexibly accommodate the rapidly transforming needs of the clients.
Hannah Tometzki shares advice from experience on going through the hurdles of project design - customers dragging their feet, rekindling waning enthusiasm and handling distractions.
Robert Reppel considers that architects should build software-centric systems as a user experience for customers, products owners, developers, IT, testers and other participants.
Michael Ong shares an approach that was used in two environments with success to bring products to market with a focus on users while considering business conditions and constraints.
Liz Keogh discusses breaking down requirements without going into too much detail combined with complexity estimation for easy planning, dependency management, and prioritization.
Viviana Doctorovich explains how to use workshops to teach clients the design process using planning, design games and methods for dealing with difficult stakeholders.
Emma Langman explores the usefulness of some of the Quality tools that have been around since the 50s for gathering requirements, tackling repeat problems, or innovating more efficiently as a team.
Barb Spurway, Tracy Bowman discuss Voice of the Customer (VoC), a Total Quality Management/ Lean Manufacturing concept helping teams build quality products from the customers’ perspective.
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
Paul deGrandis emphasizes the importance of using specification-as-a-value, a way of unifying core.contracts, test.generative, and external systems under a single common specification in Clojure.