Study guide

10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases

TOGAF Enterprise Architecture Foundation OGEA-101

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Enterprise Architecture & the TOGAF Standard

1.1 The Enterprise, the Purpose of EA & Its Benefits 1.2 Why the TOGAF Standard: Framework, Documentation Set & Certification 1.3 The Four Architecture Domains & Architecture Abstraction

2 Chapter 2: Enterprise Continuum, Architecture Repository, Content Framework & Capability

2.1 The Enterprise Continuum 2.2 The Architecture Repository 2.3 The TOGAF Content Framework & Enterprise Metamodel 2.4 Architecture Capability

3 Chapter 3: Key TOGAF Terminology

3.1 Terms for Architecture Domains, Levels, States & Capability 3.2 Terms for Work Products, Models, Requirements & Change

4 Chapter 4: ADM Fundamentals, Preliminary Phase & Phase A

4.1 The ADM Cycle, Its Phases & Information Flow 4.2 Draft vs. Approved Deliverables & the Iterative ADM 4.3 Governing EA, Scoping the Architecture & Alternatives 4.4 The Preliminary Phase 4.5 Phase A: Architecture Vision

5 Chapter 5: Architecture Definition — Phases B, C & D

5.1 Phase B: Business Architecture 5.2 Phase C: Information Systems Architectures — Data & Application 5.3 Phase D: Technology Architecture

6 Chapter 6: Opportunities, Migration Planning & Implementation Governance (Phases E, F & G)

6.1 Phase E: Opportunities & Solutions 6.2 Phase F: Migration Planning 6.3 Phase G: Implementation Governance

7 Chapter 7: Phase H, Requirements Management & Agile Delivery

7.1 Phase H: Architecture Change Management 7.2 Requirements Management 7.3 Supporting Agile Software Development with the ADM

8 Chapter 8: ADM Techniques I — Guidelines, Principles, Business Scenarios & Gap Analysis

8.1 ADM Guidelines & Techniques and Architecture Principles 8.2 Business Scenarios 8.3 Gap Analysis

9 Chapter 9: ADM Techniques II — Interoperability, Transformation Readiness & Risk

9.1 Interoperability 9.2 Business Transformation Readiness Assessment 9.3 Risk Management

10 Chapter 10: Applying the ADM

10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases 10.2 The Architecture Landscape: Strategic, Segment & Capability Levels 10.3 Architecture Partitioning 10.4 The Four Purposes of Architecture 10.5 Applying the TOGAF Standard in the Digital Enterprise

11 Chapter 11: Architecture Governance

11.1 Architecture Governance: Concept & Benefits 11.2 The Architecture Board 11.3 Architecture Contracts 11.4 Architecture Compliance

12 Chapter 12: Architecture Content

12.1 Stakeholders, Concerns, Views & Viewpoints 12.2 Building Blocks: ABBs & SBBs 12.3 ADM Deliverables I: Preliminary Phase and Architecture Vision 12.4 ADM Deliverables II: From Architecture Definition to Change

10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases

Key Takeaways Explain This Topic AI

The TOGAF Core Concepts chapter states that guidance on how to do what the ADM specifies can be found in the TOGAF Series Guides.

The Applying the ADM document gives guidelines for adapting the ADM, covering iteration, the Architecture Landscape, and architecture partitioning.

Iteration lets ADM phases operate concurrently, for example developing Business, Data, Application, and Technology Architecture together.

The ADM can run as a hierarchy of concurrent cycles at strategic, segment, and capability levels, each constrained by the level above.

TOGAF adapts to architectural styles mainly by adjusting models, viewpoints, and tools rather than changing the framework.

Last updated: September 2026

10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases

"Introduction to Applying the ADM" is worth 4 of 40 questions . This section covers two learning outcomes: describe where guidance on how to apply the TOGAF Standard is provided , and explain how iteration within the ADM enables concurrent operation of multiple ADM phases .

Where Guidance on Applying the TOGAF Standard Is Provided

The TOGAF Standard separates what should be done from how to do it:

Source What it provides

The TOGAF Standard — Architecture Development Method Recommendations on what may be done to define and deploy an Enterprise Architecture

