Introduction
The TOGAF® Architecture Development Method (ADM) is a comprehensive framework for developing enterprise architecture. Integrating Agile methodologies, particularly sprints, into the TOGAF ADM enhances flexibility, speed, and adaptability in architectural planning and execution. This guide provides a detailed overview of how to apply the TOGAF ADM using Agile sprints, drawing from best practices and industry insights.
Understanding the TOGAF ADM
The TOGAF ADM is a core method within the TOGAF framework, providing a step-by-step approach to developing enterprise architecture. It consists of several phases, from preliminary activities to architecture change management. Traditionally, the ADM has been perceived as a rigid, waterfall-like process. However, it can be adapted to incorporate Agile practices, making it more flexible and responsive to change1.
Integrating Agile Sprints with TOGAF ADM
1. Preliminary Phase
Objectives:
- Establish the architecture capability.
- Define the architecture principles.
- Set up the architecture governance.
Agile Integration:
- Sprint Planning: Include tasks for setting up the architecture capability and defining principles in the initial sprints.
- Stakeholder Engagement: Use Agile workshops to engage stakeholders in defining principles and governance.
Artifacts and Deliverables:
- Architecture Principles: Guiding principles for the architecture development.
- Architecture Governance Framework: Rules and processes for governing the architecture.
- Stakeholder List: Identified stakeholders and their roles.
- Architecture Vision Document: Initial vision and scope of the architecture.
- Stakeholder Engagement Plan: Plan for engaging stakeholders throughout the process.
- Initial Backlog: Initial set of user stories and epics for the architecture vision.
2. Phase A: Architecture Vision
Objectives:
- Define the scope.
- Identify stakeholders.
- Create the architecture vision.
Agile Integration:
- Backlog Creation: Create a product backlog with user stories and epics that define the architecture vision.
- Sprint Goals: Set sprint goals to develop the architecture vision incrementally.
- Stakeholder Feedback: Regularly gather feedback from stakeholders through sprint reviews.
Artifacts and Deliverables:
- Stakeholder Map: Visual representation of stakeholders and their interests.
- Business Scenarios: Descriptions of business situations and their impact on the architecture.
- Architecture Vision: High-level vision and scope of the architecture.
- Architecture Vision Document: Detailed document outlining the architecture vision.
- Stakeholder Requirements: Documented requirements gathered from stakeholders.
- Initial Architecture Backlog: Backlog of user stories and epics for the architecture vision.
3. Phase B: Business Architecture
Objectives:
- Develop the business architecture.
- Define the business capabilities and processes.
Agile Integration:
- Iterative Development: Use sprints to iteratively develop the business architecture.
- User Stories: Create user stories for business capabilities and processes.
- Continuous Feedback: Incorporate feedback from business stakeholders in each sprint.
Artifacts and Deliverables:
- Business Capability Map: Visual representation of business capabilities.
- Business Process Models: Models of business processes and workflows.
- Organization Structure: Description of the organizational structure and roles.
- Business Architecture Document: Detailed document outlining the business architecture.
- Business Capability Catalog: Catalog of business capabilities and their descriptions.
- Business Process Catalog: Catalog of business processes and their descriptions.
4. Phase C: Information Systems Architecture
Objectives:
- Develop the data and application architectures.
- Define the data management resources and application systems.
Agile Integration:
- Sprint Planning: Plan sprints to focus on specific data and application components.
- Incremental Delivery: Deliver data and application architecture components incrementally.
- Collaboration: Collaborate closely with data and application teams in Agile ceremonies.
Artifacts and Deliverables:
- Data Models: Models of data entities and their relationships.
- Application Portfolio: Catalog of applications and their interactions.
- Data Management Strategies: Strategies for managing data within the architecture.
- Information Systems Architecture Document: Detailed document outlining the information systems architecture.
- Data Architecture Catalog: Catalog of data entities and their descriptions.
- Application Architecture Catalog: Catalog of applications and their descriptions.
5. Phase D: Technology Architecture
Objectives:
- Develop the technology architecture.
- Define the technology components and standards.
Agile Integration:
- Sprint Goals: Set sprint goals to develop and integrate technology components.
- Continuous Integration: Use continuous integration practices to ensure technology components are integrated and tested regularly.
- Feedback Loops: Establish feedback loops with technology stakeholders to refine the architecture.
Artifacts and Deliverables:
- Technology Standards: Standards and guidelines for technology components.
- Technology Portfolio: Catalog of technology components and their interactions.
- Infrastructure Models: Models of the technology infrastructure.
- Technology Architecture Document: Detailed document outlining the technology architecture.
- Technology Standards Catalog: Catalog of technology standards and guidelines.
- Infrastructure Catalog: Catalog of infrastructure components and their descriptions.
6. Phase E: Opportunities and Solutions
Objectives:
- Identify and evaluate potential solutions.
- Select the best-fit architecture.
Agile Integration:
- Sprint Planning: Plan sprints to evaluate and select solutions.
- Prototyping: Use Agile prototyping to test potential solutions.
- Stakeholder Involvement: Involve stakeholders in solution evaluation through sprint reviews and demos.
Artifacts and Deliverables:
- Solution Building Blocks (SBBs): Reusable components for building solutions.
- Solution Architecture: Detailed architecture for specific solutions.
- Solution Evaluation Criteria: Criteria for evaluating potential solutions.
- Solution Architecture Document: Detailed document outlining the solution architecture.
- Solution Evaluation Report: Report on the evaluation of potential solutions.
- Selected Solution: Documentation of the selected solution and its rationale.
7. Phase F: Migration Planning
Objectives:
- Develop the migration plan.
- Define the transition architectures.
Agile Integration:
- Sprint Goals: Set sprint goals to develop and refine the migration plan.
- Incremental Planning: Develop the migration plan incrementally, focusing on high-priority transitions.
- Feedback: Gather feedback from implementation teams to refine the migration plan.
Artifacts and Deliverables:
- Migration Strategy: Strategy for migrating to the target architecture.
- Transition Architectures: Intermediate architectures for transitioning to the target architecture.
- Migration Plan: Detailed plan for migrating to the target architecture.
- Migration Planning Document: Detailed document outlining the migration plan.
- Transition Architecture Catalog: Catalog of transition architectures and their descriptions.
- Migration Roadmap: Visual roadmap for the migration process.
8. Phase G: Implementation Governance
Objectives:
- Provide governance for the implementation.
- Ensure compliance with the architecture.
Agile Integration:
- Sprint Reviews: Use sprint reviews to monitor implementation progress and compliance.
- Continuous Governance: Apply continuous governance practices to ensure alignment with the architecture.
- Feedback Loops: Establish feedback loops with implementation teams to address any governance issues.
Artifacts and Deliverables:
- Governance Framework: Framework for governing the implementation.
- Compliance Checklists: Checklists for ensuring compliance with the architecture.
- Implementation Metrics: Metrics for monitoring the implementation progress.
- Implementation Governance Document: Detailed document outlining the implementation governance.
- Compliance Reports: Reports on the compliance status of the implementation.
- Implementation Dashboard: Dashboard for monitoring the implementation progress.
9. Phase H: Architecture Change Management
Objectives:
- Manage changes to the architecture.
- Ensure the architecture remains relevant.
Agile Integration:
- Kanban Backlog: Manage architecture changes using a Kanban backlog.
- Continuous Improvement: Use retrospectives to identify areas for continuous improvement.
- Stakeholder Engagement: Engage stakeholders in the change management process through regular Agile ceremonies.
Artifacts and Deliverables:
- Change Management Plan: Plan for managing changes to the architecture.
- Change Request Forms: Forms for requesting changes to the architecture.
- Change Impact Assessments: Assessments of the impact of proposed changes.
- Architecture Change Management Document: Detailed document outlining the change management process.
- Change Request Catalog: Catalog of change requests and their status.
- Change Impact Reports: Reports on the impact of proposed changes.
TOGAF ADM Agile Sprint Process
| ADM Phase | Key Activities | Agile Practices | Artifacts | Deliverables | Benefits |
|---|---|---|---|---|---|
| Preliminary Phase | – Establish architecture capability – Define architecture principles – Set up architecture governance |
– Sprint planning for initial setup – Stakeholder engagement workshops – Incremental definition of principles and governance |
– Architecture Principles – Architecture Governance Framework – Stakeholder List |
– Architecture Vision Document – Stakeholder Engagement Plan – Initial Backlog |
– Structured foundation for Agile architecture – Early stakeholder buy-in – Flexible governance framework |
| Phase A: Architecture Vision | – Define scope – Identify stakeholders – Create architecture vision |
– Backlog creation with user stories and epics – Sprint goals for vision development – Regular stakeholder feedback through sprint reviews |
– Stakeholder Map – Business Scenarios – Architecture Vision |
– Architecture Vision Document – Stakeholder Requirements – Initial Architecture Backlog |
– Clear and shared vision – Incremental development – Continuous stakeholder alignment |
| Phase B: Business Architecture | – Develop business architecture – Define business capabilities and processes |
– Iterative development through sprints – User stories for business components – Continuous feedback from business stakeholders |
– Business Capability Map – Business Process Models – Organization Structure |
– Business Architecture Document – Business Capability Catalog – Business Process Catalog |
– Responsive business architecture – Incremental delivery – Alignment with business needs |
| Phase C: Information Systems Architecture | – Develop data and application architectures – Define data management resources and application systems |
– Sprint planning for data and application components – Incremental delivery of architecture components – Close collaboration with data and application teams |
– Data Models – Application Portfolio – Data Management Strategies |
– Information Systems Architecture Document – Data Architecture Catalog – Application Architecture Catalog |
– Integrated data and application architecture – Continuous integration – Feedback-driven refinement |
| Phase D: Technology Architecture | – Develop technology architecture – Define technology components and standards |
– Sprint goals for technology components – Continuous integration practices – Feedback loops with technology stakeholders |
– Technology Standards – Technology Portfolio – Infrastructure Models |
– Technology Architecture Document – Technology Standards Catalog – Infrastructure Catalog |
– Robust technology architecture – Regular testing and integration – Stakeholder-driven improvements |
| Phase E: Opportunities and Solutions | – Identify and evaluate potential solutions – Select best-fit architecture |
– Sprint planning for solution evaluation – Agile prototyping for testing solutions – Stakeholder involvement in solution selection |
– Solution Building Blocks (SBBs) – Solution Architecture – Solution Evaluation Criteria |
– Solution Architecture Document – Solution Evaluation Report – Selected Solution |
– Informed solution selection – Rapid prototyping – Stakeholder-validated solutions |
| Phase F: Migration Planning | – Develop migration plan – Define transition architectures |
– Sprint goals for migration planning – Incremental planning for high-priority transitions – Feedback from implementation teams |
– Migration Strategy – Transition Architectures – Migration Plan |
– Migration Planning Document – Transition Architecture Catalog – Migration Roadmap |
– Structured migration plan – Incremental transition planning – Feedback-driven refinement |
| Phase G: Implementation Governance | – Provide governance for implementation – Ensure compliance with architecture |
– Sprint reviews for implementation progress – Continuous governance practices – Feedback loops with implementation teams |
– Governance Framework – Compliance Checklists – Implementation Metrics |
– Implementation Governance Document – Compliance Reports – Implementation Dashboard |
– Effective implementation governance – Continuous compliance monitoring – Address governance issues promptly |
| Phase H: Architecture Change Management | – Manage architecture changes – Ensure architecture remains relevant |
– Kanban backlog for change management – Continuous improvement through retrospectives – Stakeholder engagement in change management |
– Change Management Plan – Change Request Forms – Change Impact Assessments |
– Architecture Change Management Document – Change Request Catalog – Change Impact Reports |
– Structured change management – Continuous improvement – Stakeholder-driven change management |
This table provides a comprehensive summary of the entire process of integrating Agile methodologies with the TOGAF ADM, highlighting the key activities, Agile practices, artifacts, deliverables, and benefits associated with each phase.
Agile Practices for Artifacts and Deliverables
Backlog Management:
- User Stories and Epics: Create user stories and epics for each phase to capture requirements and deliverables.
- Prioritization: Prioritize backlog items based on business value and stakeholder feedback.
Sprint Planning:
- Sprint Goals: Define clear sprint goals for each phase to focus on specific artifacts and deliverables.
- Task Breakdown: Break down tasks into manageable units for each sprint.
Continuous Integration and Delivery:
- Incremental Delivery: Deliver artifacts and deliverables incrementally through sprints.
- Continuous Feedback: Gather continuous feedback from stakeholders to refine artifacts and deliverables.
Collaboration and Feedback:
- Agile Ceremonies: Use Agile ceremonies like daily stand-ups, sprint planning, reviews, and retrospectives to foster collaboration.
- Stakeholder Engagement: Engage stakeholders continuously through Agile practices to ensure alignment and gather feedback.
Benefits of Integrating Agile with TOGAF ADM
- Faster Delivery: Agile practices enable faster delivery of architecture outputs.
- Increased Flexibility: Agile methodologies provide the flexibility to adapt to changing requirements and business needs.
- Enhanced Collaboration: Agile practices foster better collaboration among stakeholders and teams.
- Continuous Improvement: Agile retrospectives and feedback loops ensure continuous improvement of the architecture artifacts and deliverables.
Conclusion
Integrating Agile methodologies with the TOGAF ADM creates a more responsive and iterative approach to enterprise architecture development. By leveraging Agile practices like sprints, backlog management, continuous integration, and stakeholder engagement, organizations can enhance the flexibility, speed, and effectiveness of their architecture development process. This integrated approach ensures that the enterprise architecture remains relevant, adaptable, and aligned with business needs, with clear artifacts and deliverables for each phase.
TOGAF, ADM and ArchiMate Tools Resources
Cybermedian
- TOGAF ADM Overview and Importance
- Title: TOGAF ADM : Qu’est-ce que c’est et pourquoi est-ce si important ?
- URL: Cybermedian
- Description: An overview of TOGAF ADM, its importance, and how it helps organizations develop a coherent enterprise architecture.
- Introduction to TOGAF ADM
- Title: Introduction à la méthode de développement d’architecture TOGAF (ADM)
- URL: Cybermedian
- Description: A detailed introduction to the TOGAF Architecture Development Method (ADM), its phases, and its application in enterprise architecture development.
- TOGAF ADM Phase A: Architecture Vision
- Title: TOGAF ADM Phase A (Part 1 of 4) — Architecture Vision
- URL: Cybermedian
- Description: Explanation of the Architecture Vision phase in TOGAF ADM, including its purpose and key activities.
- Free Online ArchiMate Tool
- Title: Free Online ArchiMate Tool + Examples
- URL: Cybermedian
- Description: An overview of the ArchiMate language and its integration with TOGAF ADM, including examples and tools for modeling enterprise architecture.
- TOGAF ADM Automated Workflow Management
- Title: TOGAF ADM Automated Workflow Management
- URL: Cybermedian
- Description: A guide on managing the development of TOGAF ADM deliverables using automated workflow management tools.
ArchiMetric
- TOGAF Tool for Enterprise Architecture
- Title: TOGAF® Tool for Enterprise Architecture
- URL: ArchiMetric
- Description: An overview of the TOGAF tool for enterprise architecture, including its features and how it supports the TOGAF ADM process.
- Using BPMN with TOGAF ADM and ArchiMate
- Title: Using BPMN to Supplement TOGAF ADM EA Development Together with ArchiMate
- URL: ArchiMetric
- Description: A guide on integrating BPMN with TOGAF ADM and ArchiMate to enhance enterprise architecture development.
- What is TOGAF?
- Title: What is TOGAF?
- URL: ArchiMetric
- Description: An introduction to TOGAF, its architecture development method (ADM), and its application in enterprise architecture.
- TOGAF from Concepts to Deliverables
- Title: TOGAF from Concepts to Deliverable
- URL: ArchiMetric
- Description: A step-by-step guide on applying TOGAF ADM to develop enterprise architecture deliverables.
- Understanding Abstraction in the ArchiMate Language
- Title: Understanding Abstraction in the ArchiMate Language
- URL: ArchiMetric
- Description: An explanation of abstraction concepts in the ArchiMate language and their application in enterprise architecture modeling.
Visual Paradigm
- Using ArchiMate with TOGAF ADM
- Title: Using ArchiMate with TOGAF ADM
- URL: Visual Paradigm
- Description: An article explaining how ArchiMate complements TOGAF ADM in enterprise architecture development.
- TOGAF Integrated with ArchiMate
- Title: How TOGAF Integrated with ArchiMate?
- URL: Visual Paradigm
- Description: A detailed guide on how TOGAF ADM integrates with ArchiMate for comprehensive enterprise architecture development.
- TOGAF ADM Tutorial
- Title: TOGAF ADM Tutorial
- URL: Visual Paradigm
- Description: A comprehensive tutorial covering core TOGAF and ArchiMate concepts, including an outline of all ADM phases.
- Case Study: Using ArchiMate with TOGAF
- Title: Case Study: Using ArchiMate with TOGAF
- URL: Visual Paradigm
- Description: A case study demonstrating the use of ArchiMate with TOGAF ADM in enterprise architecture development.
- Using ArchiMate Tool with TOGAF ADM
- Title: Using ArchiMate Tool with TOGAF ADM
- URL: Visual Paradigm
- Description: An explanation of how an ArchiMate tool with TOGAF support can aid in enterprise architecture initiatives.
- Understanding the Differences between ArchiMate and TOGAF
- Title: Understanding the Differences between ArchiMate and TOGAF: A Guide for Enterprise Architects
- URL: Visual Paradigm
- Description: A guide comparing ArchiMate and TOGAF, highlighting their key differences and applications in enterprise architecture.
- Enhancing TOGAF ADM with ArchiMate
- Title: Enhancing TOGAF ADM with ArchiMate: An Agile Visual Modeling Approach (PART 1)
- URL: Visual Paradigm
- Description: A study guide on enhancing TOGAF ADM with ArchiMate using an agile visual modeling approach.
- Architectural Artifacts in TOGAF ADM
- Title: Architectural Artifacts in TOGAF ADM: A Comprehensive Overview
- URL: Visual Paradigm
- Description: A comprehensive overview of architectural artifacts in TOGAF ADM and their significance in enterprise architecture development.
- Step-by-Step Enterprise Architecture Tutorial with TOGAF
- Title: Step-by-Step Enterprise Architecture Tutorial with TOGAF
- URL: Visual Paradigm
- Description: A step-by-step tutorial on developing enterprise architecture with TOGAF ADM using Visual Paradigm’s tools.