Tailoring the TOGAF Framework

Tailoring the TOGAF Framework: A Comprehensive Guide for Foundation Certification

Why Tailoring the TOGAF Framework is Important

Tailoring the TOGAF framework is crucial because organizations vary significantly in size, complexity, maturity, and industry sector. A one-size-fits-all approach to enterprise architecture would be impractical and inefficient. By tailoring TOGAF, organizations can:

• Optimize Resource Allocation: Apply only the necessary phases and processes relevant to the organization's current state and objectives
• Reduce Time to Value: Accelerate architecture delivery by focusing on essential activities
• Improve Adoption: Make the framework more relevant and acceptable to stakeholders who might otherwise resist a rigid approach
• Address Specific Needs: Accommodate industry-specific regulations, governance structures, and technical environments
• Support Different Types of Engagements: Adapt to strategic initiatives, transformations, or incremental improvements
• Enhance Effectiveness: Ensure the framework works within existing organizational constraints and culture

What is Tailoring the TOGAF Framework?

Tailoring is the process of adapting and customizing the TOGAF framework to fit the specific needs, constraints, and context of an individual organization. This is one of the preliminary phase considerations and represents a fundamental principle of TOGAF: it is a framework, not a rigid methodology.

Tailoring involves making conscious decisions about:

• Which phases and steps to execute in the ADM (Architecture Development Method)
• What level of detail to include in architecture descriptions and artifacts
• Which techniques and tools to employ
• How to integrate with existing processes and governance structures
• What governance and change management approaches to adopt
• How to sequence activities based on organizational priorities
• What roles and responsibilities structure to establish
• How to manage stakeholders and communications

Tailoring is not about eliminating TOGAF principles or creating a completely new framework. Rather, it's about intelligent application of TOGAF's components to match organizational context.

How Tailoring the TOGAF Framework Works

1. Understand the Organization's Context

Before tailoring, you must thoroughly understand:

• Current state: Existing processes, governance, maturity level, and technical landscape
• Strategic objectives: What the organization is trying to achieve
• Constraints: Budget limitations, time pressures, regulatory requirements, existing commitments
• Culture and readiness: How receptive stakeholders are to change, existing architectural practices
• Scale: Size of the organization, complexity of the IT environment, geographic distribution
• Industry and regulatory environment: Specific requirements from regulations or industry standards

2. Identify Tailoring Dimensions

Consider how to tailor across multiple dimensions:

ADM Tailoring: Decide which phases to include, compress, or iterate differently
• Full ADM cycle may not be necessary for all engagements
• Some organizations may need to iterate certain phases
• Crisis situations might require accelerated or abbreviated cycles
• Incremental architecture delivery may suit some organizations better

Scope Tailoring: Determine the breadth and depth of the architecture effort
• Enterprise-wide architecture vs. specific domain
• Strategic vs. tactical architecture work
• Depth of detail appropriate for the audience

Detail and Documentation Tailoring: Adjust the level of artifacts and documentation
• Detailed documentation for heavily regulated industries
• Lighter documentation for agile environments
• Modular, reusable components vs. comprehensive repositories

Tools and Techniques Tailoring: Select methods appropriate to the organization
• Which architecture frameworks or models to use
• Visualization techniques most effective for stakeholders
• Integration with existing tools and methods
• Modeling languages and standards to employ

Governance and Change Tailoring: Adapt governance structures and change management
• Fit within existing governance boards and committees
• Risk management approaches
• Change control and approval processes
• Communication and stakeholder management strategies

3. Define the Tailored Approach

Document decisions about tailoring in:

• Architecture Governance: Define how architecture decisions will be made and enforced
• ADM Customization: Create a detailed plan showing which phases, steps, and techniques will be used
• Reference Materials: Identify which TOGAF content will guide the work
• Tools and Techniques: Specify the methods and tools that will be employed
• Roles and Responsibilities: Define who will do what in the architecture effort

4. Balance Tailoring with TOGAF Principles

Effective tailoring maintains core TOGAF concepts:

• Keep the structured, phase-based approach even if modified
• Maintain focus on business objectives
• Use TOGAF's core concepts and terminology
• Ensure stakeholder engagement remains central
• Preserve the iterative nature when appropriate
• Document all architecture work systematically

Common Tailoring Scenarios

Large, Complex Organizations:
• May tailor to include multiple architecture domains (business, data, application, technology)
• Might implement the ADM at enterprise level and department level
• Could involve extended governance with multiple review boards
• May emphasize detailed documentation and standards

Small Organizations:
• May combine phases and compress the ADM cycle
• Could focus on critical architecture decisions only
• Might use simplified documentation and lightweight governance
• May integrate with existing IT planning processes rather than separate architecture practice

Agile Environments:
• May adapt ADM to iterative cycles aligned with agile releases
• Could use less formal documentation, more collaborative methods
• Might integrate architecture and agile development practices
• May emphasize working solutions over comprehensive documentation

