Enterprise Architecture roadmap definition and review process. Best practices on reconciling Architecture Architecture roadmaps across domains. This includes review of Architecture roadmaps across functional and architecture domains (BDAT). Best practices for aligning Enterprise Architecture (EA) roadmaps with Architecture governance and technology management.

1. Architecture Roadmaps
Best practices for reconciling Architecture roadmaps
across domains
Mohan K
http://www.mohanbabuk.com/
https://www.linkedin.com/in/mohanbabuk

2. 2
Topics
● Roadmap Framework and Context
● Architecture Roadmap process alignment
● Architecture Roadmap Life Cycle and continuum
- Roadmap Pre-work
- Process: Baseline and Validate Roadmap Inputs
● Roadmap Workshop Outcome
- Updated Strategy Roadmaps
- Updated Business Architecture Roadmaps
- Updated Technology Roadmaps
● Roadmap Reconciliation: Tips and Lessons learnt
● Appendix, References and links
- Illustrative Agenda
- Workshop Flow

3. 3
Roadmaps - Framework
Future
State
Current
State
Roadmap
Strategy
Technology
Drivers
Business
Drivers
External Influences
Industry
Competitors
Customers
Regulatory
Legal
Shareholders
Internal Influences
Targets
Constraints
Aspiration
External Influences
Emergent Technologies
Strategic Vendors
Internal Influences
Obsolescence
Vision
People
Process
Technology
Plan
Timeline
Dependencies
Metrics
Reality
People
Process
Technology
Architecture roadmaps provide a focus for better alignment and efficiency in driving the
company strategy. They show the “must do” capabilities that need investment and
implementation over time.

4. 4
Architecture Roadmaps: Process Alignment
What How Who (Stakeholders )
These roadmaps provide
transparency on the
evolving 5+ year
capabilities needed to
enable the long term SBS
and IS strategy
Identify and update
“strategic themes” (The
major strategic themes to
enable our 2025 strategy,
identified in 2017)
• Business/Enterprise
Architects
• Business Partners
(business functional and
regional strategies)
• Leadership Teams
• Vendor / Partners
They show the “must do”
capabilities that need
investment for domains
over time
Update domain inputs –
ensure Architecture
domains are aligned with
business drivers
• EA, IS Architecture &
Planning
• Business Partners
(business functional,
regional views)
• Vendor/Partners
Technology Architecture
roadmaps guide the IT
related services from
various supplier / Vendors.
Align the high-level (AS-
IS) as well as the Target
(TO-BE) IT architecture
for the specified technical
domains
• EA, IS Architecture &
Planning
• IS Leadership
• Vendor/Partners
Business Architecture
Roadmaps
Strategy Roadmaps
Technology
Roadmaps
• Business Goal: $25 Bn by 2025
• Full integration of XYZ and ABC lines of business (including ongoing M&A)

5. 5 Projects / Changes
• Strategy, Business Architecture and Technology roadmaps
• Common view of the must-have IS portfolio entries for following year
• Validation of “must do” domain capabilities that need investment
Updated Roadmaps
Roadmap
Review
Corp
Strategy
Vendor/
Partner
updates
Budget ,
Portfolio
May
Sept.
Nov
StrategyOperations
Roadmap
Review
Biz.
Partner
updates
Global,
Regional
Roadmaps: Life Cycle and continuum (Proposed)

6. 6
Process: Roadmap Pre-work
1. Collect the Leadership Team strategy inputs, drivers and alignin with existing roadmaps
2. Architects receive and review IS and Business Strategy documents
1. Agree on IS Themes for review
2. Allow assimilation of IS Themes
3. Gather roadmap data in a structured template (e.g roadmap catalog XLS).
1. Create multiple roadmaps views using data in roadmap catalog
2. Views may be based on customized presentation templates (E.g less detail, tell a story
for senior stakeholders)
4. Identify appropriate format for roadmap reviews
1. Face-to-Face review, offline reviews and workshops as appropriate
• Technology Landscape: System, Information and Integration views
• Vendor / Partner updates on Technologies and Services
• Syngenta strategy updates – inputs from various sources
• Updates from Business partners – Functional business and regional
inputs
Inputs

