Business management, IT governance

1. 1
IT Transformation
Governance
An Outcome Driven Playbook

2. 2
Challenges
Why master IT transformation?
Continuous Market Changes IT Lack of agility Projects Silos
● Isolated projects and local
initiatives can’t lead the global
transformation of IT, and the
company
● Enterprise Architecture must
support this transformation by
providing an optimal target, and
project guidance to reach it
● IT projects need to be aligned
with the corporate strategy
in a context of constant digital
transformation & technological
disruption (mobility, cloud, big
data,...)
● IT is the result of years of
projects: legacy applications
cohabit with new & modern
applications; systems are quite
interconnected
● To address new business
needs, to integrate new
technologies, IT needs to evolve
smoothly and with agility

3. 3
Methodology
How do I get it done?
3
2
1
Define the governance
framework
● Control IT foundations and
propose optimizations:
● Information Data
● Applications/Services
Catalogs, Interfaces
standardizations
● Technologies
● Promote foundations during
projects or participate in IT
transverse projects
● Participate in projects:
● Impact analysis
● Architecture review
● Transition path
● Promotion of standards
● Approve target architecture &
IT transformation principles
● Architecture Review board
Control IT foundations Keep architecture aligned
with the strategic vision by
contributing to projects
● Capture the company’s vision,
objectives, strategy and tactics,
strategic planning
● Get the big picture (projects,
applications portfolio,...)
● Map business capabilities. Plan
capabilities with regards to strategic
objectives and the business roadmap.
● Define rules, policies & standards for
IT transformations projects
● Define the EA governance &
deliverables

4. 4
BUSINESS CAPABILITY MAP
Step 1
Define the governance framework
Get the IT Roadmap identifying the expected transformation phases and plan the
delivery of the expected capabilities aligned with the Business objectives
Build your own
Business Capability
Map (or import a
standard one
according to your
industry) and link
the existing
applications
1
Define the governance
framework
● Capture the company’s vision,
objectives, strategy and tactics,
strategic planning
● Get the big picture (projects,
applications portfolio,...)
● Map business capabilities. Plan
capabilities with regards to strategic
objectives and the business roadmap.
● Define rules, policies & standards for
IT transformation projects
● Define the EA Governance &
deliverables

5. 5
Step 2.1
Control IT foundations
INFORMATION DATA
Reference architecture of the
information and data views (data
definition, reference business line
objects, reference models, pivot
formats) helps to:
• Reduce inconsistencies in the
definition of data
• Simplify and standardize the access
to shared data
• Simplify and standardize the
exchanges intra-and inter-company
APPLICATION INTERFACES STANDARDIZATION
The modeling of application interfaces will help to
identify the possible standardization (ESB, pivot
format,...) to ease the integration of new applications
in the IT landscape
2
● Control IT foundations and
propose optimizations:
● Information Data
● Applications/Services
Catalogs, Interfaces
standardizations
● Technologies
● Promote foundations during
projects or participate in IT
transverse projects
Control IT foundations

6. 6
Step 2.2
Promote IT foundations during projects
TECHNOLOGIES
Technology & obsolescence management helps to
promote the reuse of recommended technologies.
APPLICATION / SERVICES CATALOGS
Application portfolio management helps to promote the
reuse of existing applications and control the
applications catalog. Any new application, or new
functionality expected will be compared to existing
applications in the capability map.
2
● Control IT foundations and
propose optimizations:
● Information Data
● Applications/Services
Catalogs, Interfaces
standardizations
● Technologies
● Promote foundations during
projects or participate in IT
transverse projects
Control IT foundations

7. 7
APPLICATION ARCHITECTURE DIAGRAMS
- Modelling of AS-IS Architecture
- Definition of TO-BE Architecture
- Gap analysis to prepare transition path
Step 3
Keep architecture aligned to the strategic vision by contributing to projects
EA DELIVERABLES
- Identification of :
- Business processes supported
- Capabilities impacted / functionalities
provided
- Data manipulated
- Systems interfaces
- Deployed infrastructures
- Architecture Definition File
- Review / approval / Check lists
3
● Participate in projects:
● Impact analysis
● Architecture review
● Transition path
● Promotion of standards
● Approve target architecture &
IT transformation principles
● Architecture Review board
Keep architecture aligned
with the strategic vision by
contributing to projects

