The stages in the Enterprise Architecture Implementation Wheel consist of steps and key focus areas. The level of detail increases as the Implementation Wheel is read from the inside out. The stages and associated steps are based on and inspired by the TOGAF® Standard. Therefore, a mapping to the TOGAF Architecture Development Method (ADM) [1] can be made. The tabs below show the relationship between the Implementation Wheel stages on the one hand and the ADM phases on the other.
The four stages of the Implementation Wheel
Stage one: Document maps to the TOGAF ADM phases A, B, C, and D.
According to the TOGAF Standard, Phase B is about developing the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers. This aligns with what the Enterprise Architecture Implementation Wheel describes as gaining insight into the organizational structure and its processes.
Phase C instructs the organization to capture its Application Portfolio within the Architecture Repository. The same goes for the technology products that are being used. They, too, need to be captured in diagrams and catalogs (during Phase D). Classifying the products during inventory is a welcome addition. The Implementation Wheel supports this method by emphasizing the importance of its inventory stage.
Finally, Phase A is all about identifying stakeholders and their concerns, as well as knowing how to communicate the architecture with them. To do so correctly, creating a stakeholder mapping based on their classification is essential. The Enterprise Architecture Implementation Wheel addresses all three of these important topics – Stakeholder Classification, Mapping, and Communication – during the first stage (Document).
More information about the Implementation Wheel mapping to the TOGAF ADM can be found in Chapter 8, Section 8.1, of my book.
Stage two: Define maps to the TOGAF ADM Preliminary Phase, as well as phases A, B, C, and D.
During the execution of Phase A, a maturity assessment should take place. The Enterprise Architecture Implementation Wheel describes the same need in its second stage (Define), but supplements it by providing guidance regarding the use of a maturity model.
The TOGAF Standard mentions defining Architecture Principles as being part of the Preliminary Phase. According to the framework, defining a set of Architecture Principles that is appropriate to the enterprise should be done once the organizational context is understood. The Implementation Wheel therefore suggests performing an inventory of the organization and its context prior to defining the principles.
With regard to strategy, the Preliminary Phase states that strategic and tactical business objectives and aspirations need to be met. The Enterprise Architecture needs to reflect this requirement and allow for operation of architecture discipline within the organization. Using the Implementation Wheel, this requirement is met by following the guidance provided by Business Architecture. The BIZBOK Guide (to which the TOGAF Standard refers) provides useful resources for developing and defining strategic drivers, goals, objectives, and initiatives. The Implementation Wheel adopts this methodology and details how these elements can be implemented.
More information about the Implementation Wheel mapping to the TOGAF ADM can be found in Chapter 8, Section 8.1, of my book.
Stage three: Execute maps to the TOGAF ADM phases E and F.
The TOGAF Standard implies in Phase F that a business value needs to be assigned to each work package. This allows for focused governance during a later stage. The Enterprise Architecture Implementation Wheel hooks into this during stage three (Execute) by detailing the objectives that originated from the organization’s strategy into initiatives (work packages).
Phase E of the framework describes the creation of an Architecture Roadmap, which is finalized in Phase F. The Architecture Roadmap contains initiatives based on the components of earlier phases. The Implementation Wheel suggests linking the initiatives to their corresponding goals and objectives defined in the second stage (Define). This allows for a visually understandable governance during the final stage (Control).
More information about the Implementation Wheel mapping to the TOGAF ADM can be found in Chapter 8, Section 8.1, of my book.
Stage four: Control maps to the TOGAF ADM phases G and H.
The objective of Phase G is to ensure conformance with the Target Architecture. Priorities are defined and the necessary transitions to reach the Target Architecture are realized. Stage four (Control) of the Implementation Wheel provides tools and techniques for measuring and monitoring the progress of these transitions. This aligns with the TOGAF Standard Phase H.
The final stage of the Enterprise Architecture Implementation Wheel also enables the architect to prioritize initiatives based on their business value.
More information about the Implementation Wheel mapping to the TOGAF ADM can be found in Chapter 8, Section 8.1, of my book.
[1] The Open Group. The TOGAF® Standard, 10th Edition, Architecture Development Method. ’s-Hertogenbosch: Van Haren Publishing, 2022.
