Top 8 TOGAF Deliverables - You Need to Make Your EA Project Succeed

Sep 11, 2026

Uploaded by James

Top 8 TOGAF deliverables needed to drive enterprise architecture implementation success. The material explains how success is measured through implementation outcomes and describes a workflow-driven model and publish/subscribe approach across project initiation, architecture development, and transition planning. It lists key architecture deliverables including principles, goals, drivers, architecture vision, Statement of Architecture Work, architecture definition document, requirements specification, transition architecture, and implementation and migration planning, emphasizing linkage to business strategy and effective executive communication.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages17

Reading Time6 min

AccessFree to download

Architecture Deliverables Overview

How Success Is Measured

Workflow-Driven and Publish/Subscribe Approaches

Project Initiation

From Business Need to Business Case

Architecture Development

Business Principles, Goals, Drivers

Architecture Vision

Principles and Governance

Statement of Architecture Work

Transition Planning

Transition Architecture

Implementation and Migration Plan

Top 8 TOGAF® Deliverables You Need to Make Your EA Project Succeed HOW DO YOU MEASURE THE SUCCESS OF AN ENTERPRISE ARCHICETURE PROJECT? Through measuring the success of implementation projects that use the architecture… Workflow Driven approach Publish & Subscribe approach Project Initiation Architecture development Architecture Deliverables • Principles, Goals, Drivers • Architecture Principles • Architecture Vision • Statement of Architecture Work • Architecture Definition Document • Architecture Requirements Specification • Transition Architecture • Implementation and Migration Plan [http://www.togaf.info](http://www.togaf.info) Click on the Templates: TOGAF 9 Templates and Example item • Architecture initiative starts with the identification of a need by someone in business (or IT) and send to the architecture team as a request for assistance. • The architecture team will then have to perform a few tasks to translate this“need” into a business case. • The business case then defined well enough to convince a manager in the organisation to act as project sponsor. Project Initiation Architecture development Transition Planning Business Principles, Business Goals, and Business Drivers • Experience taught that it is essential for the architecture team to document their understanding of the business strategies and objectives to ensure that any architectural decision or direction can be linked to a business initiative. • The business principles, business goals, and business drivers’ template provides the right context, by describing the organization and industry drivers that are constraining or influencing the organizational strategy. I normally use the Operating Model diagrams as described in Enterprise Architecture as Strategy ([http://www.imd.org/book/eas/](http://www.imd.org/book/eas/)) as the basis of the Architecture Vision. • The Architecture Vision is an executive summary of the aspirational view of the architecture end-state and is used as a communication document for executive sponsors of the project and senior management. • The Architecture Vision content is also added to the Statement of Architecture Work as an executive summary to facilitate, at the outset, what the desired outcome should be for the architecture. • Using principles (general rules and guidelines) in an architecture project is good practice. • Defining or amending a set of principles during the project initiation phase provides the team and key sponsors with a mechanism to make decisions and design choices. • It will only have an impact if the principles are widely distributed and used. A good source for a starting set of principles is available as part of the TOGAF® 9.1 standard; see Chapter 23 ( [http://pubs.opengroup.org/architecture/togaf9-](http://pubs.opengroup.org/architecture/togaf9-) doc/arch/chap23.html\#tag 23 ) for a set of generic architecture principles. • The Statement of Architecture Work is a contract between the business planning / project sponsors and the architecture team. • The scope of the project is also defined in this deliverable, as well as the change management procedures that must be used to amend the scope of work. • Creating this deliverable allows the Enterprise Architecture professional leading the initiative to plan and manage resources properly. • In organizations with formal project offices that require the team to submit project charters this document can be replaced by the organizational project documentation.

FAQs

How are success metrics defined for an enterprise architecture project?

Success is measured by evaluating implementation projects that use the architecture and linking results to business initiatives and objectives.

What deliverables are included in the TOGAF architecture deliverable set?

The list covers architecture principles and vision, Statement of Architecture Work, Architecture Definition Document, Architecture Requirements Specification, Transition Architecture, and an Implementation and Migration Plan.

What role does the Statement of Architecture Work play?

It acts as a contract between project sponsors/business planning and the architecture team, defining scope and change management procedures for amendments.

Sep 11, 2026

Uploaded by James