Open Agile Architecture
What the domain covers
The Open Agile Architecture (O-AA) domain tests whether you can apply the Open Group's O-AA Standard to architecture work in a continuously changing digital enterprise. Expect questions on how architecture becomes a continuous, product-aligned service rather than a phase-gated documentation exercise, and on the vocabulary that distinguishes O-AA from classic TOGAF-style architecture.
Core rules and concepts
- Agile Architecture is intentional and emergent: architects set guardrails (principles, standards, fitness functions) while allowing teams to discover design through delivery.
- The architecture backlog and architecture runway make architecture work visible and schedulable. The backlog holds architecture enablers, debt, and experiments; the runway provides the foundation for upcoming features without over-designing.
- Architecture is product-centric and value-stream aligned. Architects collaborate with product teams, experience designers, and platform teams rather than issuing isolated mandates.
- Governance shifts from gate reviews to continuous feedback: guardrails, metrics, and lightweight decision records.
- O-AA aligns with TOGAF's ADM but iterates it: architecture vision, backlog, and runway are revisited each increment, not frozen at an endpoint.
Worked example
A retailer wants a new mobile checkout. A phase-gated response would produce a full target-state document before any code. In O-AA, the architect identifies the value stream (checkout), places enablers in the architecture backlog (payment API standards, identity federation, observability), and defines a thin architecture runway (API gateway pattern, event schema, security guardrails). Teams deliver increments; the architect uses fitness functions-latency, PCI scope, error rate-to decide when to evolve the runway. The reasoning: architecture work is prioritized by delivery need and validated by measurable outcomes, not by document completeness.
Traps that cost marks
- Treating O-AA as "no architecture": it still requires intentional guardrails and decisions.
- Confusing architecture backlog with product backlog: backlog items are architecture enablers, debt, and experiments.
- Assuming the runway is a big up-front design; it is the minimum foundation for near-term features.
- Forgetting experience design and value streams; O-AA frames architecture around customer and employee outcomes.