The phrase “agile architecture” evokes two concepts:
- A system or software architecture that is versatile, easy to evolve, and easy to modify, while resilient enough not to degrade after a few changes.
- An agile way to define an architecture, using an iterative lifecycle, allowing the architectural design to tactically evolve over time, as the problem and the constraints are better understood.
In the best of worlds, we’d like to have an agile process that leads to a flexible architecture.
This half-day tutorial enables attendees to understand basic architecture concepts that developers use to develop large-scale systems in an agile lifecycle. Attendees who complete the tutorial should be able to understand the business case for architecture, architecture essentials, and architecting with just enough anticipation as an enabler for agile at scale.
Topics:
- Agile and architecture
- Business case for architecture (why?, cost, risk, quality, efficacy)
- Architecture essentials (what?, artifact), (who?, architect, organization roles and responsibilities), (how? practices)
- Architecting over time (when? just in time, iterative and incremental, release planning, road mapping)
- Architecture as an enabler (large scale agile)
