OGEA-102 Online Practice Questions

Explanation:
The Business Value Assessment Technique is a technique that can be used to estimate and compare the business value of the projects and project increments that implement the architecture work packages, which are the sets of actions or tasks that are required to implement a specific part of the architecture. The business value is the measure of the benefits or advantages that the project or project increment delivers to the business, such as increased revenue, reduced costs, improved quality, or enhanced customer satisfaction1
The steps for applying the Business Value Assessment Technique are:
Identify the criteria and factors that are relevant to the business value assessment, such as costs, benefits, risks, and opportunities. The criteria and factors should be aligned with the business goals and drivers that motivate the architecture work, and the stakeholder requirements and concerns that influence the architecture work.
Assign weights and scores to the criteria and factors, using various methods, such as expert judgment, historical data, or analytical models. The weights and scores should reflect the importance and performance of the criteria and factors, and the trade-offs and preferences of the stakeholders. Calculate the business value for each project or project increment, using various techniques, such as net present value, return on investment, or balanced scorecard. The business value should indicate the expected or actual outcomes and impacts of the project or project increment on the business. Prioritize the implementation projects and project increments, based on the business value and other considerations, such as dependencies, resources, or risks. The prioritization should determine the order or sequence of the projects and project increments, and the allocation and utilization of the resources.
Therefore, the best answer is C, because it describes the next steps for the migration planning, which are the activities that support the transition from the Baseline Architecture to the Target Architecture. The answer covers the Business Value Assessment Technique, which is relevant to the scenario.
Reference: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 28:
Business Value Assessment Technique: The TOGAF Standard, Version 9.2, Part II: Architecture
Development Method (ADM), Chapter 18: Phase A: Architecture Vision: The TOGAF Standard,
Version 9.2, Part II: Architecture Development Method (ADM), Chapter 21: Phase F: Migration
Planning: The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 36:
Building Blocks

Explanation:
A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project. A Request for Architecture Work is usually initiated by the sponsor or client of the architecture work, and approved by the Architecture Board, which is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. A Request for Architecture Work triggers a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture12
An Architecture Vision is a high-level description of the desired outcomes and benefits of the proposed architecture. An Architecture Vision is the output of Phase A: Architecture Vision of the ADM cycle, which is the first phase of the architecture development. An Architecture Vision defines the scope and approach of the architecture work, and establishes the business goals and drivers that motivate the architecture work. An Architecture Vision also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process3
A trade-off analysis is a technique that can be used to evaluate and compare different architecture alternatives and select the most suitable one. A trade-off analysis involves identifying the criteria and factors that are relevant to the decision, such as costs, benefits, risks, and opportunities, and assessing the strengths and weaknesses of each alternative. A trade-off analysis also involves balancing and reconciling the multiple, often conflicting, requirements and concerns of the stakeholders, and ensuring alignment with the Architecture Vision and the Architecture Principles. Therefore, the best answer is D, because it proposes the best approach for architecture development to realize the CEO’s change in direction for the company. The answer covers the Request for Architecture Work, the Architecture Vision, and the trade-off analysis techniques that are relevant to the scenario.
Reference: 1: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work 2: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance 3: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Trade-Off Analysis

Explanation:
In TOGAF, creating a Business Scenario is a foundational step in defining and understanding the business problem, especially for complex transformations involving multiple stakeholders and systems, such as in this scenario. This method aligns with Phase A (Architecture Vision) of the TOGAF Architecture Development Method (ADM).
Here’s why this approach is the most effective:
Understanding Business Requirements:
A Business Scenario provides a structured way to capture and analyze the business requirements, stakeholder concerns, and the contextual elements related to the problem. In this scenario, the company faces challenges in integrating newly acquired companies with existing operations, which includes complex stakeholder concerns across different functional areas. Developing a Business Scenario allows the EA team to break down these complexities into identifiable and manageable parts.
Risk Evaluation and Management:
By using the Business Scenario approach, the EA team can not only define the requirements but also assess associated risks systematically. TOGAF emphasizes the importance of risk management through identifying potential risks, evaluating their impact, and defining strategies for handling these risks. The process includes assessing how risks can be avoided, transferred, or reduced―a necessary step in large-scale transformations to ensure that risks are proactively managed. Residual Risks and Governance:
Any risks that cannot be fully resolved should be identified as residual risks and escalated to the Architecture Board, which is aligned with TOGAF’s governance approach. The Architecture Board’s role in TOGAF is to provide oversight and make critical decisions on risks that exceed the control of the EA team. This ensures that unresolved risks are managed at the appropriate level of the organization.
Alignment with TOGAF ADM Phases:
The Business Scenario approach directly aligns with the Preliminary and Architecture Vision phases of the TOGAF ADM, which focuses on establishing a baseline understanding of the business context and the strategic transformation required. The detailed understanding of requirements, stakeholder concerns, and risks identified here will guide the subsequent phases of the ADM, including Business Architecture and Information Systems Architecture. TOGAF Reference (Section 2.6, ADM Techniques):
TOGAF provides guidelines on the creation of Business Scenarios as part of ADM Techniques, highlighting the importance of defining a business problem comprehensively to ensure successful transformation. This method includes identification of stakeholders, business requirements, and associated risks, which aligns well with the company's need for strategic and systematic integration of new business units.
By utilizing a Business Scenario, the EA team ensures that all aspects of the transformation are well understood, risks are identified early, and residual risks are managed effectively, aligning with the company's strategic objectives and the TOGAF framework’s guidance on risk management and stakeholder alignment.

