Enterprise Architecture: Modules
The program takes an architect from a single project to the organisation level: capability and value stream maps, application portfolio management, target and transition architectures, and governance without bureaucracy. TOGAF concepts are named as a reference; the program does not promise a certification.
01
Purpose and frameworks of enterprise architecture
What enterprise architecture is for, and what to take from frameworks such as TOGAF as a reference.
- Business, data, application and technology domains
- Frameworks as reference: TOGAF concepts (ADM, repository)
- Adapting a framework rather than applying it literally
- The architect's role and sphere of influence
- Typical failures: documentation for its own sake
Lab: A document of EA goals and success criteria for a given organisation description.
02
Capabilities and value streams
Model what the organisation does and how value flows, independent of IT.
- Business capability map
- Value streams and their stages
- Capability-to-application mapping
- Assessing capabilities by maturity and importance
- Heat maps to focus investment
Lab: A capability map and two value streams for a fictional distribution company.
03
Application portfolio management
Turn a list of existing systems into a portfolio that supports decisions.
- Application inventory and ownership
- Value, risk and technical health criteria
- Keep, change, merge, retire (TIME-style) decisions
- Detecting duplicated capabilities
- Keeping portfolio data current
Lab: An assessment table and recommended decisions for a fictional 20-application portfolio.
04
Target and transition architectures
Move from the current state to the target through achievable intermediate stages.
- Baseline, target and transition architectures
- Gap analysis
- Dependencies between transition stages
- Intermediate states that deliver value
- Planning risk and rollback
Lab: A three-stage transition roadmap from a legacy ERP to a modular landscape.
05
Principles, standards and governance without bureaucracy
Build rules that keep consistency without getting in the teams' way.
- Architecture principles: statement, rationale, implications
- Standards, recommendations and the exception process
- Architecture forum and decision rights
- Guardrail approach: pre-agreed paths
- Assessing governance impact (as quality signals, without promising numbers)
Lab: A governance model draft with five principles, two standards and an exception process.
06
Technology radar
Classify technology choices in a transparent, updatable way.
- Radar rings: adopt, trial, assess, hold
- Selection criteria and rationale
- Technology lifecycle and exit plans
- Updating the radar together with teams
- How the radar relates to ADRs
Lab: A draft 15-item technology radar for a fictional organisation, with rationales.
07
Integration and data strategy
Define how systems and data connect at organisation level.
- Integration platform and API strategy
- Data ownership, master data and catalogue
- Data quality and accountability
- Privacy and regulatory constraints
- Trade-offs between centralised and distributed data models
Lab: A one-page summary of an integration and data strategy for a fictional organisation, with first steps.
08
Aligning roadmaps with business strategy
Link technical plans to business goals and present them to leadership.
- From strategy to capability investments
- Prioritising the roadmap
- Presenting investment decisions
- Balancing short and long term
- Adapting to change and refreshing the plan
Lab: An 18-month architecture roadmap for a scenario with stated business goals, and a short leadership presentation.