Business Scenarios

Business Scenarios in TOGAF 10 Foundation

What Are Business Scenarios?

Business Scenarios are a technique used in the TOGAF ADM (Architecture Development Method) to understand and communicate the business context, requirements, and expected outcomes of an enterprise architecture initiative. They are narrative descriptions that capture how an organization operates, the challenges it faces, and how the proposed architecture will address business problems and opportunities.

Why Are Business Scenarios Important?

Business Scenarios are critical for several reasons:

• Stakeholder Engagement: They provide a clear, understandable narrative that helps non-technical stakeholders grasp the value and impact of the architecture.
• Requirements Clarification: They help translate business needs into concrete architectural requirements.
• Risk Identification: By modeling current and future states, scenarios help identify potential risks and dependencies.
• Communication Tool: They bridge the gap between business and IT perspectives, ensuring everyone understands the direction.
• Validation of Architecture: Scenarios provide a way to test whether the proposed architecture actually addresses the identified business problems.
• Change Management: They help communicate why changes are necessary and how they will benefit the organization.

How Business Scenarios Work

Business Scenarios follow a structured approach within the ADM:

Components of a Business Scenario

• Business Problem or Opportunity: The current state or challenge that needs to be addressed.
• Key Actors/Stakeholders: The individuals or groups involved in the scenario.
• Business Environment: The context in which the scenario occurs (market conditions, regulatory requirements, technological landscape).
• Current State (As-Is): How the business process or system currently operates.
• Desired Future State (To-Be): How the business process or system should operate after the architecture is implemented.
• Expected Benefits: The measurable outcomes and value that will be realized.
• Constraints and Assumptions: Limitations and factors that may influence the scenario.
• Implementation Roadmap: The steps needed to move from current to future state.

The Business Scenario Process

1. Phase A - Architecture Vision: Business Scenarios are initiated here to capture the business context and vision.
2. Phase B-D: Scenarios are refined through business, information systems, and technology architecture phases.
3. Phase E - Opportunities and Solutions: Scenarios help prioritize and plan implementation.
4. Phase F-H: Scenarios guide implementation and change management.

Key Characteristics of Effective Business Scenarios

• Realistic: Based on actual business situations and challenges.
• Understandable: Written in language that all stakeholders can comprehend.
• Measurable: Includes specific metrics to assess success.
• Actionable: Leads directly to architectural decisions and requirements.
• Comprehensive: Considers multiple perspectives and viewpoints.

Business Scenarios in the ADM Phases

Phase A (Architecture Vision): Business Scenarios are essential for defining the architecture vision. They help stakeholders understand the scope and objectives of the architecture initiative.

Phase B (Business Architecture): Scenarios help map business processes and identify process improvements. The business scenario shows how business capabilities will be enhanced.

Phase C (Information Systems Architecture): Scenarios help determine what information and systems are needed to support the business processes described.

Phase D (Technology Architecture): Scenarios help identify the technology platform and infrastructure needed to support the information systems.

Phase E-H (Implementation): Scenarios serve as a reference point for validating that the implementation addresses the original business problem.

Example of a Business Scenario

Scenario Title: Customer Order Processing Improvement

Business Problem: The current order processing system requires manual data entry at multiple points, leading to errors and delays. Customers complain about long processing times.

Actors: Customer Service Representatives, Finance Team, Warehouse Staff, Customers

Current State: Orders are received via phone or email, manually entered into a legacy system, and processed through multiple departments with paper-based approvals.

Future State: Orders are submitted through a web portal, automatically validated and routed, with real-time visibility across all departments.

Expected Benefits: 50% reduction in order processing time, 90% reduction in manual errors, improved customer satisfaction scores.

Implementation Approach: Deploy an integrated order management system with automated workflows and API connections to legacy systems.

Exam Tips: Answering Questions on Business Scenarios

Understanding Question Types

Type 1 - Definition Questions: These ask you to define what a business scenario is or identify its key components.

• Strategy: Remember that business scenarios are narrative descriptions that bridge business and IT perspectives. Emphasize their role in capturing business context and requirements.

Type 2 - Purpose/Importance Questions: These ask why business scenarios are used in the ADM.

• Strategy: Focus on key benefits: stakeholder communication, requirements elicitation, risk identification, and validation of architecture decisions. Provide concrete examples.

Type 3 - Application Questions: These ask how business scenarios are used in specific ADM phases.

• Strategy: Know which phases use business scenarios most heavily (Phase A, B, and E-H). Be able to explain how scenarios evolve through the phases.

Type 4 - Component Questions: These ask you to identify elements that should be included in a business scenario.

• Strategy: Remember the key components: problem/opportunity, actors, current state, future state, benefits, constraints, and implementation approach. Recognize that complete scenarios address both As-Is and To-Be states.

Key Exam Tips

• Link to ADM: Always connect business scenarios to the ADM phases. Show that you understand where they are used and how they evolve.
• Business vs. Technical: Emphasize that business scenarios bridge the business and technical domains. This is their critical value.
• Clarity and Communication: Remember that a primary purpose of business scenarios is to communicate with non-technical stakeholders. If a question asks about effectiveness, discuss clarity and understandability.
• Measurable Outcomes: Scenarios should include specific, measurable benefits and success criteria. Use numbers and metrics in your answers.
• Realism: Scenarios must be grounded in real business situations. Avoid overly theoretical or unrealistic examples.
• Complete Picture: Don't focus only on the future state. Emphasize that scenarios capture both current and desired future states.
• Stakeholder Perspective: Remember that scenarios involve multiple actors and stakeholders. A good answer will reference different perspectives.
• Avoid Common Pitfalls: Don't confuse business scenarios with use cases (though they're related). Don't treat scenarios as purely technical solutions. Scenarios are primarily business-focused.

Sample Exam Questions and Approaches

Q: What is the primary purpose of developing business scenarios in Phase A of the ADM?

Approach: Focus on establishing the architecture vision and communicating the business context. Mention how scenarios help stakeholders understand the scope and objectives.

Q: Which of the following should be included in a business scenario? A) Only technical solutions, B) Problem statement and desired future state, C) Detailed technical specifications, D) Software vendor recommendations

Approach: The answer is B. Scenarios capture both current problems and future states, not just technical solutions.

Q: How do business scenarios support the transition from Phase B to Phase C in the ADM?

Approach: Explain how business architecture scenarios define what needs to be done (Phase B), and then information systems architecture scenarios determine how information systems will support those business processes (Phase C).

Q: Identify a key benefit of using business scenarios for stakeholder engagement.

Approach: Discuss how scenarios make architectural concepts understandable to non-technical stakeholders. Use concrete language rather than technical jargon. Explain how this improves buy-in and alignment.

Quick Reference Checklist

When answering business scenario questions, verify that your response includes:

• ☐ Clear definition or identification of the concept
• ☐ Link to the appropriate ADM phase(s)
• ☐ Both current state and future state perspectives
• ☐ Business perspective (not purely technical)
• ☐ Stakeholder and actor involvement
• ☐ Measurable benefits or outcomes
• ☐ Recognition that scenarios are communication tools
• ☐ Realistic, practical examples

Conclusion

Business Scenarios are a foundational technique in TOGAF that help bridge the gap between business needs and technical solutions. By mastering the concept of business scenarios, understanding their components, and knowing how they flow through the ADM phases, you'll be well-prepared to answer exam questions effectively. Remember to always maintain a business perspective, emphasize communication and stakeholder engagement, and connect scenarios to the broader ADM framework.