Introduction

Phase H of the TOGAF Architecture Development Method (ADM) focuses on establishing procedures for managing change to the new architecture. This phase ensures that the architecture development lifecycle is maintained, the Architecture Governance Framework is executed, and the Enterprise Architecture Capability meets current requirements. The following guide explains the key deliverables required to be completed within this phase and provides steps to complete them.

Deliverables

1. Implementation Governance Model

Objective: Develop a governance model for overseeing the implementation of the architecture.

Description: The Implementation Governance Model is a framework for overseeing the implementation of the architecture, ensuring compliance with the architecture principles and standards.

Steps to Complete:

  1. Define Governance Framework:
    • Identify Roles and Responsibilities: Determine the roles and responsibilities for overseeing the implementation.
    • Develop Governance Processes: Create processes for monitoring and controlling the implementation.
    • Develop Compliance Metrics: Define metrics for measuring compliance with the architecture principles and standards.
  2. Document Governance Model:
    • Create Governance Model Document: Create a formal Implementation Governance Model document.
    • Review Governance Model: Ensure that the governance model is complete, accurate, and aligned with business goals.
    • Get Approval: Present the Implementation Governance Model to stakeholders and obtain approval.
  3. Communicate Governance Model: Share the Implementation Governance Model with the Enterprise Architecture team and other relevant stakeholders.

2. Architecture Contracts

Objective: Establish formal agreements between the architecture team and other stakeholders to ensure compliance with the architecture principles and standards.

Description: Architecture Contracts are formal agreements that outline the commitments and responsibilities of the architecture team and other stakeholders.

Steps to Complete:

  1. Identify Stakeholders:
    • Engage Stakeholders: Work with stakeholders to understand their needs and expectations.
    • Document Commitments: Specify the commitments and responsibilities of the architecture team and other stakeholders.
  2. Develop Contracts:
    • Create Contract Documents: Develop formal Architecture Contract documents.
    • Review Contracts: Ensure that the contracts are complete, accurate, and aligned with business goals.
    • Get Approval: Present the Architecture Contracts to stakeholders and obtain approval.
  3. Communicate Contracts: Share the Architecture Contracts with the Enterprise Architecture team and other relevant stakeholders.

3. Change Request

Objective: Manage changes to the architecture by documenting and processing change requests.

Description: Change Requests are formal documents that outline proposed changes to the architecture, including the rationale, impact, and approval process.

Steps to Complete:

  1. Identify Changes:
    • Gather Input: Collect information on proposed changes to the architecture.
    • Document Changes: Create detailed descriptions of the proposed changes.
  2. Develop Change Requests:
    • Create Change Request Documents: Develop formal Change Request documents.
    • Review Change Requests: Ensure that the change requests are complete, accurate, and aligned with business goals.
    • Get Approval: Present the Change Requests to stakeholders and obtain approval.
  3. Communicate Change Requests: Share the Change Requests with the Enterprise Architecture team and other relevant stakeholders.

4. Compliance Assessment

Objective: Assess compliance with the architecture principles and standards.

Description: Compliance Assessments are evaluations that determine whether the implementation conforms to the architecture principles and standards.

Steps to Complete:

  1. Identify Compliance Criteria:
    • Define Criteria: Determine the criteria for assessing compliance with the architecture principles and standards.
    • Gather Data: Collect data on the current state of the implementation.
  2. Conduct Assessment:
    • Evaluate Compliance: Compare the current state of the implementation against the compliance criteria.
    • Document Findings: Create a detailed report of the compliance assessment findings.
  3. Communicate Assessment:
    • Review Assessment: Ensure that the compliance assessment is complete, accurate, and aligned with business goals.
    • Get Approval: Present the Compliance Assessment to stakeholders and obtain approval.
    • Communicate Assessment: Share the Compliance Assessment with the Enterprise Architecture team and other relevant stakeholders.

5. Request for Architecture Work

Objective: Initiate a new cycle of the ADM to address significant changes to the architecture.

Description: A Request for Architecture Work is a formal document that outlines the need for a new cycle of the ADM to address significant changes to the architecture.

Steps to Complete:

  1. Identify Need for Change:
    • Gather Input: Collect information on the need for significant changes to the architecture.
    • Document Need: Create a detailed description of the need for change.
  2. Develop Request for Architecture Work:
    • Create Request Document: Develop a formal Request for Architecture Work document.
    • Review Request: Ensure that the request is complete, accurate, and aligned with business goals.
    • Get Approval: Present the Request for Architecture Work to stakeholders and obtain approval.
  3. Communicate Request: Share the Request for Architecture Work with the Enterprise Architecture team and other relevant stakeholders.

6. Requirements Impact Assessment

Objective: Assess the impact of changes on the architecture requirements.

Description: A Requirements Impact Assessment is an evaluation that determines the impact of changes on the architecture requirements.

Steps to Complete:

  1. Identify Changes:
    • Gather Input: Collect information on the proposed changes to the architecture.
    • Document Changes: Create detailed descriptions of the proposed changes.
  2. Conduct Impact Assessment:
    • Evaluate Impact: Determine the impact of the proposed changes on the architecture requirements.
    • Document Findings: Create a detailed report of the Requirements Impact Assessment findings.
  3. Communicate Assessment:
    • Review Assessment: Ensure that the Requirements Impact Assessment is complete, accurate, and aligned with business goals.
    • Get Approval: Present the Requirements Impact Assessment to stakeholders and obtain approval.
    • Communicate Assessment: Share the Requirements Impact Assessment with the Enterprise Architecture team and other relevant stakeholders.

Key Concepts

  • Implementation Governance Model: A framework for overseeing the implementation of the architecture, ensuring compliance with the architecture principles and standards.
  • Architecture Contracts: Formal agreements that outline the commitments and responsibilities of the architecture team and other stakeholders.
  • Change Request: Formal documents that outline proposed changes to the architecture, including the rationale, impact, and approval process.
  • Compliance Assessment: Evaluations that determine whether the implementation conforms to the architecture principles and standards.
  • Request for Architecture Work: A formal document that outlines the need for a new cycle of the ADM to address significant changes to the architecture.
  • Requirements Impact Assessment: An evaluation that determines the impact of changes on the architecture requirements.

Conclusion

Phase H of the TOGAF ADM is crucial for establishing procedures for managing change to the new architecture. By completing the key deliverables—Implementation Governance Model, Architecture Contracts, Change Requests, Compliance Assessments, Request for Architecture Work, and Requirements Impact Assessment—organizations can ensure that their architecture development lifecycle is maintained, the Architecture Governance Framework is executed, and the Enterprise Architecture Capability meets current requirements. This phase sets the foundation for successful architecture development and deployment, driving business value and transformation.

References

Leave a Reply

Your email address will not be published. Required fields are marked *