A vibrant 3D illustration of stacked glowing circuit boards connected by bright neural pathways.
To deepen your understanding of “Developing Architecture in an Agile Way” in TOGAF®, let’s explore a practical application example.
The Architecture Landscape in TOGAF® organizes architecture along two dimensions:
This concept enables teams to maintain architectural consistency—even in Agile environments.
At the core of this approach is the three-layer model:
These are not merely hierarchical layers. They form a decomposition and alignment structure that connects strategy directly to Agile delivery.
Quoted from The TOGAF® Standard, 10th Edition
Defines enterprise-wide long-term vision and strategy.
Clarifies the “Why.”
This layer does not directly translate into sprints, but it defines all prioritization criteria.
Do not leave strategy abstract.
It must be defined in a way that allows decomposition into capabilities.
Defines architecture at the business domain or organizational level.
Clarifies the “Where.”
Defines boundaries for:
PLM Segment
SCM Segment
Finance Segment
Each segment is further decomposed into Capabilities.
This is not the same as SAP module decomposition.
❌ Incorrect:
✅ Correct:
Focus on business value streams, not system modules.
Defines architecture at the business capability level.
Clarifies the “What.”
This is the most critical layer directly connected to Agile execution.
Forms the starting point of the backlog:
Capability → Features → User Stories
Capabilities
Features
User Story
Capabilities must be defined in terms of business outcomes, not system functions.
❌ Incorrect:
✅ Correct:
(Strategy → Segment → Capability → Sprint)
Break down strategic themes into business domains.
Example:
Decompose business domains into capabilities.
Example:
Translate capabilities into product modules and features.
Example:
Key actions:
Translate into implementation plans.
Example:
If strategy remains too abstract, it cannot be translated into Agile execution.
Solution:
Decompose strategy down to the capability level and ensure alignment before sprint planning.
Designing based on SAP modules instead of business value.
Solution:
Re-define capabilities based on business requirements.
When segments do not align with business value, team boundaries become unclear.
Solution:
Define segments based on value delivery and organizational accountability.
The essence of TOGAF® Agile is:
“A structured decomposition that enables strategy to flow directly into sprints.”
And most importantly:
“Capability is the bridge to Agile execution.”
By understanding this structure, organizations can maintain architectural consistency while effectively applying Agile in real-world scenarios.
Please refer to this article for topics related to Enterprise Architecture (EA).
Enterprise Architecture – Insight Arc | SAP, Enterprise Architecture & Supply Chain Strategy
Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.
Net present value (NPV) is the go-to metric for evaluating major IT investments. This guide…
Many Architecture Repositories get built, then quietly abandoned. This article explains the eight components defined…
A practical guide to accelerating EA with generative AI: core principles, a 12-week TOGAF ADM…
Forecast and call-off integration, provisional pricing, chargeable subcontracting, kanban, and acceptance matching. This article maps…
ERP implementation in global manufacturing requires critical decisions about ERP scope, surrounding applications, global standardization,…
Measure SAP S/4HANA ROI over just three years and you will mostly see cost. This…