Comprehensive Guide to Phase G: Implementation Governance in TOGAF ADM

Introduction

Phase G of the TOGAF Architecture Development Method (ADM) focuses on providing architectural oversight of the implementation. This phase ensures that the implementation projects conform to the Target Architecture and that appropriate governance functions are performed. It involves confirming the scope and priorities for deployment, identifying necessary resources and skills, guiding the development of solutions, and performing compliance reviews.

Objectives and Steps

1. Ensure Conformance with the Target Architecture

Objective: Ensure that implementation projects conform to the Target Architecture.

Steps:

• Perform Architecture Governance Functions: Carry out governance functions for the solution and any implementation-driven architecture Change Requests.
• Confirm Scope and Priorities: Work with development management to confirm the scope and priorities for deployment.
• Identify Deployment Resources and Skills: Determine the resources and skills required for deployment.
• Guide Solution Development: Provide guidance for the development of solutions deployment.
• Perform Compliance Reviews: Conduct Enterprise Architecture compliance reviews to ensure adherence to the Target Architecture.
• Implement Business and IT Operations: Ensure that business and IT operations are implemented as per the Target Architecture.
• Conduct Post-Implementation Review: Perform a post-implementation review and close the implementation.

Inputs and Outputs

Inputs

1. Architecture Reference Materials:
   • Use architecture reference materials to guide the implementation governance process.
2. Request for Architecture Work:
   • The initial request that triggers the architecture development process.
3. Capability Assessment:
   • An evaluation of the organization’s current capabilities.
4. Organizational Model for Enterprise Architecture:
   • The organizational structure and roles involved in the Enterprise Architecture.
5. Tailored Architecture Framework:
   • The customized architecture framework used for the project.
6. Statement of Architecture Work:
   • The approved document that outlines the scope, objectives, and deliverables of the architecture project.
7. Architecture Vision:
   • The comprehensive vision for the future state of the enterprise architecture.
8. Architecture Repository:
   • Existing architecture documentation, including framework descriptions, architecture descriptions, and baseline descriptions.
9. Architecture Definition Document:
   • A detailed document that includes baseline and/or target architectures of any architectural domain.
10. Architecture Requirements Specification:
    • Includes gap analysis results and relevant technical requirements.
11. Architecture Roadmap:
    • The roadmap outlining the transition from the Baseline to the Target Architecture.
12. Implementation Governance Model:
    • A model for governing the implementation of the architecture.
13. Architecture Contract (Standard):
    • A standard contract outlining the terms and conditions for the architecture implementation.
14. Request for Architecture Work Identified in Phases E and F:
    • Requests for architecture work identified during the migration planning phase.
15. Implementation and Migration Plan:
    • A detailed plan for implementing and migrating to the Target Architecture.
16. Architecture Contract (Signed):
    • The signed contract agreeing to the terms and conditions for the architecture implementation.
17. Compliance Assessments:
    • Assessments to ensure compliance with the Target Architecture.
18. Change Requests:
    • Requests for changes to the architecture based on implementation needs.

Outputs

1. Architecture-Compliant Solutions Deployed:
   • Includes:
     • The architecture-compliant implemented system
     • Populated Architecture Repository
     • Architecture compliance recommendations and dispensations
     • Recommendations on service delivery requirements
     • Recommendations on performance metrics
     • Service Level Agreements (SLAs)
     • Architecture Vision, updated post-implementation
     • Architecture Definition Document, updated post-implementation
     • Business and IT operating models for the implemented solution
     • Architecture Building Blocks (ABBs)

Key Concepts

• Implementation Governance: The process of overseeing the implementation to ensure conformance with the Target Architecture.
• Architecture Governance Functions: Functions performed to ensure that the solution and any implementation-driven architecture Change Requests are compliant with the Target Architecture.
• Compliance Reviews: Reviews conducted to ensure that the implementation adheres to the Target Architecture.
• Post-Implementation Review: A review conducted after implementation to assess the success and identify any lessons learned.
• Architecture-Compliant Solutions: Solutions that are deployed in compliance with the Target Architecture.

Conclusion

Phase G of the TOGAF ADM is essential for ensuring that implementation projects conform to the Target Architecture. By following the outlined steps and utilizing the necessary inputs, organizations can provide effective architectural oversight, perform governance functions, and conduct compliance reviews. This phase ensures that the implemented solutions are aligned with the Target Architecture, addressing business goals, strategic drivers, and stakeholder concerns.

References

• Powerful TOGAF ADM Toolset 1.
• TOGAF ADM Software 2.
• Best TOGAF Software with Agile & UML – Visual Paradigm Enterprise 3.
• TOGAF ADM Software: Act and Generate ADM Deliverables 4.
• The Best TOGAF Software 5.
• TOGAF® Tool for Enterprise Architecture – ArchiMetric .
• Visual Paradigm TOGAF ADM Tool: Empowering Your Enterprise Architecture Teams – Visual Paradigm Guides .
• TOGAF ADM Tutorial .
• Step-by-Step Enterprise Architecture Tutorial with TOGAF .
• Streamline Your Enterprise Architecture with Visual Paradigm’s TOGAF ADM Tools – Visual Paradigm Guides .