The ADM: Transition Planning and Implementation (E, F, G, H)

Phase G (Implementation Governance) exists to provide architectural oversight of the implementation, ensuring that all implementation projects conform to the defined Target Architecture and comply with the Architecture Contract.

Approving deliverables before deployment describes a review gate process, not the ongoing governance function of Phase G. Creating new architecture models during deployment misrepresents the phase, as the architecture was already designed in earlier phases. Gathering and validating business requirements is the concern of earlier phases like Phase A (Architecture Vision) and the preliminary requirements work, not implementation governance.

Key concept tested: the purpose of Phase G Implementation Governance in the TOGAF ADM cycle.

Phase H (Architecture Change Management) assesses change requests and determines whether they require a new cycle of the ADM, and a change request that requires significant architectural revision is precisely the type of change that triggers re-entry into the ADM cycle rather than being handled within the current architecture.

A scheduled annual compliance review is a routine governance activity, not a trigger for a new ADM cycle. A stakeholder request for updated documentation does not inherently require re-initiating the ADM. An incremental change handled through standard governance procedures is explicitly the type of change that does NOT trigger a new ADM cycle, as it can be managed within Phase H itself.

The key concept tested is understanding how Phase H determines when changes are significant enough to warrant a new ADM iteration versus being managed through existing governance.

Phase F (Migration Planning) focuses on finalizing a detailed Implementation and Migration Plan that is coordinated with the Architecture Roadmap, ensuring that the transition from the baseline to the target architecture is properly planned and prioritized across multiple work packages.

The Architecture Vision document is the output of Phase A, not Phase F. The Architecture Definition Document is developed during Phases B, C, and D as part of architecture development, not migration planning. While Transition Architectures are relevant to Phase F, the primary deliverable is the Implementation and Migration Plan, not just a Transition Architecture plan.

Key concept tested: understanding the purpose and primary deliverable of Phase F in the ADM lifecycle.