This is another post about TOGAF. Check other posts in the series.

Objectives

After creating architectures, choosing solutions and planning everything, assigned teams are finalny building. In Phase G we need to make sure, that what is built is actually compliant with our architecture.

It might seem that this phase is the longest and most difficult of ADM. In real life scenarios, especially with more agile approach, ADM iterations are applied, where multiple changes are introduced into the architecture.

Objectives summary:

• Govern and manage architecture contracts.
• Govern discussion and implementation to be aligned with architecture.
• Ensure architecture conformance.

Approach

• Create projects and programs.
• Ensure implementation follows migration plan.
• Work with governance frameworks like Cobit and
  project management methods like Prince2.
• Create operation framework (ITSM).

Techniques

Compliant process – checks design, implementation process and architecture conformance.

IT compliance  terminology:

Inputs

All outputs from previous phases, most important are:

• Organizational Model for Enterprise Architecture.
• Architecture Definition Document.
• Architecture Requirements Specification.
• Implementation Governance Model.
• Implementation and Migration Plan.

Outputs

Architecture-compliant solutions deployed including:

• 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.

Materials

TOGAF Phase G – Implementation Governance
Architecture compliance