Comprehensive Guide for TOGAF ADM

Introduction

1.1 Overview

This Guide provides essential guidance on using the TOGAF framework to develop, maintain, and utilize an Enterprise Architecture (EA). It serves as a companion to the TOGAF framework, aiming to bring its concepts and generic constructs to life. The goal is to align EA with stakeholder requirements and expectations, enabling predictable value creation.

The TOGAF framework’s core is its concepts, which are universally applicable. Everything else in the framework serves as examples or starter sets that can be modified according to specific needs. This Guide advises practitioners on effectively using the TOGAF framework’s universal structure.

This Guide is specifically written for practitioners tasked with developing, maintaining, and using EA. It provides the context, content, and rationale behind choices and steps that an EA practitioner can consult at any point. A well-developed EA optimizes Boundaryless Information Flow™ within and between enterprises based on open standards and global interoperability.

The TOGAF Standard is applied to develop architectures supporting strategy development, portfolio management, project planning and execution, and solution development. There is no single correct approach to EA; the right approach depends on the specific purpose of the architecture development initiative. This Guide helps practitioners identify the appropriate approach for their particular needs.

Developing, maintaining, and using an EA requires deep interaction with various specialized functions such as strategy development, budgeting, benefits realization, portfolio management, program & project management, and operational units. This Guide will:

• Introduce key topics of concern
• Describe the TOGAF Standard concepts related to the topic
• Show how it is related to developing, maintaining, and using an EA
• Discuss what the practitioner needs to know
• Describe what the practitioner should do with this knowledge

This Guide is divided into six parts:

Part 1: Introduction

• This part contains the introductory section and a set of definitions.

Part 2: Guidance on Enterprise Architecture

• What an Enterprise Architecture is and what it is used for
• Coordinating EA development across the EA Landscape
• Coordinating EA development with the business cycle

Part 3: Guidance on Developing an Enterprise Architecture

• Using the ADM
• Developing an Enterprise Architecture to Support Strategy
• Developing an Enterprise Architecture to Support Portfolio
• Developing an Enterprise Architecture to Support Project
• Developing an Enterprise Architecture to Support Solution Delivery
• Special Cases

Part 4: Guidance on Using an Enterprise Architecture

• What to do when you are hip-deep in solution delivery
• Architecture in action (agile Enterprise, response to incident, etc.)

Part 5: Guidance on Maintaining an Enterprise Architecture

• Managing multiple simultaneous roadmaps
• What to do when you are hip-deep in solution delivery

Part 6: Appendices

• A list of useful tables related to frameworks, reference models, etc.

1.2 How to Use this Guide with the TOGAF Framework

The TOGAF framework provides essential universal scaffolding useful in a range of organizations, industries, and architectural styles. This Guide fills in what is not explicitly addressed by the TOGAF framework and provides an approach to interpret the standard. The TOGAF framework is designed to require interpretation or customization, providing universal scaffolding expressed as concepts.

This Guide is written for practitioners who develop, maintain, and use an EA, focusing on practical application rather than theoretical concerns. It assumes no detailed knowledge of the TOGAF framework but explores its core concepts in the context of using them to develop, maintain, and use an EA. This includes guidance on iteration, an EA Repository, executing the ADM for supporting Strategy, Portfolio, Project, and Solution Delivery, and performing effective governance of the EA practice.

This Guide is part of the TOGAF Library, which includes other documents like the TOGAF® Leader’s Guide to Establishing and Evolving an EA Capability. The TOGAF Library provides a complete interpretation of the TOGAF Standard to establish an EA Capability, develop the EA Capability team, and deliver a useful architecture to guide change and govern enterprise change initiatives.

1.3 Recommended Tools

Visual Paradigm

Visual Paradigm offers a comprehensive suite of tools that support TOGAF and Archimate, making it an excellent choice for practitioners. These tools help in modeling, analyzing, and managing enterprise architectures effectively.

1.4 Referenced Techniques

References to key literature and their techniques within this Guide are intended to be representative. Other tools, techniques, and literature can readily be substituted. The goal is to provide a practical approach to developing, maintaining, and using an EA.

This Guide aims to be a practical companion for practitioners, helping them navigate the complexities of enterprise architecture using the TOGAF framework.

Part 2: Guidance on Enterprise Architecture

2.1 What is Enterprise Architecture?

Enterprise Architecture (EA) is a comprehensive framework used to align business strategy with technology solutions. It provides a blueprint that describes the structure and operation of an organization, aiming to determine how an organization can effectively achieve its current and future objectives.

2.2 Key Components of Enterprise Architecture

1. Business Architecture: Focuses on the business strategy, governance, organization, and key business processes.
2. Data Architecture: Describes the structure and management of the organization’s data resources and data management resources.
3. Application Architecture: Provides a blueprint for the individual application systems and the integration of the application systems.
4. Technology Architecture: Describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services.

2.3 Coordinating EA Development Across the EA Landscape

Coordinating EA development involves aligning various architectural domains to ensure consistency and coherence. This includes:

• Aligning Business and IT Strategies: Ensuring that the IT strategy supports the business goals.
• Integrating Different Architectural Domains: Ensuring that business, data, application, and technology architectures are integrated.
• Stakeholder Engagement: Involving stakeholders from different departments to ensure that the EA meets the needs of the entire organization.

2.4 Coordinating EA Development with the Business Cycle

EA development should be aligned with the business cycle to ensure that it remains relevant and valuable. This includes:

• Aligning with Strategic Planning: Ensuring that the EA supports the organization’s strategic goals.
• Supporting Operational Planning: Providing architectural guidance for day-to-day operations.
• Adapting to Change: Being flexible enough to adapt to changes in the business environment.

Part 3: Guidance on Developing an Enterprise Architecture

3.1 Using the Architecture Development Method (ADM)

The Architecture Development Method (ADM) is a core process of TOGAF that provides a step-by-step approach to developing an EA. The key phases of the ADM include:

1. Preliminary Phase: Establishing the architecture capability.
2. Phase A: Architecture Vision: Defining the scope, identifying stakeholders, creating the architecture vision, and getting approvals.
3. Phase B: Business Architecture: Developing the business architecture.
4. Phase C: Information Systems Architectures: Developing the data and application architectures.
5. Phase D: Technology Architecture: Developing the technology architecture.
6. Phase E: Opportunities and Solutions: Identifying and evaluating potential solutions.
7. Phase F: Migration Planning: Determining how to transition from the baseline to the target architecture.
8. Phase G: Implementation Governance: Providing architectural oversight of the implementation.
9. Phase H: Architecture Change Management: Establishing procedures for managing change to the new architecture.

3.2 Developing an Enterprise Architecture to Support Strategy

• Aligning with Business Strategy: Ensuring that the EA supports the organization’s strategic goals.
• Scenario Planning: Developing different scenarios to understand the impact of various strategic decisions.
• Roadmap Development: Creating a roadmap that outlines the steps needed to achieve the strategic goals.

3.3 Developing an Enterprise Architecture to Support Portfolio

• Portfolio Management: Ensuring that the EA supports the management of the organization’s portfolio of projects and programs.
• Prioritization: Prioritizing initiatives based on their alignment with the EA and business strategy.
• Resource Allocation: Allocating resources effectively to support the portfolio.

3.4 Developing an Enterprise Architecture to Support Project

• Project Planning: Ensuring that the EA supports the planning and execution of individual projects.
• Requirements Management: Managing requirements to ensure that they are aligned with the EA.
• Risk Management: Identifying and managing risks associated with the project.

3.5 Developing an Enterprise Architecture to Support Solution Delivery

• Solution Architecture: Developing the architecture for specific solutions.
• Integration: Ensuring that the solution integrates well with the existing architecture.
• Testing: Testing the solution to ensure that it meets the architectural requirements.

3.6 Special Cases

• Agile Development: Adapting the EA to support agile development methodologies.
• Incident Response: Using the EA to support incident response and business continuity.
• Mergers and Acquisitions: Adapting the EA to support mergers and acquisitions.

Part 4: Guidance on Using an Enterprise Architecture

4.1 What to Do When You Are Hip-Deep in Solution Delivery

• Stay Aligned with EA: Ensure that the solution delivery remains aligned with the EA.
• Continuous Improvement: Continuously improve the EA based on feedback from solution delivery.
• Governance: Ensure that the solution delivery adheres to the architectural governance processes.

4.2 Architecture in Action

• Agile Enterprise: Using the EA to support agile practices within the organization.
• Incident Response: Leveraging the EA to respond to incidents effectively.
• Business Continuity: Ensuring that the EA supports business continuity planning.

Part 5: Guidance on Maintaining an Enterprise Architecture

5.1 Managing Multiple Simultaneous Roadmaps

• Coordination: Coordinating multiple roadmaps to ensure that they are aligned with the EA.
• Prioritization: Prioritizing initiatives across different roadmaps.
• Resource Management: Managing resources effectively to support multiple roadmaps.

5.2 What to Do When You Are Hip-Deep in Solution Delivery

• Monitoring: Continuously monitoring the solution delivery to ensure alignment with the EA.
• Feedback Loop: Establishing a feedback loop to improve the EA based on solution delivery experiences.
• Adaptation: Adapting the EA as needed to support the solution delivery.

Part 6: Appendices

6.1 Useful Tables and Reference Models

• Frameworks: List of frameworks that support the TOGAF ADM.
• Reference Models: Reference models that can be used to guide the development of the EA.
• Tools and Techniques: Tools and techniques that support the development, maintenance, and use of the EA.

Conclusion

This comprehensive guide provides practical advice and insights for practitioners tasked with developing, maintaining, and using an Enterprise Architecture (EA) using the TOGAF framework. By following the guidance outlined in this document, practitioners can ensure that their EA aligns with business strategy, supports operational needs, and adapts to changes in the business environment. The TOGAF framework’s universal scaffolding, combined with the practical approach outlined in this guide, enables practitioners to create a robust and valuable EA that delivers predictable value to the organization.