Nico Celen
Nico Celen is an experienced Enterprise Architect bringing 20+ years of expertise in IT in different roles and domains to companies in various industries.
As an Enterprise Architect he acts as an advisor for business and ICT. He supports organizations by developing a vision and roadmap for business and IT transformation programs. As a Solution Architect he defines the high level architecture of new solutions.
In the previous post, the process of roadmapping was introduced. In this post, I would like to present a custom method that can help you in your roadmapping process. The method refers to the TOGAF ADM and ArchiMate specification, but there is no strict dependence.
Like Enterprise Architecture, roadmapping should be considered as an iterative, incremental process. Since roadmapping is part of the EA effort, the TOGAF 9.1 ADM can be used as a guidance for the roadmapping process. We describe briefly the TOGAF 9.1. ADM phases as explained in the TOGAF 9.1. specification.
- The Preliminary Phase is about defining “where, what, why, who, and how we do architecture” in the enterprise concerned.
- Phase A – Architecture Vision aims to develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture. An approval for a Statement of Architecture Work needs to be obtained that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision.
- Phase B – Business Architecture aims to develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns. Candidate Architecture Roadmap components need to be identified based upon gaps between the Baseline and Target Business Architectures.
- Phase C – Information Systems Architectures aims to develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns.
- Phase D – Technology Architecture aims to develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns. Candidate Architecture Roadmap components need to be identified based upon gaps between the Baseline and Target Technology Architectures.
- Phase E – Opportunities & Solutions aims to generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D. If an incremental approach is required Transition Architectures need to be defined that will deliver continuous business value.
- Phase F – Migration Planning aims to finalize the Architecture Roadmap and the supporting Implementation and Migration Plan. The Implementation and Migration Plan must be coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio. The business value and cost of work packages and Transition Architectures must be understood by key stakeholders.
- Phase G – Implementation Governance aims to ensure conformance with the Target Architecture by implementation projects. Architecture Governance functions appropriate for the solution and any implementation-driven architecture Change Requests need to be performed.
- Phase H – Architecture Change Management aims to ensure that the architecture lifecycle is maintained, that the Architecture Governance Framework is executed and that the enterprise Architecture Capability meets current requirements.
- Requirements Management aims to ensure that the Requirements Management process is sustained and operates for all relevant ADM phases. Architecture requirements identified during any execution of the ADM cycle or a phase need to be managed.
The TOGAF 9.1 ADM phases can be clustered in 4 areas:
- The Preliminary Phase and Phase A – Architecture Vision focus on the definition of the Architecture Context.
- Phase B – Business Architecture, Phase C – Information Systems Architectures and Phase D – Technology Architecture focus on the Architecture Definition.
- Phase E – Opportunities & Solutions and Phase F – Migration Planning focus on Transition Planning.
- Phase G – Implementation Governance and Phase H – Architecture Change Management focus on Architecture Governance.
- Requirements Management is relevant for all areas.
The development of a consolidated and integrated roadmap is part of Transition Planning. The description of the current state (baseline architecture) and the desired future state (target architecture) based on goals and drivers is essential input for the definition of the roadmap. Once the roadmap is developed, an implementation and migration plan is developed that describes the necessary steps to realize the desired future state. As a consequence, programs/projects are defined to execute the roadmap and all necessary governance structures are put in place.