The TOGAF Standard — Applying the ADM (Fundamental Content) Guidelines for adapting the ADM to address the specific style of architecture required in a practical context: applying iteration, applying the ADM across the Architecture Landscape, and architecture partitioning

The TOGAF Standard — ADM Techniques (Fundamental Content) Techniques used when applying the TOGAF approach and the ADM

TOGAF Series Guides The guidance part of the standard. The Core Concepts chapter states that guidance on how to do what is specified can be found in the TOGAF Series Guides

The TOGAF Library White Papers, Guides, and other resources classified to support practical application

Examples of Series Guides that explain how to apply the standard include A Practitioners' Approach to Developing Enterprise Architecture Following the TOGAF ADM , The TOGAF Leader's Guide to Establishing and Evolving an EA Capability , Enabling Enterprise Agility , Applying the ADM Using Agile Sprints , Using the TOGAF Standard in the Digital Enterprise , and Integrating Risk and Security within a TOGAF Enterprise Architecture .

Architecture Styles

The TOGAF framework is designed to be used with various architectural styles . An architectural style is "the combination of distinctive features related to the specific context within which architecture is performed or expressed." To support a style, the practitioner first identifies its distinctive features and then decides how they will be addressed — usually by adjusting the models, viewpoints, and tools used, not by making significant changes to the TOGAF framework.

How Iteration Enables Concurrent Operation of ADM Phases

The ADM is iterative over the whole process, between phases, and within phases (Section 4.2), and it does not mandate a fixed sequence. That flexibility is what allows multiple phases, and multiple ADM cycles, to operate at the same time .

The Four Iteration Cycles

Iteration cycle Phases Enables concurrency by

Architecture Capability Preliminary, A Adjusting the approach, principles, scope, vision, and governance while architecture work proceeds

Architecture Development B, C, D Cycling through or integrating the Business, Information Systems, and Technology phases rather than finishing each in turn

Transition Planning E, F Iterating between opportunity identification and migration planning to create change roadmaps

Architecture Governance G, H Governing implementation and managing change continuously while new architecture work continues

Iteration Within an ADM Cycle

Within one cycle, phases can overlap. For example, Business, Data, Application, and Technology Architecture work can progress together, with each domain's findings feeding the others; Phases E and F can iterate as costs and priorities become clearer; and implementation governance (Phase G) can run for one Transition Architecture while planning (Phases E and F) continues for the next. Within Architecture Development iterations, the team can take a Baseline First or Target First approach.

Iteration Between ADM Cycles

The ADM can also be applied at different levels at the same time, forming a hierarchy of ADM processes . A cycle developing a Strategic Architecture identifies and prioritizes Segment Architecture work; each segment cycle can in turn initiate Capability Architecture cycles. These cycles run concurrently, each within the direction and constraints set by the level above, and their results feed back up.

Classes of Architecture Engagement

The Applying the ADM guidance also describes how architecture engagements differ depending on where they sit in the change lifecycle — for example, engagements that identify required change (supporting strategy and portfolio decisions), engagements that define change (for a program or project), and engagements that support implementation of change . Each class calls for a different depth and speed of ADM iteration.

Scenario: Three Cycles at Once

A government department runs a strategic ADM cycle to set a five-year digital services direction. It launches two segment cycles — citizen services and back-office finance — which run in parallel. Within citizen services, a capability cycle for online identity is already in Phase G, governing implementation of Transition Architecture 1, while the same team works in Phases E and F on Transition Architecture 2. The Architecture Board uses the strategic architecture to resolve a conflict between the two segments over a shared payments service. Iteration makes all of this work concurrently without abandoning governance.

Common Exam Pitfalls

Thinking all guidance is in the ADM chapter. The ADM says what ; Applying the ADM, ADM Techniques, and the Series Guides show how .

Assuming only one ADM cycle can run at a time. Cycles can operate concurrently at strategic, segment, and capability levels.

Using the name "Architecture Definition iterations." The TOGAF term is Architecture Development iterations.

Believing architecture styles require rewriting TOGAF. Styles are addressed mainly by adjusting models, viewpoints, and tools.

Loading diagram... A Hierarchy of Concurrent ADM Cycles