TOGAF 10 and the Architecture Development Method
The TOGAF Standard 10th Edition structure, every ADM phase with inputs and outputs, how to tailor TOGAF for agile organizations, and how it compares with other frameworks.
[!FACT] The TOGAF Standard, 10th Edition was released by The Open Group in April 2022. It splits content into the Fundamental Content (stable core: ADM, concepts, governance) and the Series Guides (practical guidance on topics such as agile, digital, security, business architecture), making it more modular than TOGAF 9.2.
The ADM cycle
flowchart TB P[Preliminary<br/>framework, principles, capability] --> A A[A. Architecture Vision] --> B[B. Business Architecture] B --> C[C. Information Systems<br/>Data + Application] C --> D[D. Technology Architecture] D --> E[E. Opportunities & Solutions] E --> F[F. Migration Planning] F --> G[G. Implementation Governance] G --> H[H. Architecture Change Management] H --> A RM((Requirements<br/>Management)) --- A & B & C & D & E & F & G & H
| Phase | Purpose | Key outputs |
|---|---|---|
| Preliminary | Set up the architecture capability: scope, framework tailoring, principles, governance, tools | Organizational model for EA, tailored framework, architecture principles |
| A. Architecture Vision | Define scope, stakeholders, business goals and a high-level target vision; secure approval | Statement of Architecture Work, Architecture Vision, stakeholder map |
| B. Business Architecture | Baseline and target business: capabilities, value streams, processes, organization | Business architecture, gap analysis, capability map |
| C. Information Systems | Data and application architectures | Data models, data flows, application portfolio and interactions |
| D. Technology Architecture | Platforms, infrastructure, technology standards | Technology architecture, standards, gap analysis |
| E. Opportunities & Solutions | Consolidate gaps into work packages; identify transition architectures; build vs buy | Implementation and migration strategy, work packages |
| F. Migration Planning | Sequence and cost the roadmap; value and risk | Architecture roadmap, implementation and migration plan |
| G. Implementation Governance | Ensure projects conform to the architecture | Architecture contracts, compliance reviews |
| H. Change Management | Monitor changes in business and technology; decide when to start a new cycle | Change requests, updated architecture |
| Requirements Management | Continuous: capture and route requirements through all phases | Requirements repository |
Core concepts
- Architecture Repository: models, standards, reference architectures, governance log.
- Enterprise Continuum: from generic foundation architectures to organization-specific ones.
- Architecture Content Framework: deliverables, artifacts (catalogs, matrices, diagrams) and building blocks (architecture building blocks vs solution building blocks).
- Architecture Capability Framework: the organization, roles and skills to run EA.
Tailoring TOGAF for agile organizations
- Run the ADM at different levels (strategic, segment, capability) and iterate quickly; not every project needs every phase.
- Produce "just enough" artifacts that inform decisions: capability maps, target state diagrams, roadmaps, ADRs.
- Embed architecture in product teams (enabling architects) and use lightweight governance (guardrails, automated checks).
- The TOGAF Series Guide on agile explicitly addresses using the ADM with agile delivery.
Comparison with other frameworks
| Framework | Focus |
|---|---|
| Zachman | Ontology/classification of architecture artifacts (what/how/where/who/when/why × perspectives) |
| ArchiMate | Modeling language (also from The Open Group), often used with TOGAF |
| FEAF | US federal EA framework |
| SAFe (Enterprise Architect role) | Architecture within scaled agile delivery |
| C4 model | Lightweight software architecture diagrams (context, containers, components, code) |
Architect-level considerations
[!EA] Use TOGAF as a toolkit, not a process to impose. Measure EA by outcomes: reduced duplication, faster delivery, risk reduction, cost savings, not by documents produced.
Interview questions and answers
Walk me through how you would apply the ADM to a cloud transformation.
Preliminary: define principles (cloud-first, managed services preferred) and governance. A: vision with business goals (agility, cost, resilience) and scope. B: map capabilities affected and value streams. C: assess application portfolio (7 Rs) and data residency. D: target platform (landing zone, standards). E: group into migration work packages and transition architectures. F: roadmap with waves, costs and benefits. G: architecture compliance in each migration project. H: adjust as business priorities and cloud services change.
Is TOGAF still relevant with agile and product teams?
Yes, as a shared vocabulary and toolbox for enterprise-level decisions (capabilities, portfolio, roadmaps, governance), tailored to be iterative and lightweight. It is not meant to dictate how teams build software sprint by sprint.