7. 7
Process: Baseline and Validate Roadmap Inputs
1. Define and update Roadmaps capabilities for all domain/sub-domain
• Reconcile roadmaps across Architecture domains (timelines, common services and
requirements)
2. Domain architects (grouped by IS Theme) provide a combined transformation map based
on their individual domain roadmaps
• Define Capability Maps (Benefit Dependency Network) across domains
• Align Roadmap capabilities with Portfolio proposals (use BDN to revalidate)
3. Identify dependencies and gaps across roadmaps
• Highlight Business and Technical capabilities on roadmaps
• Validate roadmaps with stakeholders
• Updated Strategy Roadmaps
• Updated Business Architecture Roadmaps
• Updated Technology Roadmaps
Outcome

8. 8
Roadmap Workshop Outcome
Baseline and communicate roadmaps to stakeholders
• Updated Strategy Roadmaps : Enablers for major strategic themes. The
following have been identified to enable our 2025 strategy:
• Integrated Commercial Solutions
• Integrating our Information Assets
• Virtual and Independent Enterprise
• Build our Digital Products
• Updated Business Architecture roadmaps: provide a focus for better
alignment and efficiency in driving the company strategy and implementation
across domains over time.
• Updated Technology Architecture roadmaps: document the high-level (AS-IS)
as well as the Target (TO-BE) IT architecture for the specified and agreed
technical domains

9. 9
Roadmap Reconciliation: Tips and Lessons learnt
•Delink ownership and cross-domain dependencies by focusing on just the “content” of roadmaps
• Use XLS/Tables and common templates
•Acknowledge geography and Time-zone challenges of working with Architecture group
• For Face-to-face meetings, use post-it notes, printed roadmap charts views and other tools
• For virtual meetings use other visual aids to support voice and Instant messaging. Where
possible use Video conferencing
Tip: Address Roadmap ownership (human dynamics)
•During initial roadmap discussions, focus on content and capabilities.
•Minimize focus on “visuals” (It is not important to discuss T-Map vs Gantt Chart vs other views or
the formatting of roadmap. This can happen later)
•Highlight key capabilities and roadmap building blocks
• What/ Why: /Objectives of Roadmap based on Business Strategy and drivers
• When: Indicative Timeline
•Capture these key data elements in a tool
• Use a spreadsheet, database or EA tool
• It is easy to convert data from a tool to a formatted view (T-Map, Gantt Chart etc)
Tip: Delink template from roadmap content and message

10. 10
Roadmap Workshop : Illustrative Agenda
Purpose
Objectives
Output
To review the BA roadmap and agree the 2020 capabilities that are needed in the portfolio to
support the business and IS strategy
Outcome
• Common view of the Must-Have 2020 portfolio entries based on knowledge of the strategy
• Agreement that the portfolio entries are improved by having a holistic view of architecture
roadmaps
Next steps with owners for moving the 2020 portfolio entries
• Provide transparency on the evolving 5+ year capabilities roadmaps
• Identify the 2020 capabilities (keystones/ milestones) that we need developed in order to
support the business and IS strategy themes

11. 11
Day-long Workshop Flow
Check in
0830-0845
Check Out
1715-1730
IS Strategy
0915 - 0945
Functional
Overview -1
1000-1100
Integrating
our Data
Assets
1400-1515
Functional
Overview -2
1100-1215
Virtual and
Independent
Enterprise
1530-1645
Build Our
Digital
Products
1300-1400
Wrap Up
1645-1715
Introduction
0845-0915

12. 12
Roadmap Structure and Table of Content (TOC)
1. Info. – Rivision Control
2. Principles
3. Assumptions
4. Requirements
5. Building Blocks
6. AS-IS and/or TO-BE
7. Roadmap Timeline
8. Risk and Mitigation
Building blocks (Architecture
Summary, Background)
Short / mid term timeline in
Gantt Chart and
Long term (> 3 years) in a T-Map
Define domain guiding principles
Highlight key assumptions and
requirements