3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition

Executive Summary: Phase A of the TOGAF ADM establishes project boundaries, identifies key stakeholders and business requirements, develops the Architecture Vision, and secures formal executive authorization via the Statement of Architecture Work.

1. Objectives of Phase A: Architecture Vision

Phase A initiates an iteration of the Architecture Development Method (ADM). Its primary purpose is to define the scope of the architecture effort, gain executive buy-in, and construct a high-level representation of the Baseline and Target Architectures.

The core objectives of Phase A include:

• Scope Definition: Establishing organizational, business domain, time horizon, and architectural depth limits for the architecture project.
• Business Goal Alignment: Ensuring the architecture directly addresses executive business drivers, strategic goals, and operational constraints.
• Executive Authorization: Obtaining formal agreement and funding through the approved Statement of Architecture Work.
• Architecture Vision Formulation: Articulating a clear, compelling vision of the Target Architecture and its projected business value.
• Stakeholder Engagement: Systematically mapping stakeholders, uncovering their concerns, and determining required views and viewpoints.

---

2. Core Deliverables of Phase A

Phase A produces two foundational deliverables that govern subsequent ADM phases:

The Statement of Architecture Work serves as the formal project charter. No detailed architectural design (Phases B through D) should proceed without an approved Statement of Architecture Work, as it protects the architecture team from scope creep and ensures budget allocation.

---

3. Systematic Stakeholder Management

Stakeholder management is a critical success factor in Enterprise Architecture. A stakeholder is an individual, team, or organization with an interest in or concerns regarding the outcome of the architecture.

The Power/Interest Grid

TOGAF recommends classifying stakeholders using a 2x2 matrix based on their level of power (authority) and interest (concern regarding outcomes):

1. High Power / High Interest (Key Players - Manage Closely): Executive sponsors, CIO, CFO, major business unit heads. Require active involvement and frequent consultation.
2. High Power / Low Interest (Keep Satisfied): Board members, compliance officers, regulatory bodies. Must be kept satisfied to prevent project blockages.
3. Low Power / High Interest (Keep Informed): End users, operational staff, domain specialists. Should be kept informed via regular updates to build buy-in.
4. Low Power / Low Interest (Monitor): Peripheral groups, general IT staff. Require minimal effort and basic monitoring.

                  HIGH POWER
          +-------------------+-------------------+
          |  Keep Satisfied   |  Manage Closely   |
          |  (e.g. Board,     |  (e.g. Sponsor,   |
          |   Compliance)     |   CIO, CFO)       |
POWER     +-------------------+-------------------+
          |     Monitor       |   Keep Informed   |
          |  (e.g. Peripheral |  (e.g. End Users, |
          |   Staff)          |   Operational)    |
          +-------------------+-------------------+
                   LOW          HIGH
                        INTEREST

Views and Viewpoints

To address stakeholder concerns effectively, architects must distinguish between views and viewpoints:

• Viewpoint: The perspective, template, or schema from which a view is constructed. It defines the conventions, notation, and modeling techniques (e.g., Security Viewpoint, Capability Viewpoint).
• View: The actual representation of a specific system from the perspective of a viewpoint, tailored to address specific stakeholder concerns.

---

4. Business Scenarios Technique in Phase A

Phase A utilizes the Business Scenarios technique to derive clear, un-ambiguous business requirements. A business scenario is a structured narrative describing a business problem, the environment in which it occurs, the actors involved, and the desired outcome.

By engaging business leaders in scenario modeling during Phase A, architects ensure that the Architecture Vision addresses concrete business capabilities rather than abstract IT concepts.

---

5. Phase A Execution Flow: Inputs, Steps, and Outputs

Key Inputs

• Request for Architecture Work: Sent by sponsoring organization to initiate the architecture project.
• Business Principles, Goals, and Drivers: High-level strategic statements defining enterprise direction.
• Enterprise Continuum: Existing architectural assets, reference models, and organizational standards.
• Organizational Model for Enterprise Architecture: Defined architecture capability, roles, and governance from Preliminary Phase.

Detailed Steps

1. Establish the Architecture Project: Confirm team composition, resources, and governance environment.
2. Identify Stakeholders, Concerns, and Business Requirements: Develop Stakeholder Map and document concerns.
3. Confirm and Elaborate Business Goals, Drivers, and Constraints: Validate strategic alignment.
4. Evaluate Business Capabilities: Assess current capability strengths, weaknesses, and maturity gaps.
5. Assess Readiness for Business Transformation: Measure organizational change readiness and risk.
6. Define Scope: Establish boundaries across enterprise units, architecture domains, and timeframes.
7. Confirm Architecture Principles: Review and adapt business and architecture principles.
8. Develop Architecture Vision: Create executive summaries, baseline/target concepts, and solution options.
9. Define Value Propositions and KPIs: Document quantitative business outcomes and metrics.
10. Identify Business Transformation Risks: Conduct initial risk assessment and mitigation planning.
11. Develop Statement of Architecture Work: Draft, review, and secure formal approval.

Key Outputs

• Approved Statement of Architecture Work
• Architecture Vision Document
• Refined Stakeholder Map and Management Plan
• Capability Assessment Summary
• Tailored Architecture Principles

---

Section Summary & Exam Focus

• Understand the exact purpose of the Statement of Architecture Work vs the Architecture Vision.
• Master the 4 quadrants of the Stakeholder Power/Interest Matrix.
• Differentiate clearly between a View (the actual content) and a Viewpoint (the template/specification).