In 30 seconds
- Balances intentional architecture with emergent design.
- Works with teams, often hands-on, not from an ivory tower.
- Focuses on decisions that are expensive to change.
What changes in agile
| Traditional | Agile |
|---|---|
| Big design up front | Just enough design, evolving |
| Documents handed over | Decisions made with teams |
| Architect separate from code | Often codes or pairs with teams |
Main responsibilities
- Identify costly-to-change decisions and make them deliberately
- Keep the architecture simple and documented just enough
- Guide teams on cross-cutting concerns like security and scale
- Let the rest emerge through emergent design
Signs it's working
Teams can change and release independently, decisions are recorded with their reasons, and architecture work appears in the backlog like any other work. In SAFe, a related role is the System Architect.
Myth vs reality
Myth · Agile teams don't need architects.
Reality · They need architecture; someone has to guide it.
Myth · Architects shouldn't write code.
Reality · Hands-on architects make more grounded decisions.
Myth · Architecture is done once.
Reality · It evolves with the product.
FAQ
What's an architecture decision record?
A short note of a decision, its context and its consequences.
How much up-front design is enough?
Enough to avoid costly mistakes, no more.
Is the architect part of the Scrum team?
Often a developer on the team, or a guide across several teams.