Statement of Architecture Work: Complete Guide for TOGAF 10 Foundation Exam

Statement of Architecture Work: Complete Guide for TOGAF 10 Foundation Exam

Introduction

The Statement of Architecture Work is a foundational document in the TOGAF ADM (Architecture Development Method) that establishes the scope, goals, and constraints for an architecture engagement. Understanding this concept is crucial for passing the TOGAF 10 Foundation exam and successfully implementing enterprise architecture in real-world scenarios.

Why the Statement of Architecture Work is Important

The Statement of Architecture Work serves several critical purposes in enterprise architecture:

• Sets Clear Boundaries: It defines what is and what is not included in the architecture engagement, preventing scope creep and misaligned expectations.
• Establishes Governance: It outlines the decision-making authority, roles, and responsibilities for the architecture project.
• Defines Success Criteria: It establishes metrics and outcomes that will determine whether the architecture engagement has succeeded.
• Manages Stakeholder Expectations: It communicates to all stakeholders what they can expect from the architecture work and what resources will be required.
• Secures Sponsorship and Funding: It provides the business case and justification needed to obtain executive support and financial resources.
• Guides the ADM Process: It acts as a reference document throughout the architecture development method, ensuring the work remains focused and aligned with original objectives.

What is the Statement of Architecture Work?

The Statement of Architecture Work is a formal document that is created at the beginning of an architecture engagement, typically during the Preliminary and Vision phases of the TOGAF ADM. It is essentially a contract between the architecture team and the organization that commissions the architecture work.

Key Components of the Statement of Architecture Work include:

• Architecture Project Scope: A description of what the architecture initiative will cover, including which business domains, IT services, and technologies are in scope.
• Architecture Project Objectives: The goals and desired outcomes of the architecture engagement, such as improving efficiency, reducing costs, or enabling new capabilities.
• Architecture Project Success Criteria: Specific, measurable criteria that define what success looks like (e.g., reduced time-to-market, improved system availability).
• Architecture Project Constraints: Limitations and constraints such as budget, timeline, organizational policies, and regulatory requirements.
• Governance and Approval: The decision-making framework, approval authorities, and escalation paths for the architecture work.
• Architecture Project Team and Stakeholders: Identification of key team members, sponsors, and stakeholders involved in or affected by the architecture work.
• Requested Architecture Domains: Specification of which architecture domains (Business, Data, Application, Technology) should be included in the engagement.
• Baseline Architecture Assumptions: Any existing systems, processes, or constraints that should be considered as the baseline.
• Implications for the Organization: Potential organizational impacts, change management considerations, and risks associated with the architecture engagement.

How the Statement of Architecture Work Functions

The Statement of Architecture Work operates as a living document throughout the architecture engagement:

1. Creation and Approval (Preliminary Phase)

The Statement of Architecture Work is typically developed during the Preliminary Phase and refined in the Vision Phase. It is created collaboratively by the architecture team and key stakeholders, then formally approved by the architecture sponsor and governance bodies. This approval process ensures buy-in and alignment from leadership.

2. Scope Definition

Once approved, the document serves as the authoritative definition of the architecture engagement's scope. Any requests to expand or change the scope must be formally reviewed and approved, preventing unauthorized scope creep.

3. Guiding the ADM Phases

As the architecture team progresses through subsequent ADM phases (Architecture Development Phases A through D), the Statement of Architecture Work remains the reference point. All architecture work must align with the stated objectives and scope.

4. Managing Expectations

The document communicates clearly to all stakeholders what to expect from the architecture work, including timelines, deliverables, required resources, and expected outcomes.

5. Change Control

If circumstances change during the engagement, the Statement of Architecture Work can be formally revised through an approved change control process. This prevents unplanned changes and maintains project discipline.

6. Baseline for Governance

The governance structures and decision authorities defined in the Statement of Architecture Work remain in effect throughout the engagement, ensuring consistent decision-making.

Key Relationships in the TOGAF ADM

The Statement of Architecture Work is closely related to several other key TOGAF concepts:

• Request for Architecture Work (RfAW): The RfAW is typically the input that triggers the creation of the Statement of Architecture Work. It comes from the business and asks for architecture work to be performed.
• Architecture Vision: Developed in the Vision Phase, the Architecture Vision articulates the target state that the architecture will support, while the Statement of Architecture Work defines the scope and governance for achieving that vision.
• Stakeholder Management: The Statement of Architecture Work identifies all stakeholders and establishes how they will be engaged throughout the architecture engagement.
• Architecture Governance: The Statement of Architecture Work defines the governance framework that will oversee the architecture work.

How to Answer Exam Questions on Statement of Architecture Work

When you encounter exam questions about the Statement of Architecture Work, follow these strategies:

Question Type 1: Definition and Purpose

How to Approach: These questions ask what the Statement of Architecture Work is or why it is important.

Key Points to Remember:

• It is a formal contract between the architecture team and the organization commissioning the work.
• It is created in the Preliminary and Vision phases.
• It defines scope, objectives, success criteria, constraints, and governance.
• It serves as a reference point throughout the ADM.

Example Question: What is the primary purpose of the Statement of Architecture Work?
Answer Strategy: Look for options mentioning scope definition, governance establishment, and success criteria. The Statement of Architecture Work is fundamentally about establishing the boundaries and success measures for the architecture engagement.

Question Type 2: What Should Be Included

How to Approach: These questions ask what components or information should be included in a Statement of Architecture Work.

Key Points to Remember:

