Abstract: 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 Declan 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 iterative plan for your product, both functionally and architecturally.
Learning Outcomes: - What is Evolutionary Architecture and why it is essential
- How to balance evolvability with the other capabilities architecture provides
- The factors that enable or limit the evolvability of an architecture
- Patterns (and anti-patterns) for evolutionary architecture, in green-field and legacy systems