10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases
Key Takeaways
- 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.
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.
According to the TOGAF Standard, where can guidance on how to do what the ADM specifies be found?
Which Fundamental Content document contains guidelines for adapting the ADM to address the specific style of architecture required in a practical context?
How does iteration enable concurrent operation of multiple ADM phases?
A strategic architecture cycle identifies two segment architectures, each of which starts its own ADM cycle while the strategic cycle continues. What does this illustrate?