Ücretsiz Kullanmaya Başla

Phase A: Architecture Vision Knowledge-Based Study

TOGAF · Enterprise Architecture Capability and Governance · Foundation · Establishing an Architecture Capability

Foundation topic explanations on Phase A: Architecture Vision.

Study notes

  1. Overview and Purpose

    In the TOGAF Standard, 10th Edition, applying the Architecture Development Method (ADM) to establish or evolve an Enterprise Architecture (EA) Capability treats the capability itself as the subject of the architecture. While the Preliminary Phase defines the organizational context, governance frameworks, and architecture principles, Phase A: Architecture Vision initiates the specific iteration to build or enhance that capability.

    The primary purpose of Phase A in this context is to:

    • Articulate the business value, motivation, and strategic intent for establishing or enhancing the EA Capability.
    • Identify key stakeholders and their concerns regarding architecture practice governance, skills, and funding.
    • Define the high-level scope and constraints of the architecture effort.
    • Obtain formal approval via the Statement of Architecture Work to proceed with detailed capability design.

    Objectives of Phase A

    When standing up an EA Capability, Phase A focuses on establishing consensus among business leaders, IT executives, and operational heads regarding what the capability will deliver.

    Stakeholder Identification and Engagement

    A vital activity in Phase A is identifying stakeholders across business and IT domains. Key focus areas include:

    • Developing the Stakeholder Map: Determining stakeholder power, influence, and interest in architecture governance and decision-making.
    • Understanding Concerns: Capturing expectations related to investment portfolio alignment, digital transformation oversight, risk mitigation, and standards compliance.
    • Creating Readiness Assessments: Evaluating the organization's business readiness for adopting a structured enterprise architecture practice.

    Deliverables Produced in Phase A

    Phase A produces essential deliverables that set the boundary and direction for developing the Architecture Capability:

    • Statement of Architecture Work: The foundational contract between the architecture organization and the sponsoring business leadership. It outlines the scope, budget, schedule, deliverables, and governance metrics for establishing the capability.
    • Architecture Vision: A high-level description of the Target Architecture Capability. It contrasts the baseline capability maturity with the target maturity state and highlights expected business benefits.
    • Communications Plan: A strategy for keeping enterprise leaders, practitioners, and consumers informed throughout the capability rollout.
    • Capability Assessment: An initial baseline evaluation of current architectural maturity, competencies, and tool readiness.

    Key Conceptual Distinctions

    Practitioners must distinguish how Phase A operates when creating an Architecture Capability versus executing a traditional Solution-focused or Enterprise Transformation ADM cycle:

    • Subject Matter: In an Architecture Capability iteration, the "Business Architecture" (Phase B) addresses architecture teams, roles, skills, and governance committees. The "Information Systems Architectures" (Phase C) define repositories, metamodels, and modeling tools.
    • Business Value: Rather than delivering a software platform or operational business process, the Architecture Vision in this context outlines how architecture decision-making improves capital allocation, risk reduction, and strategic alignment.
    • Sponsorship: Executive sponsorship must come from enterprise leaders with authority over governance bodies, enterprise standards, and operating models.