• Scope (what is and is not included)
• Objectives (goals of the engagement)
• Success criteria (how we measure success)
• Constraints (budget, time, policies)
• Governance and approvals
• Stakeholders and team members
• Architecture domains to be addressed
• Assumptions about the baseline
• Organizational implications

Example Question: Which of the following should be explicitly included in a Statement of Architecture Work?
Answer Strategy: Look for options that include the items listed above. Eliminate options about detailed technical specifications or solution designs, as those come later in the ADM. The Statement of Architecture Work is high-level and strategic.

Question Type 3: When to Create/Update

How to Approach: These questions ask when the Statement of Architecture Work should be created, reviewed, or updated.

Key Points to Remember:

• Created during the Preliminary Phase and refined in the Vision Phase.
• Updated through formal change control if scope or objectives change.
• Referenced throughout all ADM phases.
• Not typically updated during Implementation phases, but may inform phase reviews.

Example Question: At what stage of the TOGAF ADM is the Statement of Architecture Work typically created?
Answer Strategy: The correct answer is the Preliminary Phase (or sometimes listed as Preliminary and Vision phases). It is created early, before detailed architecture development begins.

Question Type 4: Relationships to Other Artifacts

How to Approach: These questions ask how the Statement of Architecture Work relates to or differs from other TOGAF concepts.

Key Points to Remember:

• RfAW (Request for Architecture Work) triggers the creation of the Statement of Architecture Work.
• The Architecture Vision is developed within the scope defined by the Statement of Architecture Work.
• The Statement of Architecture Work defines governance that oversees the Architecture Vision and subsequent work.
• The Statement of Architecture Work is broader than any single architecture domain (Business, Data, Application, Technology).

Example Question: What is the relationship between a Request for Architecture Work and a Statement of Architecture Work?
Answer Strategy: The RfAW comes from business requesting architecture work. The Statement of Architecture Work is the formal response that defines how that request will be addressed, including scope, objectives, and governance.

Exam Tips: Answering Questions on Statement of Architecture Work

Tip 1: Remember the Strategic Nature

The Statement of Architecture Work is a strategic, high-level document, not a technical specification. Exam answers should focus on scope, governance, objectives, and constraints—not on specific technology choices or detailed design decisions.

Tip 2: Link It to Sponsorship and Authority

Questions about the Statement of Architecture Work often relate to governance and decision-making authority. Remember that it establishes who approves decisions and how conflicts are escalated. This is its governance function.

Tip 3: Recognize It as a Contractual Document

Think of the Statement of Architecture Work as a contract between the architecture team and the sponsoring organization. This mental model helps you understand why it is so important to establish it early and why changes to it must be formally approved.

Tip 4: Distinguish Scope Boundaries

Exam questions often test whether you understand what should and should not be in scope. The Statement of Architecture Work explicitly defines these boundaries. A common exam question format is: "Which of the following should be addressed in the Statement of Architecture Work scope?"

Tip 5: Connect to Success Criteria

Remember that the Statement of Architecture Work includes success criteria. Questions about how you measure whether an architecture engagement was successful often point to information defined in the Statement of Architecture Work.

Tip 6: Identify Stakeholder Management

The Statement of Architecture Work identifies stakeholders and establishes how they will be engaged. Exam questions about stakeholder communication and management often reference the Statement of Architecture Work as the document that establishes this.

Tip 7: Understand the Approval Process

Key exam point: The Statement of Architecture Work must be formally approved by the sponsor and governance bodies before detailed architecture work begins. If an exam question asks about how to ensure buy-in or secure executive commitment, the Statement of Architecture Work approval is often the answer.

Tip 8: Recognize It as a Control Document

The Statement of Architecture Work serves a control function throughout the engagement. It prevents scope creep, manages changes, and ensures work remains aligned with original objectives. Questions about controlling an architecture engagement often reference the Statement of Architecture Work.

Tip 9: Know the Input and Output Relationships

For exam purposes, remember:
Input: Request for Architecture Work (RfAW)
Output: Statement of Architecture Work
Use: Guides all subsequent ADM phases
Updates: Through formal change control

Tip 10: Practice Recognition in Context

Exam questions often present scenarios describing architecture engagement situations. Practice identifying when the Statement of Architecture Work is the relevant TOGAF concept. For example: "An organization wants to establish clear governance and success measures for its architecture initiative. What should be documented?" The answer is the Statement of Architecture Work.

Common Exam Question Patterns

Pattern 1: Definition Questions
These ask directly what the Statement of Architecture Work is. The answer emphasizes it as a formal document establishing scope, objectives, success criteria, and governance for an architecture engagement.

Pattern 2: Content Questions
These ask what should be included. Study the nine key components listed in the "What" section above.

Pattern 3: Process Questions
These ask when it is created or how it is used. Remember: created in Preliminary/Vision phases, used throughout the ADM, updated via change control.

Pattern 4: Relationship Questions
These test your understanding of how the Statement of Architecture Work relates to RfAW, Architecture Vision, and governance frameworks.

Pattern 5: Scenario Questions
These present a business situation and ask what tool or document is needed. Practice identifying when the Statement of Architecture Work is the answer.

Conclusion

The Statement of Architecture Work is a critical foundational document in the TOGAF ADM. It serves as the formal agreement between the architecture team and the sponsoring organization about what will be done, how success will be measured, and how decisions will be made. For the TOGAF 10 Foundation exam, understanding this concept is essential. Focus on remembering its key components, its strategic nature, its role in governance, and its relationships to other TOGAF artifacts. With this comprehensive understanding and the exam tips provided, you will be well-prepared to answer any exam question about the Statement of Architecture Work.