Study guide
3.4 Business Scenarios & Value Stream Modeling
TOGAF Enterprise Architecture Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts
1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan
2 Chapter 2: ADM Foundation & Preliminary Phase
2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise
3 Chapter 3: ADM Architecture Vision & Business Architecture
3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling
4 Chapter 4: ADM Information Systems Architectures (Phase C)
4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability
5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)
5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies
6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)
6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews
7 Chapter 7: BDAT Architecture Domains Deep-Dive
7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms
8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts
8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints
9 Chapter 9: Architecture Governance, Capability & Maturity
9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments
10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques
10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns
3.4 Business Scenarios & Value Stream Modeling
Key Takeaways Explain This Topic AI
Creating a Business Scenario involves seven activities — rank the problem, model the environment, set SMART objectives, identify human actors, identify computer actors, document roles and measures of success, and test fitness-for-purpose.
A Business Scenario is developed over iterative phases of Gathering, Analyzing, and Reviewing, refining each pass until the scenario is fit for purpose.
Value Stream Modeling represents an end-to-end collection of value-adding activities that create an outcome for a customer or stakeholder.
A Value Stream consists of distinct Value Stages, each producing a specific value item or state change.
Cross-mapping Value Streams to Business Capabilities identifies exactly which capabilities enable specific stages of value delivery.
Last updated: August 2026
3.4 Business Scenarios & Value Stream Modeling
Executive Summary: Business Scenarios and Value Stream Modeling are central techniques in the TOGAF Standard 10th Edition. A Business Scenario is built from seven activities carried out over iterative phases of Gathering, Analyzing, and Reviewing, while Value Stream Modeling structures end-to-end value delivery and cross-maps required business capabilities.
1. The Business Scenario Technique
A Business Scenario is a proven TOGAF technique used to discover, document, and validate business requirements. It bridges the gap between executive strategy and technical architecture by framing requirements within realistic business problem contexts.
Purpose of Business Scenarios
Uncover implicit or un-articulated business requirements.
Ensure architecture solutions address real-world operational constraints and user needs.
Establish measurable SMART (Specific, Measurable, Actionable, Realistic, Time-bound) criteria for success.
2. Creating a Business Scenario: Seven Activities, Three Iterative Phases
TOGAF describes business scenario creation on two axes at once, and candidates routinely confuse them. The activities say what content you produce ; the phases say how you converge on it . Both come from the standard; neither is a linear checklist.
The Seven Activities of Creating a Business Scenario
Identify, document, and rank the problem that is driving the scenario. State the problem as what must be accomplished, never as how — a problem phrased as a technology choice is a red flag and should be pushed back.
Identify the business and technical environment of the scenario and document it in scenario models.
Identify and document the desired objectives — the results of handling the problem successfully. Objectives must be SMART : Specific, Measurable, Actionable, Realistic, and Time-bound.
Identify the human actors (the participants) and their place in the business model.
Identify the computer actors (the computing elements) and their place in the technology model.
Identify and document roles, responsibilities, and measures of success per actor , together with the required scripts per actor and the results of handling the situation.
Check for "fitness-for-purpose" in inspiring subsequent architecture work, and refine only if necessary.
- The Three Iterative Phases +-------------+ +-------------+ +-------------+
- | GATHERING | ----> | ANALYZING | ----> | REVIEWING |
- +-------------+ +-------------+ +-------------+
- ^ |
- +------------- refine if not yet ------------+
- fit-for-purpose
A business scenario is developed over a number of iterative phases of Gathering , Analyzing , and Reviewing the information it contains. In each pass every one of the seven areas above is successively improved. The refinement decision at the end of a pass is exactly the fitness-for-purpose test in activity 7: is the scenario now good enough to carry requirements downstream, or does it need another pass?
3. Value Stream Modeling in TOGAF 10th Edition
Value Stream Modeling has become a centerpiece of TOGAF Business Architecture in the 10th Edition.
What is a Value Stream?
A Value Stream is an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end user.
Unlike business processes (which focus on internal operational execution efficiency), value streams focus strictly on value creation from the stakeholder's perspective .
Core Components of a Value Stream
Triggering Event: External or internal event that initiates the value stream (e.g., "Customer requests loan").
Stakeholder / Value Receiver: Entity receiving the ultimate outcome (e.g., "Retail Customer").
Value Stages: Sequential segments within the value stream, each producing a specific value increment.
Value Proposition / Outcome: Net value delivered upon completing the final stage (e.g., "Loan funded & active").
4. Anatomy of a Value Stage
Each Value Stage represents a critical phase in value creation. A value stage must be defined with five key attributes:
- Attribute Description Example (Stage: Account Verification)
- Stage Name Concise verb-noun title in active voice. Verify Customer Identity
Description Brief explanation of what occurs in the stage. Validation of customer identity documents and KYC compliance.
Entry Criteria Conditions that must be met before stage begins. Customer application submitted with valid ID documents.
Exit Criteria Conditions required to successfully complete stage. Identity verified against national database without fraud flags.
Value Item Specific value increment produced by this stage. Verified Customer Risk Profile.
5. Cross-Mapping Capabilities to Value Streams
Value streams describe how value flows , but they cannot execute on their own. They depend on Business Capabilities for enablement.
The Value Stream / Capability Cross-Mapping Matrix
Architects map Business Capabilities to specific Value Stream Stages to identify enabling dependencies, maturity gaps, and technology investment targets. +-----------------------------------------------------------------------------------+
- | VALUE STREAM: Customer Onboarding |
- +----------------------+----------------------+----------------------+--------------+
- | Stage 1: Prospect | Stage 2: Identity | Stage 3: Risk | Stage 4: |
- | Engagement | Verification | Assessment | Activation |
- +----------------------+----------------------+----------------------+--------------+
- | ENABLING | ENABLING | ENABLING | ENABLING |
- | CAPABILITIES: | CAPABILITIES: | CAPABILITIES: | CAPABILITIES:|
- | - Digital Marketing | - Document Parsing | - Credit Scoring | - Account |
- | - Lead Management | - KYC Compliance | - Fraud Detection | Creation |
- +----------------------+----------------------+----------------------+--------------+
- Real-World Example: Customer Onboarding
Trigger: Customer submits online application for a bank account.
Stage 1 (Engage Prospect): Enabled by Digital Marketing and Lead Management capabilities. Value Item: Qualified Prospect.
Stage 2 (Verify Identity): Enabled by KYC Compliance and Biometric Verification capabilities. Value Item: Confirmed Identity.
Stage 3 (Assess Credit Risk): Enabled by Credit Scoring and Automated Risk Assessment capabilities. Value Item: Approved Credit Profile.
Stage 4 (Activate Account): Enabled by Core Banking Account Provisioning capability. Value Item: Active Bank Account (Final Outcome).
By cross-mapping capabilities, if "Biometric Verification" has a low maturity score (Red Heat Map), architects immediately recognize that Stage 2 of Customer Onboarding will bottleneck, directly impacting customer conversion and business value.
Section Summary & Exam Focus
Keep the two axes of the Business Scenario technique apart. The seven activities produce the content: rank the problem; identify the business and technical environment; set SMART objectives; identify human actors; identify computer actors; document roles, responsibilities, and measures of success per actor; and check fitness-for-purpose. The three iterative phases — Gathering, Analyzing, Reviewing — are how you converge on it. TOGAF has no six-step "Gather/Analyze/Document/Review/Finalize/Execute" sequence; that wording is a distractor.
Understand that Value Streams represent end-to-end value creation for a stakeholder, while Business Processes represent internal detailed operational activities.
Remember how Business Capabilities are cross-mapped to Value Stream Stages to pinpoint capabilities requiring investment.