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.
Matt Barcomb shares practical ideas for generating and validating projects as Real Options, using value models and risk consideration to create a framework for prioritization and decision-making.
Robert Reppel considers that architects should build software-centric systems as a user experience for customers, products owners, developers, IT, testers and other participants.
Brindusa Axon, David Evans debate the pros and cons of using stories and discuss practices and techniques for improving them.
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.
Pieter Hintjens teaches a trick he is using daily to create better software clients.
Allan Kelly examines the project model and shows how it fails to match software development, outlining an alternative to it and advising on what companies need to do to achieve that.
Liz Keogh discusses breaking down requirements without going into too much detail combined with complexity estimation for easy planning, dependency management, and prioritization.
Martin Aspeli shares his experiences using Kanban, Real Options, Conway's Law and Feature Injection to help clients "see" the value stream in their programmes and better align disparate workstreams.
Dimitar Bakardzhiev discusses planning a fixed bid project by applying the Monte Carlo simulation using collected historical data about lead time per story.