Patterns & Co. is introducing a Commercial Off-the-Shelf (COTS) Market Analytics solution in order to improve its new delivery service. Patterns &…

The scenario describes a situation where the CIO, the project sponsor, has made a strategic decision to accept a non-standard technology after considering the risks. The task is to execute Phase G (Implementation Governance) based on this decision. The correct course of action is to govern the implementation of the approved solution, not to challenge or reverse the CIO's decision.

Option B correctly reflects the necessary governance activities. It formalizes the CIO's decision by updating the company's standards (Standards Information Base) to include the new technology. It establishes formal oversight through an Architecture Contract, plans for necessary assurance activities like performance testing (to meet KPIs) and compliance reviews, and confirms operational parameters (SLAs) with the business. This approach respects the sponsor's authority while ensuring the project is governed correctly according to TOGAF principles.

A. This option incorrectly challenges the CIO's explicit decision by asking the supplier to modify the solution to meet the old standards. The architect's role here is to implement the approved decision, not reverse it.

C. This option directly contradicts the CIO's directive. The CIO has already approved the non-standard solution, overruling the Architecture Board's initial recommendation. Eliminating the component is not an option.

D. This option proposes re-doing work, such as risk and impact analysis, that should have informed the CIO's decision. While some activities are correct (Architecture Contract), it misses the crucial step of formalizing the standards exception, which is a key governance action in this context.

1. The TOGAF® Standard

Version 9.2

Chapter 14: Phase G - Implementation Governance:

Section 14.2

Objectives: The objectives of Phase G include ensuring conformance with the Target Architecture. When a deviation is approved by a sponsor

the governance function's role is to manage that deviation.

Section 14.4

Step 4: Perform Enterprise Architecture Compliance Review: This step is central to Phase G. The review assesses compliance

and in this case

would confirm the CIO's approved dispensation for the non-standard technology. Option B's plan for a compliance review aligns with this.

Section 14.5

Outputs: Key outputs include a signed Architecture Contract and Compliance Assessments

both of which are mentioned or implied in option B.

2. The TOGAF® Standard

Version 9.2

Chapter 36: Architecture Governance:

Section 36.2.6

Dispensation: "The dispensation process is a formal record of an agreement to deviate from the standard for a given period of time or on a specific project or system." The CIO's approval is a dispensation. The follow-on action in option B

updating the Standards Information Base

is the correct way to manage this approved change.

3. The TOGAF® Standard

Version 9.2

Chapter 35: Architecture Contracts:

Section 35.2

Contents of an Architecture Contract: This section details that contracts should cover conformance requirements

including SLAs. Option B correctly identifies the need to create an Architecture Contract and agree on SLAs with the business.