Applying the ADM Across the Landscape

Applying the ADM Across the Landscape: Complete Guide for TOGAF 10 Foundation

Introduction

Applying the ADM Across the Landscape is a critical concept in TOGAF 10 that addresses how the Architecture Development Method can be implemented across an organization's entire enterprise architecture landscape. This guide will help you understand this concept thoroughly for your certification exam.

Why This Concept Is Important

Understanding how to apply the ADM across the landscape is essential because:

• Enterprise Scope: Most organizations operate with multiple business units, systems, and domains that require coordinated architectural approaches
• Consistency: Ensures architectural principles and standards are applied uniformly across the enterprise
• Efficiency: Prevents duplicated efforts and promotes reuse of architectural artifacts
• Strategic Alignment: Ensures all architectural initiatives align with overall business strategy
• Governance: Enables proper oversight and control of architectural work across the organization
• Scalability: Provides frameworks for managing architecture at different levels and scales

What Is Applying the ADM Across the Landscape?

Definition: Applying the ADM Across the Landscape refers to the systematic approach of deploying the Architecture Development Method across multiple levels of the enterprise, different business domains, and various architectural concerns.

Key Concept: The ADM can be applied at different levels simultaneously:

• Strategic Level: Enterprise-wide architecture for long-term vision
• Segment Level: Architecture for specific business domains or units
• Capability Level: Architecture for specific business capabilities
• Project Level: Architecture for specific implementation initiatives

Multi-Level Architecture: Rather than treating the ADM as a single linear process, it operates as a framework that enables parallel and sequential architecture cycles at different organizational levels.

How It Works

1. Architecture Hierarchy

The landscape consists of different architectural levels:

• Enterprise Architecture: Highest level, covers entire organization
• Segment Architecture: Focuses on specific business segments or major divisions
• Capability Architecture: Targets specific business capabilities or functions
• Project Architecture: Details for specific implementation projects

2. Parallel and Sequential Execution

Parallel Application: Multiple ADM cycles can run simultaneously at different levels of the organization. For example, while enterprise architecture is in Phase C (Information Systems Architecture), a segment might be in Phase E (Opportunities and Solutions).

Sequential Application: Results from higher-level ADM cycles inform and constrain lower-level cycles. Enterprise decisions establish boundaries for segment-level work.

3. Architecture Landscape Taxonomy

Understanding the landscape structure helps organize ADM application:

• Organizational Units: Different departments or business lines may require tailored architectural approaches
• Geographical Distribution: Different regions may need specific architectural considerations
• Functional Domains: Different business functions may follow different architectural patterns
• Technology Domains: Different technology stacks may require specialized architectural attention

4. Architecture Governance Framework

When applying ADM across the landscape, establish governance that includes:

• Clear escalation paths for decisions across levels
• Architectural review boards at different levels
• Standards and compliance checking mechanisms
• Change management processes
• Documentation and artifact management standards

5. Integration Points

Key integration mechanisms when applying ADM across the landscape:

• Architecture Principles: Consistent across all levels
• Reference Models: Shared across segments for consistency
• Building Blocks: Reusable components across the landscape
• Gap Analysis: Aggregated from lower to higher levels
• Implementation Roadmaps: Coordinated across segments

Practical Implementation Steps

Step 1: Define the Landscape

Identify all architectural levels in your organization and document which ADM phases are active at each level.

Step 2: Establish Governance Structure

Create architectural governance that operates across all levels with clear roles, responsibilities, and decision-making authority.

Step 3: Develop Common Frameworks

Create shared architecture models, standards, and reference architectures that will be used across all levels.

Step 4: Manage Dependencies

Identify and manage interdependencies between architectural work at different levels to ensure consistency and avoid conflicts.

Step 5: Coordinate Implementation

Ensure that implementation roadmaps from different levels are coordinated to prevent conflicts and maximize resource efficiency.

Step 6: Monitor and Control

Establish metrics and monitoring mechanisms to track progress across all architectural levels.

Common Patterns When Applying ADM Across the Landscape

Pattern 1: Top-Down Approach

How it works: Enterprise architecture is developed first, establishing principles and constraints that guide segment and capability-level work.

Best for: Organizations with strong centralized governance and clear strategic direction.

Pattern 2: Bottom-Up Approach

How it works: Segment-level architectures are developed first, then aggregated to inform enterprise architecture.

Best for: Organizations with decentralized decision-making or diverse business units with different needs.

Pattern 3: Hybrid Approach

How it works: Enterprise architecture provides strategic direction, while segments develop detailed architectures that feedback to refine enterprise architecture.

Best for: Most large organizations balancing centralization with autonomy.

Key Considerations for Applying ADM Across the Landscape

• Scalability: The ADM framework must scale to handle multiple concurrent cycles
• Flexibility: Different business units may need different ADM tailoring
• Resource Management: Architecture resources must be allocated and coordinated across multiple levels
• Communication: Clear communication channels must exist between different architectural levels
• Version Control: Architecture artifacts must be versioned and tracked across the landscape
• Change Management: Changes at one level must be evaluated for impact on other levels
• Compliance: All architectural work must comply with organizational standards regardless of level

Exam Tips: Answering Questions on Applying the ADM Across the Landscape

Tip 1: Understand the Multi-Level Structure

What to focus on: Exam questions often test whether you understand that the ADM operates at multiple levels simultaneously. Remember the hierarchy: Enterprise → Segment → Capability → Project.

Common question type: "Which architectural level should address enterprise-wide standards?" Answer: Enterprise Architecture level applies ADM to establish principles for all lower levels.

Tip 2: Recognize the Relationship Between Levels