8. 8
All reports (1)
Propose or mandate technology standards
and others architectural patterns
Required data
• Technologies
• Technologies' Lifecycles and Status
• Software Vendors
TECHNOLOGY STANDARDS
Manage backlog to maintain clear visibility on
how developments support business
capabilities with projects and deliverables
Required data
• Business Capabilities & Functionalities
• Projects
• Solution Building Blocs: Application
Systems, Applications, IT-Services,
Micro-Services,…
BUSINESS CAPABILITY COVERAGE
Bring an overview for each transformation
phase to dev teams so that they get the full
picture of needs and features
Required data:
• Business Capability Hierarchy
• Functionalities (Features)
BUSINESS CAPABILITY MAP

9. 9
All reports (2)
Expose how the overall application system
is/will be integrated in the IT Landscape, how
applications work/will be working together,…
Required data
• Application Systems
• Applications
• Org-Units
• Interactions and Service Points
Design the Architecture: how the application
will be integrated in the application system
with other existing or developing applications
Required data:
• Applications
• IT Services
• Interactions and Service Points
APPLICATION SYSTEM
ARCHITECTURE
APPLICATION ARCHITECTURE
Plan the delivery of the expected
functionalities aligned with the Business
Objectives and Capability improvements
for each transformation phase and
increments
Required data:
• Objectives
• Business Capabilities
• Functionalities (Features)
• Digital Transformation Phases
IT ROADMAP

10. 10
All reports (3)
Explore Data description and Service
Catalogs to reuse components and deliver
better quality, cheaper and faster
Required data:
• Information Architecture at semantic,
logical or physical levels
• Service Catalogs : IT Services, Micro-
Services, Technical Services,…
DENDROGRAM ON DATA CATALOG
Build, share and take note of pivot data
models of IT services and data structure, …
and/or other UML diagrams
Required data:
• Classes, Attributes,
Associations/Parts,…
• All UML2.0 diagrams required
UML CLASS DIAGRAM
Design features and/or enablers: solution
components and model emergent
architecture in an agile way
Required data:
• Scenarios (for Main Use Cases)
• Applications, IT Services, Micro-Services
• Application flows and Business Objects
SCENARIO OF APPLICATION FLOW

11. 11
All reports (4)
Check dependencies of the application with
the overall solution architecture
Required data:
• Project portfolios
• Projects
• Project lifecycles
• Project dependencies
360° MATRIX
Define infrastructure architecture in
alignment with Business Needs.
Re-use Architecture and deploy Architecture
Patterns
Required data:
• Applications, IT Services, Micro-services
• Technologies, Technology Stacks
• Servers, Networks, Routers,…
• Workstations, Laptops, Smartphones
• IT Peripherals, IoT, other devices, …
• Sites (Datacenter, Internal or External
Cloud,…)
IT INFRASTRUCTURE DIAGRAM
Distribute IT Service & Software Technology
to the technical zones according with Tech
Architectural Pattern
Required data:
• IT Services
• Technical zones
• Communication Lines, Formats and
Protocols
TECHNICAL ARCHITECTURE

12. 12
Challenges
How does EA help to master IT transformation?
● EA mission:
● Provide the “IT big picture”
● Propose IT transversal optimisations and
optimal targets:
o Rationnalization of applications
o Standardization of applications interfaces
o Set-up of master data
● Elaborate rules, principles & standards for IT
transformation projects
● Continuously ensure IT global consistency
by supporting projects:
o IT alignment to business needs & IT strategy
o IT modularity & agility
o IT global optimization (reuse of applications,
building blocks, patterns,..)
o Compliance with security & regulations
● In alignment with portfolio management
(projects, applications) activities
EA Projects
Initiate
Plan
Design
Build
Validate
Go Live

13. 13
Hopex Collaboration Tools
Collaboration around a single point of truth
Where can you share and find architecting data in your organization?
Application Owners
Applications
and Data Flows
Enterprise & Business
Architects
CIO
Business
Analyst
CEO & CxO
CTO
Shared Services Engineer
Information & Data Architect
System & Technical Architect
Infrastructure & DevOps Architect
Technology Portfolio Manager
IT Service Manager
…
Solution Architect
PMO
Strategy & Objectives,
Business Capability
Map & Value Steam
Tag, Follow and Share Objects in Hopex
Collect, Assess and Manage Ideas
Decentralize Decision-Making with Review Notes
Solution Architecture
Standards, Patterns
and Expertise
Technology
Standards
Solution and
Portfolio
Roadmaps
Portfolio Vision
To-Be Processes
definition
Project
Monitoring
Objective: disseminate &
decentralize the actions
of Enterprise Architecture

