People are generally not great at understanding abstractions or novel ideas when we’re first exposed to them, but we’re pretty good at deriving abstractions or concepts given enough concrete examples. Including examples in requirements (whether that is by user stories, specifications or something else), will help teams understand the purpose of a requirement and lead to creative solutions.

Join Chris and Shawn in this interactive session, as they demonstrate why including examples is useful and what makes an example effective. Learn how adding a few examples can help illuminate the purpose of a requirement and how it helps start conversations into unexplored areas. Learn about the various tools and frameworks that support automating examples. See how team members and stakeholders can work together to develop examples that can lead to unexpected solutions.

In Agile you should start with the simplest thing that will give you value, and iteratively build on top of that. But how does that work with a Legacy Enterprise Application that everyone is terrified to touch? Or what if we need to build an application that handles millions of transactions a day? How can we make sure that our architecture will meet our needs two years from now, when we don’t know what the application will look like? And how does the process of architecture work in an Agile environment?

Join Chris and Shawn in this interactive session, as they explore these topics. Learn architectural patterns that allow you to evolve your architecture. Examine techniques to help you work with legacy apps and dependencies. Learn how good architecture allows us to manage technical risk. See how business and technical people can work together to build an incremental plan for your product.