TOGAF EA Practitioner study plan
TOGAF EA Practitioner · Give each week a clear focus.
8 weeks · About 7 hours per week
Preliminary Phase and Architecture Governance & Phase A: Architecture Vision
Map every Preliminary Phase output (Architecture Principles, tailored ADM, governance bodies, Architecture Repository) to the ADM phase that consumes it, and state the trigger for re-running the phase
Draft five Architecture Principles in the standard Name / Statement / Rationale / Implications format and test each against a sample architecture decision
Describe how the Architecture Board, the sponsoring body, and the Chief Architect approve dispensations, and how compliance reviews are scheduled and escalated
Produce an Architecture Vision for a familiar organization covering scope, stakeholder map, concerns, key business requirements, and constraints
Write a Statement of Architecture Work skeleton linking the vision to approvals and success criteria
Your checkpoint
A two-page pack: five drafted principles plus a one-page Architecture Vision with a stakeholder/concern matrix, self-assessed against a written checklist of Preliminary and Phase A outputs.
Phase B: Business Architecture
Decompose one real business capability map to three levels and assign an owner to each level-1 capability
Model the value streams and business processes for two capabilities, flagging where information-system and technology dependencies arise
Derive business architecture gaps by comparing baseline and target models, and log each gap with an identifier
Trace three stakeholder concerns from Phase A into the specific business architecture views that resolve them
Apply one business architecture technique (e.g., business capability, value stream, or organization map) and explain its selection criteria
Your checkpoint
A business architecture pack containing a three-level capability map, two process models, and a numbered gap list of at least eight entries, each traceable to a Week 1 concern.
Phase C: Information Systems Architectures
Separate data architecture artifacts from application architecture artifacts and justify where each belongs in the Architecture Repository
Build baseline and target data entity/relationship models for one business area and identify at least three data gaps
Produce an application communication diagram plus Application Portfolio Catalog entries for five applications, noting interfaces
Validate every data and application gap against the Architecture Requirements Specification so no gap lacks a Phase A requirement
Explain how the two sub-architectures are developed in parallel and reconciled at a single baseline/target decision point
Your checkpoint
An information systems architecture pack: baseline and target data models, an application communication diagram, five catalog entries, and a reconciliation table tying each gap to a requirement ID.
Phase D: Technology Architecture & Architecture Requirements Management and ADM Techniques
Model a technology architecture covering platform services, infrastructure, and network for one logical environment
Classify at least five technology gaps as baseline removal, target addition, or consolidation, and record the logic
Apply two Domain 10 techniques to a change request: gap analysis and requirements impact assessment
Sequence the Phase B to Phase D outputs into a single artifact hand-off diagram and narrate it without notes
Your checkpoint
A technology architecture diagram set with a five-item classified gap register, plus a handwritten artefact hand-off diagram photographed/transcribed into your notes for later self-testing.
Phase E: Opportunities and Solutions
Consolidate gaps from Domains 3, 4, and 5 into work packages and group related packages logically
Produce a solutions-and-dependencies matrix showing which work packages enable or depend on others
Compare two candidate Transition Architectures and select one, justifying the choice on cost, benefit, and risk
Identify two quick wins and state what makes each a candidate for early delivery
Your checkpoint
A Solutions and Dependencies Matrix covering at least ten work packages plus a one-page memo selecting a Transition Architecture and naming rejected alternatives with reasons.
Phase F: Migration Planning & Phase G: Implementation Governance
Build a phased migration plan with work packages, resources, dependencies, and a calendar timeline
Construct an Implementation Factor Assessment and Deduction matrix for two material factors
Estimate cost and benefit for two work packages and place both on the migration timeline
List the required contents of an Architecture Contract and the Architecture Board's role in Phase G
Your checkpoint
A one-page migration plan timeline with a cost/benefit sheet for two work packages and a checklist of Architecture Contract contents.
Phase G: Implementation Governance & Phase H: Architecture Change Management
Draft an Architecture Contract for one work package, listing deliverables, compliance checks, and sign-off criteria
Run a mock compliance review of a solution against one principle and record either a dispensation or a remediation action
Classify five change requests using the Phase H categories and identify the drivers behind each
Decide for three of those changes whether incremental ADM re-entry or a full ADM cycle is required, and justify each decision
State the criteria for a change that invalidates the Architecture Vision and forces re-approval
Your checkpoint
A compliance review record with a dispensation entry, plus a change-classification log of five requests each annotated with the re-entry decision and rationale.
Architecture Requirements Management and ADM Techniques & Preliminary Phase and Architecture Governance & Phase A: Architecture Vision & Phase B: Business Architecture & Phase C: Information Systems Architectures & Phase D: Technology Architecture & Phase E: Opportunities and Solutions & Phase F: Migration Planning & Phase G: Implementation Governance & Phase H: Architecture Change Management
Apply the Requirements Management process end to end: capture, baseline, and disposition five requirements as they change across phases
Explain for each ADM phase which requirements artefact it reads and which it updates
Complete two timed full-length practice sets and log every missed topic with its domain
Re-drill all logged weak topics until each is answered correctly twice in a row
Compress the whole ADM into a one-page crib sheet covering inputs, outputs, and key techniques per phase
Your checkpoint
A mock-exam score report at or above 80 percent on the second full-length set, plus a one-page ADM crib sheet and a requirements traceability log of five items.
Milestones
Week 2: Without notes, name the inputs, outputs, and purpose of the Preliminary Phase and Phase A, and explain how a stakeholder concern becomes a business architecture view; score at least 7 of 10 on a self-written recall test.
Week 4: Closed-book 30-question quiz covering Domains 1 through 5 plus basic Domain 10 techniques at 75 percent or better, and narrate the Phase B, C and D artefact hand-offs from memory.
Week 6: Produce a complete work-package-to-migration-timeline trace for a fresh scenario in under 45 minutes, with every work package traceable to a logged gap.
Week 8: Two full-length timed practice sets completed with the second at 80 percent or higher, and every missed question traced to a specific domain and closed with a written correction note.