Definition of an Enterprise

Definition of an Enterprise: TOGAF 10 Foundation Guide

Introduction

The Definition of an Enterprise is a foundational concept in TOGAF 10 that establishes what constitutes an enterprise from an architectural perspective. This concept is critical for enterprise architects as it provides clarity on the scope and boundaries of architectural work.

Why This Concept Is Important

Understanding the definition of an enterprise is crucial because:

• Scope Clarity: It helps define the boundaries of the enterprise architecture effort, determining what is included and excluded from architectural initiatives.
• Stakeholder Alignment: It ensures all stakeholders have a common understanding of what organization or organizational unit is being addressed.
• Architecture Governance: It establishes clear parameters for governance structures and decision-making authority within the architecture practice.
• Resource Planning: It helps determine what resources, systems, and business processes are within scope for transformation.
• Strategic Alignment: It ensures architectural decisions are made within the proper organizational context and strategic objectives.

What Is Definition of an Enterprise?

In TOGAF 10, an enterprise is defined as any collection of organizations that is bound together by a set of shared goals and objectives. Key characteristics include:

• Not Limited to Single Organizations: An enterprise can encompass multiple organizations, business units, departments, or even combinations of organizations within a larger organizational structure.
• Shared Goals and Objectives: The defining characteristic is that all parts operate toward common strategic goals and objectives.
• Diverse Structures: An enterprise might be a government department, a private company, a nonprofit organization, or a consortium of organizations working together.
• Flexibility: The enterprise definition is flexible and context-dependent, varying based on the scope of the architecture effort and organizational structure.
• Operational Integration: While not necessarily technically integrated, there is operational coordination and strategic alignment across the defined enterprise.

How It Works

The Definition of an Enterprise operates within TOGAF through several mechanisms:

1. Scope Definition
When beginning an architecture engagement, architects must first define what constitutes the enterprise. This involves:

• Identifying organizational boundaries
• Determining which business units are included
• Clarifying the extent of IT systems to be considered
• Establishing whether external partners or suppliers are included

2. Architecture Governance Structure
The enterprise definition directly influences:

• Who makes architectural decisions
• Which governance bodies are established
• The authority and responsibility of the Architecture Board
• Escalation paths and decision-making processes

3. Architecture Repository and Assets
The enterprise scope determines:

• What assets are stored in the architecture repository
• What standards and baselines apply
• Which architecture patterns and reusable components are relevant

4. ADM (Architecture Development Method) Application
The enterprise definition shapes:

• The scope of Phase A: Architecture Vision
• Which business units participate in architecture development
• How requirements are gathered and validated
• Which implementation programs are considered

5. Stakeholder Engagement
Understanding the enterprise definition helps identify:

Practical Examples of Enterprise Definitions

Example 1: Single Organization
A manufacturing company with headquarters and three regional factories might define its enterprise as all operations within these four locations, including headquarters functions.

Example 2: Multi-Division Organization
A large financial services company might define its enterprise to include retail banking, wealth management, and corporate banking divisions, but exclude the independent insurance subsidiary.

Example 3: Government Entity
A government agency might define its enterprise to include headquarters, regional offices, and partner agencies that share common objectives within the public mission.

Example 4: Consortium
Multiple healthcare providers working together on a shared patient record system might define the enterprise as all participating hospitals and clinics bound by the shared goal of improving patient care coordination.

Key Principles for Defining an Enterprise

• Clear Boundaries: The enterprise boundaries must be clearly documented and understood by all stakeholders.
• Purpose-Driven: The definition should align with the purpose of the architecture engagement.
• Strategic Alignment: The enterprise definition should reflect the organization's strategic intent and structure.
• Inclusivity vs. Manageability: The scope should be inclusive enough to capture interdependencies but manageable for effective architecture work.
• Flexibility: While defined clearly, the enterprise definition may be revisited as the architecture work progresses and organizational context changes.

Exam Tips: Answering Questions on Definition of an Enterprise

Tip 1: Focus on Shared Goals and Objectives
When answering exam questions, remember that the key defining characteristic of an enterprise in TOGAF is that it is bound together by shared goals and objectives. If a question asks what makes something an enterprise, the shared goals element is critical.

