Developing Architecture in an Agile Way with TOGAF®: Practical Application and Key Insights

---

Enterprise architecture and agile development often appear at odds — the former structured and principle-driven, the latter flexible and iterative. However, TOGAF’s “Developing Architecture in an Agile Way” provides practical guidance on how to harmonize both worlds.

If you’ve read the TOGAF® documentation but still struggle to visualize how to apply it in real projects, you’re not alone. This article breaks down how to translate this concept into tangible steps for daily practice, especially in large-scale enterprise or manufacturing environments.

---

1. The Purpose of “Developing Architecture in an Agile Way”

This guidance aims to integrate agile methods (Scrum, SAFe, etc.) with TOGAF’s Architecture Development Method (ADM) by enabling:

• Coexistence of agile iteration cycles and structured ADM phases.
• Avoidance of big-design-upfront while ensuring architectural coherence and governance.
• A mechanism to deliver Just Enough / Just in Time architecture for agile teams.
• Bridging enterprise-level architecture principles and standards with product-level agile execution.

In essence, it helps enterprises build architecture that evolves incrementally — aligned with business value flow and iteration cadence.

---

2. Core Components of Agile Architecture under TOGAF® 10th

TOGAF® 10th and related Enabling Enterprise Agility guidance outline several key practices:

• Agile-aligned ADM: Use ADM phases A–H iteratively, focusing only on necessary parts each cycle. Convert outputs into epics, initiatives, or architecture backlog items.
• Architecture Backlog: Manage decisions, constraints, and technical debt as backlog items prioritized by business value, risk, and dependency.
• Just Enough / Just in Time Architecture: Define minimal architecture before each sprint; refine details in future iterations leveraging reference architectures and reusable patterns.
• Lightweight Governance: Embed compliance checks into sprint reviews or inception workshops. Enforce non-functional requirements through “Definition of Done” checklists.
• Roles & Collaboration:
  • Enterprise Architects maintain standards, principles, and reference models.
  • Solution/Product Architects co-design with agile teams.
  • Agile Teams integrate architecture backlog items into their product backlog seamlessly.

---

3. Practical Application Process

A simplified approach to blending TOGAF® ADM with Agile workflows:

1. Preparation & Principles (Preliminary + Early Phase A):
   Define enterprise vision, architecture principles, and reference models. Identify “architecture epics” and create an initial architecture backlog.
2. Scope Slicing:
   Decide which ADM elements to elaborate based on business value units (e.g., product increments or release trains). Initial iterations might cover only business and high-level technical architecture.
3. Iterative Architecture Activities:
   • Iteration 0 / Inception: Define vision, major components, and non-functional boundaries.
   • Before Each Sprint: Select relevant architecture items for the sprint backlog.
   • During Sprint: Architects co-design and log architectural decisions.
   • After Sprint: Review and improve architecture practices via retrospectives.
4. Continuous Governance & Refactoring:
   Capture key architecture decisions as ADRs or TOGAF® artifacts (catalogs, matrices, diagrams). Reassess technical debt regularly and plan architecture improvement epics.

---

4. Common Use Cases in Practice

• Enterprise Platforms (e.g., API, Data Hub, MDM): Shared foundations designed within SAFe or large-scale agile frameworks.
• Legacy Modernization (Monolith to Cloud/Microservices): TOGAF® provides the overarching “As-Is/To-Be” view while migration happens per microservice sprint.
• Global ERP / Core System Rollouts: Core templates designed with TOGAF® discipline, deployed through agile increments.
• Solution Architecture within Product Teams: Unified lightweight templates to maintain consistency.

---

5. Key Considerations for Real-World Adoption

• Don’t apply TOGAF® ADM “as-is” — tailor phases and artifacts.
• Drive architecture via backlog — treat architecture work as user stories.
• Align with sprint timelines — use spikes or PoCs for exploration.
• Embed non-functional standards in Definition of Ready / Done.
• Avoid separation between EA and agile teams — encourage shared governance.

---

Developing Architec6. Where to Start

In manufacturing or other complex industries, a pragmatic start includes:

• Assess current architecture maturity and define tailoring strategy.
• Prototype an architecture backlog.
• Pilot with one product team.
• Establish minimal viable governance and standard sets.
• Build learning and feedback loops early.

---

Summary

TOGAF’s “Developing Architecture in an Agile Way” is not about forcing TOGAF® onto agile teams. It’s about evolving architecture with agility.

Key takeaways:

• Architecture evolves continuously — not a one-time blueprint.
• Tailor ADM phases for iterative delivery.
• Treat architecture as a managed backlog aligned with business objectives.

Applying these principles enables enterprises to balance speed and control, ensuring sustainable digital transformation.

Please refer to this article for topics related to Enterprise Architecture (EA).
Enterprise Architecture – Insight Arc | SAP, Enterprise Architecture & Supply Chain Strategy

---

Reference Links

• The Open Group TOGAF® Standard, 10th Edition
• TOGAF Series Guide: Enabling Enterprise Agility
• TOGAF Series Guide: Applying the ADM Using Agile Sprints
• Scaled Agile Framework (SAFe) Official Site
• The Agile Manifesto

---

Disclaimer

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.

---

Back to Top