Regulated Industries (Financial, Healthcare, Government):
• May require detailed architecture documentation for compliance
• Could demand extensive change governance and audit trails
• Might include specific security and compliance considerations
• May integrate with existing regulatory and compliance frameworks

Rapid Transformation Scenarios:
• May abbreviate certain phases to accelerate delivery
• Could focus on critical architecture decisions
• Might use agile or iterative approaches rather than waterfall
• May prioritize working solutions over perfect documentation

How to Answer Exam Questions on Tailoring the TOGAF Framework

Understanding Question Types

Exam questions on tailoring typically fall into these categories:

1. Definition Questions: "What is tailoring of the TOGAF framework?"
2. Rationale Questions: "Why is tailoring important?"
3. Application Questions: "Which of these scenarios requires tailoring? How?"
4. Process Questions: "What are the steps in tailoring?"
5. Constraint Questions: "What should you consider when tailoring?"

Key Concepts to Remember

• TOGAF is a framework, not a methodology: This foundational concept justifies why tailoring is not just acceptable but necessary
• Tailoring is not elimination: You're adapting, not removing TOGAF principles
• Context matters: All tailoring decisions must be justified by organizational context
• Maintain core values: Business focus, structured approach, stakeholder engagement remain central
• Documentation of tailoring: The tailoring decisions should be explicit and documented
• Iterative refinement: Tailoring itself may evolve as the organization matures

Common Correct Answer Patterns

When answering tailoring questions, look for these patterns in correct answers:

• References to organizational context or specific needs
• Mentions of maintaining TOGAF principles while adapting execution
• Discussion of multiple dimensions (scope, detail, governance, tools)
• Emphasis on documented decisions about the approach
• Integration with existing processes and governance
• Acknowledgment that different organizations will tailor differently
• Recognition that tailoring should align with business objectives

Common Incorrect Answer Patterns to Avoid

• Suggesting you should ignore TOGAF components rather than adapt them
• Implying tailoring means creating an entirely different framework
• Failing to consider organizational context in tailoring decisions
• Suggesting tailoring eliminates the need for architecture governance
• Implying all organizations should tailor in the same way
• Removing core TOGAF concepts rather than adapting their implementation
• Suggesting tailoring can be done without documenting the decisions

Exam Tips: Answering Questions on Tailoring the TOGAF Framework

Tip 1: Remember the Framework Philosophy

Always start with the principle that TOGAF is explicitly designed as a framework, not a rigid methodology. This is mentioned repeatedly throughout TOGAF documentation to justify why tailoring is not just allowed but necessary. When you see a question about tailoring, this foundational principle should guide your thinking.

Tip 2: Look for the Context Clue

Exam questions about tailoring will almost always include context about an organization. Read this carefully:

• Size of organization: Large enterprises need different tailoring than small businesses
• Industry or regulatory requirements: Financial institutions, healthcare, government agencies need compliance-focused tailoring
• Existing processes: If the organization already has architecture or governance practices, tailoring should integrate with them
• Maturity level: Immature organizations need simpler tailoring; mature organizations can use more complex approaches
• Time or budget constraints: These may require abbreviated approaches
• Strategic objectives: What the organization is trying to achieve drives tailoring decisions

Tip 3: Tailoring is Active Decision-Making

Correct answers will describe tailoring as making deliberate choices about which TOGAF components to use and how to use them. Incorrect answers might suggest tailoring is passive or automatic. Look for answers that show:

• Analysis of organizational context
• Deliberate selection of which ADM phases to include
• Intentional decisions about detail levels and documentation
• Conscious choices about governance structures
• Planned integration with existing processes

Tip 4: Balance is Key

The correct approach to tailoring maintains tension between adaptation and consistency:

• You adapt the execution of TOGAF to organizational context
• You maintain the principles and concepts of TOGAF across all tailoring
• You can abbreviate or compress the ADM, but you don't eliminate its structured nature
• You can lighten documentation for agile environments, but you still document architecture decisions
• You can integrate with existing governance, but you maintain architecture governance

When answering, look for answers showing this balance rather than those going to extremes in either direction.

Tip 5: ADM Tailoring is Specific

Questions often ask specifically about tailoring the ADM. Remember these tailoring options:

• Which phases to include: Not all engagements require all phases
• Iteration patterns: You might cycle through phases multiple times
• Parallel execution: Some phases might run concurrently in large organizations
• Phase abbreviation: You can compress phases where context allows
• Incremental delivery: You might deliver architecture across multiple iterations
• Starting point variation: You don't always start at Phase A; context determines entry point

However, you should maintain the logical sequence of the phases and not skip critical thinking represented by each phase, even if executed differently.

Tip 6: Documentation Tailoring Must Still Occur

