TOGAF 9.1 Released – What does it mean to you?

If you are planning to take up TOGAF certification examination, you would definitely want to know how the release of TOGAF 9.1 impacts you. You would want to which version you need to study.

Here is the simple guideline. If you are planning to appear for the exam…

1. …before June 2012 the you should study TOGAF 9
2. …between June 2012 and May 2013 then you can study either TOGAF 9 of 9.1
3. …after June 2013 it is only TOGAF 9.1

In a nutshell, if you have already done most of the studying using TOGAF 9.0 then you have slightly more than a year to clear the exam. However, if you have yet to begin the study you better start with 9.1.

What are the main differences between TOGAF 9 and 9.1?

The Open Group has published a presentation in the form of a PDF which provides an overview of the differences – here is the link.

If you would prefer to have a look at the difference as a two pager then I recommend that you go through this post of Mike Walker.

However, I think the biggest difference between the two is how the objectives of each of the ADM phase are written. The latest version seems to be significant improvement. This is also the most important change for those of you who want to appear for the foundation level exam.

You may also need to go through Phase E and F more carefully as they have been reworked.

Comparison of ADM Objectives – TOGAF 9 vs. TOGAF 9.1

Phase	Objective as per TOGAF 9	Objective as per TOGAF 9.1
Preliminary	To review the organizational context for conducting enterprise architecture To identify the sponsor stakeholder(s) and other major stakeholders impacted by the business directive to create an enterprise architecture and determine their requirements and priorities from the enterprise, their relationships with the enterprise, and required working behaviors with each other To ensure that everyone who will be involved in, or benefit from, this approach is committed to the success of the architectural process To enable the architecture sponsor to create requirements for work across the affected business areas To identify and scope the elements of the enterprise organizations affected by the business directive and define the constraints and assumptions (particularly in a federated architecture environment) To define the ‘‘architecture footprint’’ for the organization — the people responsible for performing architecture work, where they are located, and their responsibilities To define the framework and detailed methodologies that are going to be used to develop enterprise architectures in the organization concerned (typically, an adaptation of the generic ADM) To confirm a governance and support framework that will provide business process and resources for architecture governance through the ADM cycle; these will confirm the fitness-for-purpose of the Target Architecture and measure its ongoing effectiveness (normally includes a pilot project) To select and implement supporting tools and other infrastructure to support the architecture activity To define the architecture principles that will form part of the constraints on any architecture work	Determine the Architecture Capability desired by the organization: Review the organizational context for conducting enterprise architecture Identify and scope the elements of the enterprise organizations affected by the Architecture Capability Identify the established frameworks, methods, and processes that intersect with the Architecture Capability Establish Capability Maturity target Establish the Architecture Capability: Define and establish the Organizational Model for Enterprise Architecture Define and establish the detailed process and resources for architecture governance Select and implement tools that support the Architecture Capability Define the Architecture Principles
Phase A	To ensure that this evolution of the architecture development cycle has proper recognition and endorsement from the corporate management of the enterprise, and the support and commitment of the necessary line management To define and organize an architecture development cycle within the overall context of the architecture framework, as established in the Preliminary phase To validate the business principles, business goals, and strategic business drivers of the organization and the enterprise architecture Key Performance Indicators (KPIs) To define the scope of, and to identify and prioritize the components of, the Baseline Architecture effort To define the relevant stakeholders, and their concerns and objectives To define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with To articulate an Architecture Vision and formalize the value proposition that demonstrates a response to those requirements and constraints To create a comprehensive plan that addresses scheduling, resourcing, financing, communication, risks, constraints, assumptions, and dependencies, in line with the project management frameworks adopted by the enterprise (such as PRINCE2 or PMBOK) To secure formal approval to proceed To understand the impact on, and of, other enterprise architecture development cycles ongoing in parallel	Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision
Phase B	To describe the Baseline Business Architecture To develop a Target Business Architecture, describing the product and/or service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment, based on the business principles, business goals, and strategic drivers To analyze the gaps between the Baseline and Target Business Architectures To select and develop the relevant architecture viewpoints that will enable the architect to demonstrate how the stakeholder concerns are addressed in the Business Architecture To select the relevant tools and techniques to be used in association with the selected viewpoints	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 Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures
Phase C	The objective of Phase C is to develop Target Architectures covering either or both (depending on project scope) of the data and application systems domains.Information Systems Architecture focuses on identifying and defining the applications and data considerations that support an enterprise’s Business Architecture; for example, by defining views that relate to information, knowledge, application services, etc.	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 Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures
Phase D	The Technology Architecture phase seeks to map application components defined in the Application Architecture phase into a set of technology components, which represent software and hardware components, available from the market or configured within the organization into technology platforms.As Technology Architecture defines the physical realization of an architectural solution, it has strong links to implementation and migration planning.Technology Architecture will define baseline (i.e., current) and target views of the technology portfolio, detailing the roadmap towards the Target Architecture, and to identify key work packages in the roadmap. Technology Architecture completes the set of architectural information and therefore supports cost assessment for particular migration scenarios.	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 Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures
Phase E	To review the target business objectives and capabilities, consolidate the gaps from Phases B to D, and then organize groups of building blocks to address these capabilities To review and confirm the enterprise’s current parameters for and ability to absorb change To derive a series of Transition Architectures that deliver continuous business value (e.g., capability increments) through the exploitation of opportunities to realize the building blocks To generate and gain consensus on an outline Implementation and Migration Strategy	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 Deter mine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
Phase F	To ensure that the Implementation and Migration Plan is coordinated with the various management frameworks in use within the enterprise To prioritize all work packages, projects, and building blocks by assigning business value to each and conducting a cost/business analysis To finalize the Architecture Vision and Architecture Definition Documents, in line with the agreed implementation approach To confirm the Transition Architectures defined in Phase E with relevant stakeholders To create, evolve, and monitor the detailed Implementation and Migration Plan providing necessary resources to enable the realization of the Transition Architectures, as defined in Phase E	Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
Phase G	To formulate recommendations for each implementation project To govern and manage an Architecture Contract covering the overall implementation and deployment process To perform appropriate governance functions while the solution is being implemented and deployed To ensure conformance with the defined architecture by implementation projects and other projects To ensure that the program of solutions is deployed successfully, as a planned program of work To ensure conformance of the deployed solution with the Target Architecture To mobilize supporting operations that will underpin the future working lifetime of the deployed solution	Ensure conformance with the Target Architecture by implementation projects Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
Phase H	To ensure that baseline architectures continue to be fit-for-purpose To assess the performance of the architecture and make recommendations for change To assess changes to the framework and principles set up in previous phases To establish an architecture change management process for the new enterprise architecture baseline that is achieved with completion of Phase G To maximize the business value from the architecture and ongoing operations To operate the Governance Framework	Ensure that the architecture lifecycle is maintained Ensure that the Architecture Governance Framework is executed Ensure that the enterprise Architecture Capability meets current requirements

Here are the links to the material from The Open Group

• TOGAF 9: Technical Corrigendum No. 1 – containing the details of all corrections
• An Introduction to TOGAF 9.1