14. Phase G: Implementation Governance

Chapter Contents
14.1 Objectives | 14.2 Inputs | 14.3 Steps | 14.4 Outputs | 14.5 Approach

This chapter provides an architectural oversight of the implementation.



Figure 14-1: Phase G: Implementation Governance

14.1 Objectives

The objectives of Phase G are to:

14.2 Inputs

This section defines the inputs to Phase G.

14.2.1 Reference Materials External to the Enterprise

14.2.2 Non-Architectural Inputs

14.2.3 Architectural Inputs

14.3 Steps

The level of detail addressed in Phase G will depend on the scope and goals of the overall architecture effort.

The order of the steps in Phase G as well as the time at which they are formally started and completed should be adapted to the situation at hand in accordance with the established Architecture Governance.

The steps in Phase G are as follows:

14.3.1 Confirm Scope and Priorities for Deployment with Development Management

14.3.2 Identify Deployment Resources and Skills

The project resources will include the development resources which will need to be educated in the overall Enterprise Architecture deliverables and expectations from the specific development and implementation projects.

The following considerations should be addressed in this step:

14.3.3 Guide Development of Solutions Deployment

14.3.4 Perform Enterprise Architecture Compliance Reviews

14.3.5 Implement Business and IT Operations

14.3.6 Perform Post-Implementation Review and Close the Implementation

Closure on Phase G will be when the solutions are fully deployed once.

14.4 Outputs

The outputs of Phase G may include, but are not restricted to:

14.5 Approach

It is here that all the information for successful management of the various implementation projects is brought together. Note that, in parallel with Phase G, there is the execution of an organizational-specific development process, where the actual development happens.

To enable early realization of business value and benefits, and to minimize the risk in the transformation and migration program, the favored approach is to deploy the Target Architecture as a series of transitions. Each transition represents an incremental step towards the target, and each delivers business benefit in its own right. Therefore, the overall approach in Phase G is to:

Phase G establishes the connection between architecture and implementation organization, through the Architecture Contract.

Project details are developed, including:

Implementation governance is closely allied to overall Architecture Governance, which is discussed in Part VI, 44. Architecture Governance .

A key aspect of Phase G is ensuring compliance with the defined architecture(s), not only by the implementation projects, but also by other ongoing projects within the enterprise. The considerations involved with this are explained in detail in Part VI, 42. Architecture Compliance .
return to top of page