A common exam trap: suggesting that tailoring means not documenting architecture work. This is incorrect. Tailoring documentation might mean:

• Less formal documentation in some contexts (lighter weight artifacts)
• More focused documentation on critical decisions
• Different formats suited to audience preferences
• Modular documentation for reuse and agility
• Integration with existing documentation standards

But architecture decisions must still be documented in whatever form is appropriate to the organization.

Tip 7: Governance Tailoring is Crucial

Questions often test understanding that tailoring must address governance. Key points:

• Tailoring should fit into existing governance structures where possible
• Architecture governance is not eliminated by tailoring, but its structure may change
• Decision-making authority must be clearly defined in the tailored approach
• Change control processes should be integrated with existing change management
• Stakeholder engagement mechanisms should be appropriate to organizational culture

Tip 8: Preliminary Phase Connection

Remember that tailoring decisions are typically made in the Preliminary Phase of the ADM. Questions might test whether you understand:

• Tailoring is not a separate phase but done within Preliminary
• Preliminary Phase is where you define the approach that will be used
• Tailoring decisions in Preliminary govern how all subsequent phases are executed
• If tailoring decisions change, they're typically revisited in subsequent iterations

Tip 9: Avoid Absolutes

Exam questions on tailoring almost never have one right answer for all organizations. Be suspicious of answer choices that say things like:

• "The TOGAF framework always requires..."
• "All organizations must include all ADM phases"
• "Tailoring means eliminating..."
• "Documentation is not necessary when..."

Correct answers will usually be more nuanced, referencing organizational context or saying things like "may be tailored based on" or "should be adapted to"

Tip 10: Read the Organization Description Carefully

Most scenario questions about tailoring include a detailed description of an organization. The correct answer will reference specific details from that description. For example:

• If the scenario mentions a startup, look for answers about lightweight tailoring
• If it mentions a financial institution, look for answers about compliance and governance
• If it mentions existing architecture practices, look for integration with those practices
• If it mentions time pressure, look for answers about abbreviating phases
• If it mentions multiple business units, look for domain-specific tailoring

The scenario details are clues to what the correct answer should emphasize.

Tip 11: Integration is a Tailoring Goal

A key principle in exam answers: tailoring should aim to integrate TOGAF with existing practices rather than replacing them. Look for answers that discuss:

• How to align TOGAF with existing IT governance
• How to map TOGAF roles to existing organizational roles
• How to integrate architecture work with project management or agile practices
• How to use TOGAF concepts with existing methodology frameworks
• How to combine TOGAF with other standards (ITIL, COBIT, ISO/IEC standards)

Tip 12: Preliminary Phase Artifacts

Questions might ask what artifacts document tailoring decisions. Key artifacts from Preliminary Phase include:

• Statement of Architecture Work: Describes the approach including tailoring
• Architecture Governance documentation: Describes tailored governance approach
• ADM Customization: Describes how ADM will be tailored
• Reference Materials: Identifies which TOGAF and other materials will be used
• Tools and Techniques: Documents tailored tools and techniques

When asked about how tailoring is documented, reference these artifacts.

Sample Exam Question Pattern

Question: "A large financial services organization with mature existing architecture practices and strict regulatory requirements wants to implement TOGAF. They have expressed concerns about the time required for a full ADM cycle. How should the architecture team tailor TOGAF for this organization?"

Key Elements to Address in Your Answer:

• Acknowledge the regulatory requirements (must be maintained, not eliminated)
• Note the existing architecture practices (should be integrated, not replaced)
• Address the time concerns (can optimize or compress, but maintain rigor)
• Reference the organization's maturity (can use more sophisticated approaches)
• Describe how to document the tailored approach (in Preliminary Phase)
• Explain how to maintain TOGAF principles (business focus, governance, stakeholder engagement)

What NOT to Include:

• Don't suggest eliminating regulatory compliance documentation
• Don't propose replacing TOGAF with something entirely different
• Don't suggest a quick shortcut that bypasses critical thinking
• Don't imply that existing practices should be ignored
• Don't recommend avoiding governance or change control

Summary: Tailoring for Success on Exam Day

When you encounter questions about tailoring the TOGAF framework on your exam, remember these core principles:

1. TOGAF is a framework - this justifies why tailoring is not just acceptable but essential
2. Tailor with purpose - all tailoring decisions should be driven by organizational context and business objectives
3. Balance adaptation and consistency - adapt execution while maintaining TOGAF principles
4. Document your decisions - tailoring is formalized in Preliminary Phase artifacts
5. Maintain core practices - don't eliminate governance, architecture thinking, or business focus
6. Integrate, don't replace - fit TOGAF with existing processes and practices
7. Context is king - different organizations will tailor differently based on their specific situation

By mastering these concepts, you'll be well-prepared to answer any exam question about tailoring the TOGAF framework.