Explanation:
According to the TOGAF standard, the Target Architecture is the description of a future state of the architecture being developed for an organization. It should be aligned with the Architecture Vision, Principles, and Requirements that have been agreed with the stakeholders. To address the incompatibilities between key stakeholder preferences, the TOGAF standard recommends creating and evaluating multiple alternative Target Architectures that meet different sets of criteria. These criteria should reflect the value preferences and priorities of the stakeholders, as well as the business drivers and objectives. The alternative Target Architectures should be illustrated using a set of architecture views that show the impact of each alternative on the business, data, application, and technology domains. The impact on planned projects should also be identified and analyzed. The strengths and weaknesses of each alternative should be understood and documented. A formal stakeholder review should then be conducted to decide which alternative is the most fit for purpose and should be moved forward with. The funding required for implementing the chosen alternative should also be determined and secured.
Reference: The TOGAF Standard, Version 9.2 - Phase B: Business Architecture - The Open Group The TOGAF Standard, Version 9.2 - Phase C: Information Systems Architectures - The Open Group
[The TOGAF Standard, Version 9.2 - Phase D: Technology Architecture - The Open Group]
[The TOGAF Standard, Version 9.2 - Phase E: Opportunities and Solutions - The Open Group]
[The TOGAF Standard, Version 9.2 - Phase F: Migration Planning - The Open Group]

Explanation:
The best answer is C. You would hold a series of interviews at each of the manufacturing plants using the business scenarios technique. This will allow you to understand the systems and integrations with local partners. You would use stakeholder analysis to identify key players in the engagement, and to understand their concerns. You will then identify and document the key high-level stakeholder requirements for the architecture. You will then generate high level definitions of the baseline and target architectures.
This answer is based on the TOGAF standard, which recommends the following steps to initiate the architecture project1:
Establish the architecture project
Identify stakeholders, concerns, and business requirements
Confirm and elaborate business goals, business drivers, and constraints Evaluate business capabilities
Assess readiness for business transformation
Define scope
Confirm and elaborate Architecture Principles, including business principles Develop Architecture Vision
Define the Target Architecture value propositions and KPIs Identify the business transformation risks and mitigation activities Secure stakeholder and sponsor approval
The answer C covers most of these steps, by using the business scenarios technique to elicit and validate the business requirements, goals, drivers, and constraints, as well as the current and future states of the architecture2. The answer C also uses stakeholder analysis to identify and engage the key stakeholders, and to address their concerns and expectations3. The answer C also generates high level definitions of the baseline and target architectures, which can be used to develop the Architecture Vision and the value propositions4.
The other answers are not the best approach for architecture development, because:
Answer A focuses on researching vendor literature and conducting briefings with vendors, which is not the best way to understand the business needs and the current situation of the enterprise. Answer A also defines a preliminary Architecture Vision without involving the stakeholders or validating the requirements, which may lead to misalignment and lack of consensus.
Answer B conducts a pilot project that will enable vendors to demonstrate potential solutions, which is premature and costly at this stage of the architecture project. Answer B also does not address the stakeholder concerns or the current systems and integrations, which may result in gaps and risks.
Answer B also develops the requirements after the pilot project, which may not reflect the actual business needs and goals.
Answer D develops baseline and target architectures for each of the manufacturing plants, which may not consider the enterprise-wide perspective and the potential benefits of a common ERP system. Answer D also does not involve the stakeholders or address their concerns, which may result in resistance and conflict. Answer D also does not define the business case or the performance metrics, which are essential for demonstrating the value and feasibility of the architecture.
Reference: 1: The TOGAF Standard, Version 9.2 - Architecture Vision 2: The TOGAF Standard, Version 9.2 - Business Scenarios 3: [The TOGAF Standard, Version 9.2 - Stakeholder Management] 4: [The TOGAF Standard, Version 9.2 - Architecture Definition Document]