14. 14
Tips & Tricks
EA should primarily be involved in the strategy and solution design stages
EA provides all stakeholders with
general representations of the IT
(processes, functions, applications,
information) in order to:
• share knowledge about the existing
situation,
• ensure the strategic alignment of
projects,
• carry out functional and technological
impact studies,...
The project collects elements of
analysis and framing during its
upstream phases (opportunity
study,...) and provides a global
description of its provisional target
(preliminary study,...) then its final
target (start-up).
The corporate architects support the
project in its modelling work and in its
Gate Reviews with an Architecture
Review Board
Vision
/Strategy
Plan Design Build Validate Go Live
Enterprise Architects
✓ Identify the concerned Capabilities
✓ Identify the concerned applications
✓ Check the durability of applications
✓ Check the functional coverage
✓ Check the requirements compliance
✓ Select solution
IT Architects
Project Manager
✓ Check compliance with EA principles
✓ Check compliance with IT standards
✓ Support architecture definition decisions
1 2
1 2

15. 15
Tips & Tricks
Business Value Metrics
● Level of coverage for Capabilities required for strategy
● Enterprise utilization of enterprise standard & recommended platforms, technology
● % of projects with Architecture approval
● % of applications compliant with EA principles & guidelines
● Level of modularity of IT (number of applications using standard interfaces (ESB),..)
● Master data dissemination (number of applications using master data,..)
● % of reuse per projects (service, functionalities, applications, master data,...)
● Quantified Savings from Architecturally led portfolio reductions
● Number of strategic projects delivered on time
● % of projects using the EA repository

16. 16
French Bank
Setting up an EA practice
● Objectives
● Manage increasing IT complexity to meet rapid change
expectations, under pressure from an increase in
regulation and a trend towards non-traditional digital
banking applications
● Be able to support and secure the digital
transformation of the business with a strong EA practice
(initial situation: 4 teams, 4 metamodels, 4 platforms, no
unified language…)
● Results
● A unified EA Shared Services Center with one team,
one platform, a federal approach for the 29 BU
o To capitalize, share information, plan IT roadmap
● Single source of truth within a unique repository:
o 15,000 applications, 4,000 business processes, …
o Creation of a business glossary with 9,000 business
concepts
● Implementation of a corporate governance
● and a community of Architect with 500+ persons, incl.
300 experts TOGAF or ArchiMate certified

17. 17
IT Transformation
● Objectives
● Gain better insight into the interdependencies of
applications and technologies
● Identify unutilized, redundant or non-compliant
applications
● Develop strategies for the modernization of their
systems
● Meet the demands of a growing company with a
bigger focus on digital transformation
● Results
● Created a complete view of organization’s
EA by rationalizing data and applications, thereby
identifying and realizing downstream cost savings
● Created consistency and structured work
projects that helped standardize documentation and
increase output of digital documentation
● Moved from an EA “push” mode to a business
“pull mode” that successfully communicated the
value of EA output across business units
● Enabled faster and more streamlined planning
by using HOPEX data as a single source of truth for
application inventory
“The EA group is an influencer of strategic planning and
HOPEX provided us with the ultimate visibility required
to have a holistic understanding of ecosystems, data,
and interdependencies across the business
units. Through visualizations and dashboards, business
managers are empowered to translate data into
action. And, as a trusted advisor to the business units,
our EA team has a seat at the table to influence
strategic initiatives.”
- Financial Services Company Senior Manager,
Enterprise Architecture
US Bank

18. 18
IT Transformation journey
What’s next?
Horizontal inventory, Impact analysis, Communication
SECURE
RATIONALIZE
EA BASELINE
Application & Technology Inventory, Capability Mapping
& Enterprise Portal
EA BASELINE
TRANSFORM
IT Strategic Planning
Application Rationalization Technology Standards & Obsolescence
IT Policy &
Regulatory
Compliance
Data
Compliance
Data Glossary
Management
Agile Solution
Architecture
Complex Systems
Architecture
Cloud Migration
Resiliency
Architecture
IT Transformation Governance

19. 19