Study guide
8.5 Business Transformation Readiness Assessment and Risk Management
TOGAF Enterprise Architecture Practitioner OGEA-103
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Mechanics & Foundation Overview
1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise
2 Chapter 2: Preliminary Phase & Establishing the EA Capability
2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools
3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)
3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
4 Chapter 4: Business Architecture (Phase B)
4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates
5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)
5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements
6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)
6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions
7 Chapter 7: Technology Architecture (Phase D)
7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models
8 Chapter 8: Opportunities and Solutions (Phase E)
8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management
9 Chapter 9: Migration Planning (Phase F)
9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps
10 Chapter 10: Implementation Governance (Phase G)
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists
11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management
11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict
12 Chapter 12: Architecture Governance, Boards, and Dispensations
12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts
13 Chapter 13: Architecture Content Framework & Architecture Repository
13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
14 Chapter 14: EA Capability, Tailoring, and Iteration
14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security
8.5 Business Transformation Readiness Assessment and Risk Management
Key Takeaways Explain This Topic AI
Business Transformation Readiness Assessment determines readiness factors, presents them with maturity models, rates them, assesses their risks, and works the actions into the Phase E and F Implementation and Migration Plan.
TOGAF's example readiness factors include Vision; Desire, Willingness, and Resolve; Need; Business Case; Funding; Sponsorship and Leadership; Governance; and IT and Enterprise Capacity to Execute.
Each readiness factor is rated for Urgency, Readiness Status (Low, Fair, Acceptable, Good, High), and Degree of Difficulty to Fix (No Action Needed, Easy, Moderate, Difficult).
TOGAF's Risk Management technique assesses risks by effect (Catastrophic, Critical, Marginal, Negligible) and frequency, at an initial level before mitigation and a residual level after it.
Residual risks must be accepted through the governance framework and are monitored in Phase G; moving a frequent/catastrophic risk to frequent/critical still leaves an extremely high risk.
Last updated: October 2026
8.5 Business Transformation Readiness Assessment and Risk Management
Two ADM Techniques decide whether a technically sound architecture can actually be implemented: Business Transformation Readiness Assessment and Risk Management . Both start in Phase A, are confirmed in Phase E, shape the Implementation and Migration Plan in Phases E and F, and are monitored in Phase G. The Level 2 learning outcomes ask you to apply the risk and security considerations of Phases E, F, and G and to create an environment in which the uncertainty of change can be managed. Part 2 scenarios therefore often hinge on recognizing a readiness gap or an unmitigated risk.
Business Transformation Readiness Assessment
TOGAF observes that an innovative Architecture Vision and Architecture Definition usually mean considerable change, and that the human element is by far the most important dimension of change . A change-averse culture or a narrowly skilled workforce can stop even the soundest architecture. The technique builds on the Canadian Government's Business Transformation Enablement Program (BTEP) .
The Recommended Activities
Determine the readiness factors that will affect the organization, ideally in a facilitated workshop with people from across the organization.
Present the readiness factors using maturity models.
Assess the readiness factors , including readiness factor ratings.
Assess the risks for each readiness factor and identify improvement actions to mitigate them.
Work these actions into the Phase E and F Implementation and Migration Plan.
The BTEP Readiness Factors
TOGAF's example set of factors is:
Factor What it asks
Vision Can management clearly define and communicate what is to be achieved?
Desire, Willingness, and Resolve Is there a desire for the results, willingness to accept the impact, and resolve to follow through?
Need Is there a compelling need to execute the endeavor?
Business Case Is there a business case with concrete benefits the organization is committed to deliver?
Funding Is there a clear source of funds to meet the expected expenditure?
Sponsorship and Leadership Is sponsorship broadly shared but not so broad that accountability is diffused?
Governance Can the organization engage everyone with an interest so that corporate interests are served?
Accountability Is responsibility assigned and aligned with where benefits and consequences will be felt?
Workable Approach and Execution Model Is the approach sensible, proven, and supported, with clear roles and a communication plan?
IT Capacity to Execute Does IT have the skills, tools, processes, and management capability, ideally proven on a similar endeavor?
Enterprise Capacity to Execute Can the business outside IT perform its tasks and make timely decisions?
Enterprise Ability to Implement and Operate Can the enterprise absorb the changes and operate in the new environment?
Rating the Factors
Each factor is assessed for its vision (where it must evolve to, with an intermediate target if useful), its rating , and its risks and actions . The BTEP rating scheme rates each factor on:
Urgency : an urgent factor needs action before the transformation can begin.
Readiness Status : Low (substantial work needed before proceeding), Fair (some work needed), Acceptable (some issues, no showstoppers), Good (relatively minor issues), or High (no readiness issues).
Degree of Difficulty to Fix : No Action Needed , Easy , Moderate , or Difficult .
Readiness and Migration Planning
The assessment is a key input to migration planning, which starts in Phase E and is completed in Phase F. Note whether business transformation actions sit on the critical path: there is no point deploying new IT capability without trained employees and ready support staff. The readiness factors are monitored in Phase G, and the assessment is a living document .
TOGAF also advises that the Architecture Definition should not be widely circulated until business transformation issues are identified and mitigated . For example, a consolidation that could cost jobs should not be announced before a supporting human resources plan exists. The readiness workshops then become part of the Communications Plan.
Risk Management
TOGAF states that there will always be risk in any architecture or business transformation effort. Risks should be identified, classified, and mitigated before starting, then tracked throughout. The Enterprise Architect may identify risks and mitigate some of them, but risks have to be accepted and managed within the governance framework .
Two Levels of Risk
Initial level of risk : the risk categorization before mitigating actions are determined and implemented.
Residual level of risk : the risk categorization after mitigating actions are implemented, if any.
The Risk Management Activities
Risk classification : commonly by time (schedule), cost (budget), and scope. Risks can also be client transformation relationship, contractual, technological, scope and complexity, environmental (corporate), personnel, or client acceptance risks, and they can be classified by architecture domain. EA risks are ultimately corporate risks.
Risk identification : maturity and readiness assessments generate many risks, documented in a Risk Management Plan.
Initial risk assessment : classify each risk by effect and frequency using scales the organization already uses.
Risk mitigation and residual risk assessment : plan actions that reduce risk to an acceptable level, from simple monitoring or acceptance to full contingency plans.
Risk monitoring : in Phase G, the risk worksheets are maintained as governance artifacts.
Effect, Frequency, and Impact
TOGAF's example scales are:
- Effect Meaning
- Catastrophic Critical financial loss that could bankrupt the organization
- Critical Serious loss in more than one line of business; no return on the IT investment
- Marginal Minor loss in a line of business; reduced return on the IT investment
- Negligible Minimal impact on a line of business's ability to deliver
Frequency runs from Frequent and Likely through Occasional and Seldom to Unlikely . Combining effect and frequency gives a corporate impact of Extremely High (E) , High (H) , Moderate (M) , or Low (L) .
Judging Mitigation
After mitigation, re-assess effect and frequency to check whether the effort made an acceptable difference. TOGAF warns that mitigation must reduce the corporate impact, not just move the risk to another similarly high category: changing a risk from frequent/catastrophic to frequent/critical still leaves an extremely high risk . Large outlays for little residual benefit should also be challenged.
Residual risks must be approved through the IT governance framework , and potentially corporate governance where business acceptance is needed. Phase G implementation governance may uncover critical risks that are not being mitigated, which can require another full or partial ADM cycle.
How the Techniques Appear in the ADM
Phase Readiness and risk activity
A Step 5 assesses readiness for business transformation; step 10 identifies business transformation risks with initial and residual levels, and mitigation activities go into the Statement of Architecture Work
E Step 7 confirms readiness and risk, reviewing the Phase A assessment; risks are recorded in the Consolidated Gaps, Solutions, and Dependencies matrix
- F Readiness actions and risk validation shape prioritization and the Implementation and Migration Plan
- G Readiness factors and residual risks are monitored; risk worksheets are maintained as governance artifacts
- H The "Manage risks" step continues risk management after deployment
Many Part 2 scenarios describe a sponsor who wants to announce or deploy a change quickly while readiness is rated low. The best answers address the readiness gap in the plan, or the residual risk in governance, rather than ignoring it or cancelling the work.