✅ 16.1 EA Governance

🔹 What is Governance?

Governance = a system to direct and control the current and future state of an enterprise.

  • Ensures structured, transparent decision-making

  • Includes rules, structures, metrics, and procedures

  • Balances interests and protects stakeholders' rights

🔸 Types of Governance in EA

Type

Purpose

Corporate Governance

Directs business conduct; focuses on board roles, accountability

EA Governance

Directs and controls Enterprise Architecture across the organization

Domain Governance

Business, Application, Data, Technology architecture areas

Implementation Governance

Ensures changes align with target architecture

EA Governance is part of Corporate Governance.

🧱 Why is EA Governance Needed?

Without governance, the architecture may drift from its target state:

  • EA = planned change

  • ADM = method of change

  • Governance = ensures both are aligned and realized

⚙ What Does EA Governance Control?

  1. Development of the Target Architecture

  2. Implementation of Changes to reach the target

🧩 Governance Mechanisms & Tools

Tool

Purpose

Statement of Architecture Work

Directs EA team’s scope and intent

Architecture Contracts

Governs implementation and enforces obligations

Architecture Requirement Specs

Defines expected behavior and conformance criteria

Checklists

Verify EA work meets agreed guidelines

All these are stored in the Architecture Repository.

📁 Architecture Repository Governance Content

  1. Reference Data – Procedures, templates, project guidance

  2. Process Status – Live governance actions (e.g. pending assessments)

  3. Audit Information – Key decisions, actions, and responsibilities

✅ Benefits of EA Governance (from Ramani Naidu)

  1. Discipline – Adherence to roles/processes

  2. Responsibility – Each party acts accountably

  3. Accountability – Groups are answerable

  4. Fairness – Prevents unfair advantages

  5. Transparency – All decisions traceable

  6. Independency – Reduces conflict of interest

🧠 The Architecture Board

A cross-functional decision-making body for EA governance.

  • Comprised of key stakeholders

  • Enforces architecture strategy and compliance

  • Resolves issues, grants dispensations, oversees implementation

Architecture Board Responsibilities

Review and approve EA work and changes

Validate service levels, compliance, cost savings

Issue policy updates and dispensations

Own governance processes (e.g. compliance checklists, decision templates)

📌 Important: The final decision-making power over architecture always lies with stakeholders, not the board or architects.

🛡 Architecture Compliance

TOGAF defines two kinds:

  1. Architecture Function Compliance

    • Directs projects on how to align with EA

    • e.g., mandates participating in tech selection or supplier choice

  2. Enterprise/IT Governance Compliance

    • Formal architecture compliance review process

    • Ensures projects stay aligned with target architecture