Tip 2: Recognize That Enterprise ≠ Single Organization
A common misconception is that an enterprise equals one company or organization. In TOGAF, an enterprise can be:

Exam questions often test whether you understand this flexibility. If a question presents a scenario with multiple organizations sharing objectives, this can constitute an enterprise.

Tip 3: Link Enterprise Definition to Scope
Questions often require you to connect enterprise definition to architecture scope. Remember that defining the enterprise is the first step in scoping the architecture engagement. Look for questions that ask about boundaries, scope, or what should be included in the architecture effort.

Tip 4: Distinguish From Architecture Governance
While the enterprise definition influences governance, they are not the same thing. The enterprise definition is what is being architected; governance is how architectural decisions are made. Exam questions may ask you to differentiate between these concepts.

Tip 5: Use the ADM Connection
Questions may ask how enterprise definition impacts the ADM process. The key points to remember are:

• Phase A uses the enterprise definition to scope the architecture vision
• The definition affects who participates in each ADM phase
• It determines what baseline and target architectures are relevant

Tip 6: Recognize Practical Application Scenarios
Exam questions often present real-world scenarios asking you to identify an enterprise or define its boundaries. For example:

• A retail company with three product divisions and a shared IT department wants to implement a unified CRM. Which divisions should be included in the enterprise definition?
• Two competing companies form a joint venture. How should the enterprise be defined for this initiative?

Approach these by asking: What shared goals bind these entities together? What are the natural operational boundaries?

Tip 7: Watch for Red Herring Options
Exam questions may include options that describe:

• Governance structures (not enterprise definition)
• Technical architectures (not enterprise definition)
• Single departments or teams (possibly too narrow)
• Loosely affiliated organizations without shared goals (not enterprises)

Focus on shared objectives when eliminating incorrect options.

Tip 8: Remember the Flexibility Principle
TOGAF emphasizes that enterprise definition is context-dependent. Questions might ask what the appropriate enterprise definition is for a specific scenario. The answer depends on:

• What organization commissioned the architecture work
• What problem or opportunity is being addressed
• What scope is feasible and meaningful

This flexibility is a key exam concept—there isn't always one "right" answer, but rather the most appropriate definition for the context.

Tip 9: Connect to Architecture Repository and Governance
Questions may ask how enterprise definition impacts architecture governance and the architecture repository. Remember that the enterprise scope determines:

• Which standards apply
• Who sits on the Architecture Board
• Which assets go into the repository
• What architectural decisions are relevant

Tip 10: Study Typical Enterprise Definitions
Be familiar with how different types of organizations define enterprises:

• Private Sector: Often organized by divisions, business units, or geographic locations
• Government: Often defined by agency, department, or mission-critical programs
• Nonprofit: Often defined by functional areas or geographic service regions
• Healthcare: Often defined by hospital systems or care networks

Knowing these patterns helps answer scenario-based questions quickly.

Common Exam Question Patterns

Pattern 1: Multiple Choice on Definition
"Which of the following best describes an enterprise in TOGAF?"
Look for the option emphasizing shared goals and objectives, and allowing for multiple organizations.

Pattern 2: Scenario-Based Questions
"Company X has headquarters, three regional offices, and a subsidiary. What is the appropriate enterprise definition?"
Analyze the shared objectives and strategic intent to determine boundaries.

Pattern 3: Consequence Questions
"If the enterprise definition is changed to exclude Division B, what impact would this have?"
Think through implications for scope, governance, and stakeholder engagement.

Pattern 4: Matching Questions
Match enterprise characteristics to definitions or match scenarios to appropriate enterprise scopes.

Summary

The Definition of an Enterprise in TOGAF 10 Foundation is a fundamental concept that establishes the boundaries and scope of architectural work. By understanding that an enterprise is any collection of organizations bound by shared goals and objectives, and by recognizing its flexibility in different contexts, you'll be well-prepared to answer exam questions on this topic. Focus on shared objectives, practice connecting enterprise definition to scope and governance, and familiarize yourself with diverse organizational contexts for the best exam performance.