Responsibilities Knowledge-Based Study

Study notes

1. Overview and Governance Mandate

   In the TOGAF Standard, an Architecture Board is a cross-functional governance body established to oversee the implementation of the enterprise architecture governance strategy. As organizations scale and maintain disparate business units, architectural governance ensures that individual systems and change initiatives align coherently with broader enterprise goals.

   The Architecture Board is not typically responsible for the day-to-day authoring of models or project management; rather, it provides top-level oversight, strategic steer, and governance authority across all architecture work within the enterprise.

   Key Governance Responsibilities

   The TOGAF Standard outlines specific operational and governance duties assigned to the Architecture Board, including:

   • Consistency between Sub-Architectures: Ensuring integration and alignment across domain architectures (Business, Data, Application, and Technology) and between federated business units.
   • Architecture Compliance Review: Monitoring implementation projects to verify that targets defined in Architecture Contracts and specifications are strictly observed.
   • Dispensation and Variance Approval: Evaluating requests for exceptions, waivers, or dispensations when a project cannot meet standard architectural constraints, ensuring deviations are documented, time-bounded, and managed.
   • Promoting Reuse: Identifying common components, services, and reference models across programs to reduce duplication and total cost of ownership.
   • Resolving Ambiguity and Conflict: Providing authoritative arbitration when competing priorities or architectural interpretations arise across stakeholder groups.
   • Capability Maturity: Guiding the ongoing improvement and professionalization of the organization's enterprise architecture practice.

   Distinguishing Governance from Execution

   A frequent point of confusion in enterprise architecture is distinguishing the Architecture Board's responsibilities from those of Project Management Offices (PMOs) or operational solution delivery teams.

   • Architecture Board vs. Project Management: The Board does not allocate project budgets, manage sprint backlogs, or supervise contractor staff. It reviews architectural alignment and grants compliance sign-offs.
   • Architecture Board vs. Lead Architect: While the lead architect drives the creation and technical synthesis of architectural deliverables, the Architecture Board acts as the formal approval and dispute-resolution authority representing cross-organizational interests.
   • Dispensations vs. Architecture Changes: Granting a dispensation allows a temporary or bounded exception for a specific project without altering baseline enterprise standards. In contrast, changing baseline standards requires formal architecture change management processes overseen by the Board.

   Knowledge Check

   Test your understanding of the formal responsibilities of the Architecture Board according to the TOGAF Standard.

   Question: Which of the following is a primary responsibility of the Architecture Board?

   • A) Managing project schedules, individual developer task assignments, and software sprint backlogs.
   • B) Approving variances, granting dispensations, and resolving architectural conflicts across initiatives.
   • C) Drafting daily low-level database schemas and unit testing operational code.
   • D) Directly procuring third-party vendor contracts and managing day-to-day facilities operations.

   Answer & Explanation

   Correct Answer: B

   Explanation: In the TOGAF Standard, the Architecture Board's core governance responsibilities include reviewing compliance, adjudicating conflicts, and approving or rejecting dispensations (variances) against established architectures. Options A, C, and D describe operational project management, low-level implementation, and operational procurement/facilities duties, which fall outside the scope of architectural governance.