frameworks
TOGAF ADM: Architecture Development Method
The ADM is an iterative method for developing enterprise architecture, consisting of nine phases that guide architects through the complete architecture lifecycle.
TOGAF ADM: Architecture Development Method
TL;DR
The Architecture Development Method (ADM) is TOGAF's core process for developing enterprise architecture. It's an iterative, cyclical method with 9 phases: Preliminary + Phases A through H, plus Requirements Management at the center. The ADM is designed to be adapted—use what fits your organization's maturity and context.
Key Takeaways
- Iterative, not waterfall: Cycle through phases multiple times at different levels of detail
- Requirements-driven: Requirements Management is continuous and central to all phases
- Adaptable: Tailor the ADM to your organization's size, maturity, and culture
- Deliverable-focused: Each phase produces specific artifacts and outputs
- Governance-integrated: Architecture governance is embedded throughout the process
Why the ADM Matters
The ADM provides a structured, repeatable approach to enterprise architecture that:
- Ensures business and IT alignment through explicit traceability
- Reduces risk through stakeholder engagement and iterative validation
- Enables reuse of architecture assets across projects
- Provides a common vocabulary for architecture teams
- Supports governance and compliance requirements
Adoption Reality
Most organizations don't implement all ADM phases with full rigor. Successful EA practices adapt the ADM to their context, often combining phases or simplifying deliverables while maintaining the core principles.
ADM Overview Diagram
Phase-by-Phase Deep Dive
Purpose: Define the architecture capability, principles, and governance framework before starting architecture development.
Key Activities:
- Define the enterprise scope and affected stakeholders
- Confirm governance and support frameworks
- Define architecture principles
- Select and tailor the architecture framework (ADM)
- Implement architecture tools
Key Deliverables:
| Deliverable | Description |
|---|---|
| Architecture Principles | Foundational beliefs guiding decisions |
| Organizational Model for EA | Roles, responsibilities, governance |
| Tailored Architecture Framework | Customized ADM and content framework |
| Architecture Repository | Initial structure for architecture assets |
Success Criteria:
- Executive sponsorship confirmed
- EA team structure defined
- Governance processes established
- Initial principles documented and approved
ADM Iteration Strategies
The ADM supports different iteration approaches:
Architecture Landscape Iterations
Purpose: Maintain broad, enterprise-wide architecture Scope: All domains at conceptual level Frequency: 12-24 month cycles
Architecture Capability Iterations
Purpose: Develop specific capability areas in depth Scope: Single domain or capability Frequency: 3-6 month cycles
Architecture Governance Iterations
Purpose: Support project compliance Scope: Solution-level architecture Frequency: Aligned with project lifecycle
Agile Integration
Many organizations run ADM iterations aligned with SAFe Program Increments (PIs) or quarterly planning cycles, using "Architecture Runway" concepts to ensure architecture enables delivery.
Common Pitfalls
What to Avoid
1. Analysis Paralysis
- Spending months in Phases A-D without delivering value
- Fix: Time-box phases, focus on decisions not documentation
2. Ivory Tower Architecture
- Creating architecture in isolation from delivery teams
- Fix: Embed architects in agile teams, iterate based on feedback
3. Boiling the Ocean
- Trying to architect everything at once
- Fix: Prioritize high-value domains, iterate incrementally
4. Ignoring Governance
- Creating architecture without compliance mechanisms
- Fix: Establish lightweight but consistent governance from the start
5. Technology-First Thinking
- Jumping to Phase D without completing B and C
- Fix: Start with business outcomes, trace to technology
Related Topics
- Prerequisites: What is Enterprise Architecture?
- Next Steps: TOGAF Architecture Domains
- Cloud Integration: AWS Well-Architected
Quick Reference Card
ADM Phases at a Glance
PRELIMINARY Establish EA capability, principles, governance
PHASE A Architecture Vision - high-level goals and scope
PHASE B Business Architecture - capabilities and processes
PHASE C Information Systems - data and applications
PHASE D Technology Architecture - platforms and infrastructure
PHASE E Opportunities & Solutions - work packages and transitions
PHASE F Migration Planning - prioritized roadmap
PHASE G Implementation Governance - compliance oversight
PHASE H Change Management - maintain and evolve architecture
REQUIREMENTS Continuous throughout all phases
KEY PRINCIPLE: Iterate at multiple levels (landscape, capability, project)