What to focus on: Higher levels constrain lower levels. Results from lower levels inform refinement of higher levels.

Common question type: "How does enterprise architecture relate to segment architecture?" Answer: Enterprise architecture establishes constraints and principles; segment architecture operates within these parameters while providing detailed implementation within its domain.

Tip 3: Know the Governance Structure

What to focus on: When applying ADM across the landscape, governance mechanisms are critical for ensuring consistency and managing conflicts.

Common question type: "What is needed to manage architectural work across multiple levels?" Answer: Governance framework, architectural review boards at each level, escalation procedures, and compliance mechanisms.

Tip 4: Understand Parallel Execution

What to focus on: Multiple ADM cycles can operate at different phases simultaneously. This is a key differentiator from running ADM once sequentially.

Common question type: "Can different segments be in different ADM phases?" Answer: Yes, each segment can have its own ADM cycle tailored to its needs, though they should align with enterprise architecture principles.

Tip 5: Recognize Artifact Reusability

What to focus on: One major benefit of applying ADM across the landscape is the ability to create reusable building blocks and architecture patterns.

Common question type: "What is a key advantage of landscape-wide ADM application?" Answer: Reusable components, consistent standards, and reduced duplication across the organization.

Tip 6: Watch for Governance vs. Architecture Questions

What to focus on: Distinguish between questions about HOW to apply the ADM (method) versus questions about WHAT governance structures are needed (organizational).

Common question type: "Who is responsible for approving architectural decisions in a multi-level environment?" Answer: Typically different governance boards at different levels, with escalation paths defined.

Tip 7: Look for Dependencies and Conflicts

What to focus on: Questions may ask how to handle situations where segment-level decisions conflict with enterprise principles or where parallel projects might have interdependencies.

Common question type: "What should be done when a segment architecture contradicts enterprise principles?" Answer: The governance framework should address this through change management processes or escalation to appropriate authority.

Tip 8: Remember Architecture Landscape Artifacts

What to focus on: The ADM produces artifacts that must be managed across the landscape including principles, models, standards, and roadmaps.

Common question type: "Which architectural artifacts should be consistent across all landscape levels?" Answer: Architecture principles, reference models, and technology standards should be consistent across the organization while allowing flexibility in implementation details.

Tip 9: Understand Tailoring for Context

What to focus on: While applying ADM across the landscape, the method should be tailored to organizational context without abandoning core principles.

Common question type: "Can the ADM be tailored differently for different segments?" Answer: Yes, the ADM can be adapted to segment-specific contexts while maintaining alignment with enterprise architecture and governance frameworks.

Tip 10: Focus on Practical Coordination

What to focus on: Practical questions about how to coordinate work across multiple concurrent ADM cycles.

Common question type: "How would you manage the interdependency between a segment architecture and enterprise architecture that are both progressing in parallel?" Answer: Establish integration points, regular reviews, escalation procedures, and change impact analysis mechanisms.

Common Exam Question Patterns

Pattern A - Identify Appropriate Level: "Which ADM level is most appropriate for defining how a business capability should be delivered?" Answer: Typically capability or project level, depending on specificity required.

Pattern B - Governance Questions: "What governance structure is needed when applying ADM across multiple business segments?" Answer: Architecture review boards at each level, escalation procedures, compliance mechanisms, and coordination meetings.

Pattern C - Artifact Management: "How should architecture artifacts be managed across the landscape?" Answer: Centralized repository, version control, access controls, and traceability matrices.

Pattern D - Conflict Resolution: "What happens when a project-level decision conflicts with segment-level architecture?" Answer: Follow governance escalation procedures; typically requires change management review.

Pattern E - Integration Points: "What should remain consistent across all landscape levels?" Answer: Architecture principles, governance processes, reference models, and core standards.

Practice Questions

Q1: An organization with three business segments is implementing ADM across the landscape. Enterprise architecture is establishing principles for data governance. What is the primary purpose of sharing these principles across all segments?

Answer: To ensure consistency and prevent redundant work by having all segments operate within the same data governance framework while allowing flexibility in implementation details.

Q2: A segment architecture team discovers that implementing a proposed solution would violate an enterprise architecture principle. What should be the first step?

Answer: Escalate to the appropriate governance body, as defined in the governance framework, rather than proceeding with the violation or independently changing the principle.

Q3: When applying ADM across a landscape with multiple parallel cycles, what prevents chaos and ensures alignment?

Answer: A defined governance framework that includes architectural review boards, escalation procedures, artifact management standards, and regular coordination meetings.

Key Takeaways

• ADM can and should be applied at multiple organizational levels simultaneously
• Higher architectural levels provide constraints and principles for lower levels
• Multiple ADM cycles can execute in parallel if properly governed
• Governance structures are essential for managing landscape-wide architecture work
• Common artifacts and standards should be reused across the landscape
• Dependencies between levels must be actively managed
• Clear escalation and change management processes are critical
• The landscape approach maximizes efficiency and ensures consistency
• Different contexts may require ADM tailoring while maintaining core principles
• Coordination mechanisms must be built into the organizational structure

Conclusion

Applying the ADM Across the Landscape is about orchestrating the Architecture Development Method across an entire enterprise in a coordinated, governed, and efficient manner. Success requires understanding both the hierarchical nature of the landscape and the governance mechanisms needed to manage work at multiple levels. For your exam, focus on the multi-level execution model, the role of governance, artifact consistency, and how decisions at different levels interact. Remember that the landscape approach is not about running the ADM multiple times independently, but about creating an integrated ecosystem where architectural work at all levels is coordinated toward enterprise objectives.