Enterprise Architecture Management (EAM) I Best Practices I NuggetHub

1NuggetHub 2019. All rights reserved |
Best Practices
E N T E R P R I S E A R C H I T E C T U R E
M A N A G E M E N T ( E A M )

Architecture Target Picture Development3
Enterprise Architecture Approach2
Need for Enterprise Architecture Management1
Agenda
Implementation Roadmap4

The growing importance of digitization drives the increasing
complexity and number of business opportunities through transformation
66.4 % of CIOs
assume that their
business models
will significantly
change
42.3 % face
challenges in the
integration of
new technologies
into existing IT
architectures
62.9 % are
concerned about a
lack of employees
with necessary
digital know-how
and capabilities
90.0 % could not
realize innovation
processes within
previous initiatives
so far
Organizations require an architecture management aligning business and IT
requirements by integrating new and legacy systems focusing on most valuable
artefacts as well as by utilizing customized digital applications

Enterprise Architecture Management focuses on all domains of an
organization and aims to fasten up the adoption of new technologies
GOVERNANCE
vs. vs. vs. vs.vs.
PROCESSES APPLICATIONS SYSTEMSDATA
Integrated top-
down
& bottom-up
Global, seamless
integration
Focus on business
requirements
Modular & flexible
system design
Real-time
analysis
The more mature the Enterprise Architecture Management function, the more likely is a
rapid integration of new technologies and innovation of business models
Complex & unclear
hierarchies
Redundancy &
missing interfaces
Missing & ambiguous
documentation
Legacy systems &
long release cycles
Missing in-memory
computing

The maturity of the overall architecture
capability can be measured in 7 dimension
Framework for enterprise architecture capability maturity
ARCHITECTURE GOVERNANCE
How is enterprise architecture
managed and controlled
enterprise wide?
ENTERPRISE
ARCHITECTURE
CAPABILITY
How mature are the
architecture capabilities?
VALUE CONTRIBUTION
Which value does the Architecture
Mgmt. create for the overall
enterprise?
ARCHITECTURE SKILLS
FRAMEWORK
Do roles provide the adequate
level of skills?
ARCHITECTURE CONTRACTS
How is the collaboration between
development partners and
sponsors designed?
ARCHITECTURE BOARD
How successful is the
implementation of the IT-
governance strategy overseen?
ARCHITECTURE COMPLIANCE
Is the compliance of projects
within the enterprise architecture
ensured?

Agenda
Framework, Objectives and Principles1
Activities and Processes2
Roles and Governance3
Enterprise Architecture models and tools4
Success factors for implementation5

An integrated approach is mandatory to set
up a successful Enterprise Architecture (EA)
Our perspective on EA
Benefits
What?
Roles &
Governance
Establish relevant EA roles
and functions as well as
ensure effective and efficient
collaboration in governance
committees
 Establish prerequisites
to make EA actually
working
 Support planning,
implementation and
control processes ("EA as
catalyst")
EA model &
tools
Establish a detailed picture
of current and target EA
and provide tools to
maintain and use EA data
and information
effectively
 Single source of truth -
transparency on the
current and target EA(s)
 Insights on pain points
and development areas
(e.g., risks, business
support gaps)
Activities &
Processes
Establish and leverage EA
competencies (methods,
techniques) to develop,
analyze and evolve the
client EA ("EA in a narrow
sense")
 Obtain competency to
develop a business
oriented EA that
contributes to the
business and IT
strategies and goals
(e.g., Cloud, Digital)
Objectives &
Principles
Define clear objectives for
EA and derive overall
principles for the daily work
which can be translated into
EA principles for projects
 Common understanding
of the EA value
 Transparent guidelines
for daily work and target
picture design

The strategic objectives and principles are guidelines for the EAM
DETAILS
 Objectives for EAM should be part of
the overall IT strategy
 The objectives on the left are general
objectives and should be adjusted
regarding company specifics
 Principles should be consistent to the
objectives and their characteristics
per dimension should be defined by
IT senior management
OBJECTS AND PRINCIPLES
• Business IT Alignment to
design solutions based on the
business strategy
• Transparency about business
and technology trends to
enable new business models or
digitization opportunities
• Transparency and
communication to reduce the
complexity and enable flexibility
• Implementation of further
governance guidelines to
improve IT steering
• Central architecture steering
• Agile organizational structure and decentral
architecture development
• Continuous alignment with business for high
business orientiation
• Continuous, evolutionary development and
project based implementation
• Involvement of senior management
• Regular business feedback regarding EAM
• Architecture artefacts are available centrally
• Overarching guidelines involving several focus
areas
• Involvement of EAM in strategic planning and
regular controlling of architecture
PRINCIPLES
OBJECTIVES
EXAMPLE

Agenda

The evolutionary, iterative design of the approach tackles pain
points and potentials in the current architecture strategy rapidly
…constitutes the baseline for
target architecture and
optimization measures based
on business and IT strategy
ARCHITECTURE STRATEGY
…ensures a pointed focus on all
architecture projects and thus,
an alignment of business and
IT along prioritization, bundling
and execution
ARCHITECTURE PROJECT
PORTFOLIO MANAGEMENT
…enables the support for IT and
business decision-makers
while ensuring a lean
organization based on joint
agreements
PROJECT SUPPORT
…allows an evolutionary
development by a continuous
determination of architecture
gaps and pain points following
the principles & standards
ARCHITECTURE
CONTROLLING
Digital
Architecture
Management

ARCHITECTURE PRINCIPLES
Central definition of basic principles and
guidelines for architectural domains
ARCHITECTURE DEVELOPMENT
Target images and artifacts on business, data,
application & infrastructure level
PROJECT-BASED IMPLEMENTATION
Implementation control based on architecture
contracts and support of architects
ARCHITECTURE COMMUNICATION
Central repository and publication of architectural
principles and artifacts
ARCHITECTURE REVIEW
Identification of weak points & gaps for the deri-
vation of architectural optimization measures
AGILE PROJECT EXECUTION
Implementation of project tasks in small and
agile Teams
REQUIREMENTS ANALYSIS
„Architecture Gate "in Demand Management to
evaluate the impact on architecture
PORTFOLIO MANAGEMENT
Aggregation, prioritization and planning of
identified architectural optimization measures
The approach is based on an iterative
development approach
Digital
Architecture
Management
Enterprise
Architecture
Management
1
2
6
7
8
5
3
4

The EAM process integration approach combines strategic planning,
project life cycle as well as operation and monitoring
EAM process integration
Develop
architecture
vsion
Situation
analysis
Elaborate
strategic
options
Roadmapping
and migration
planning
Project
portfolio
planning
Evaluation of
architecture
evolution
Evaluation of
architecture
evolution
Strategic Planning Project life cycle
Operation and monitoring
Monitoring the EA
Implement
operational
changes
Assess
operational
changes
Pilot and
roll-out
Project
set-up
Design
solution
Implement
solution
Convert very
small
projects into
operational
changes
Convert large
operational changes
into projects
1
2
3 4
5
6
1
2
3
42
31
4

Agenda

The concept requires assigning clear roles and responsibilities to
continuously improve the IT landscape
Business IT
…supports development of
digital solutions in alignment
with business goals and the
architecture function
ENTERPRISE ARCHITECT
…is responsible for process
management of goals, functional
requirements and continuous
development
PROCESS OWNER
…is responsible for an IT
solution regarding
functionalities, continuous
development and
dependencies
SOLUTION OWNER
…is responsible for the
technological layer of the
application architecture
TECHNOLOGY ARCHITECT
Solution
Owner
Process
Owner
Digital
Architecture
Management

A basic architectural governance model consists of architectural
governance, business as well as IT roles
Architecture governance model
Senior leadership
Office of the CIO, CFO or CEO
Enterprise architecture council
Chair: Chief architect
Guiding principles working group
Architecture framework working group
Security standards working group
Other working groups
Architecture review board
Chair: EA program manager
Program project teams
Project 1
Project 2
Project n
Architecture forum
Chair: rotating
Business
BU 1
Business architects
BU IT architects
BU n
Business architects
BU IT architects
Corporate 1
Business architects
Corporate n
Business architects
IT
Architects
Information
architects
Application
architects
Other
Programme
management
Service architects
Infrastructure
architects
Security
architects
Integration
architects
IT finance
ParticipantsParticipants
Escalation
Participants
Participants Participants
Participants
Escalation
Influence
Guidance
Standards
Mandate

Role: Enterpise Architect
DESCRIPTION
TASKS
• Develop initiatives and measures for the further development of
architecture
• Implement measures and initiatives
RESPONSIBILITY
The Enterprise Architect conceives and controls IT architectures centreally and ensures their alignment with strategic corporate goals. He
supports strategic planning, manages the further development of the architecture by developing targeted measures in cooperation with the
Solution Architects and is responsible for the implementation of such measures in projects.
• Understand of customer needs
• Analyze the corporate strategy and advising management in
determining the further development of the digital strategy
• Record the needs and expectations of clients with regard to
systems and architectures
• Develop evaluated solution proposals and decide bases on the
basis of the recorded requirements
• Accelerate decision making through communication with cross-
functional teams
• Develop solutions and proof-of-concepts for further architectural
development
• Develop and implement quality standards regarding architectures
• Plan and execute of workshops and project kick-offs
Professional experience
• University degree (computer
science)
• Several years of professional
experience in application
development, architecture
(further) development, IT
consulting (internal/external)
SKILLS
Qualification
• Extensive knowledge of the
business processes, challenges
and procedures
• Ability to identify developments
in technology fields and adapt
them to business areas

Role: Enterpise Architect
DESCRIPTION
TASKS
• Correctness of technical specifications (esp. coverage of technical
specifications)
• Short- and long-term further development of the application
architecture
RESPONSIBILITY
The Solution Architect is responsible for the technical solution conception and the design of applications based on technical specifications.
This includes the technical specification of the technologies to be used as well as the application architecture and data structures as a basis
for application development. The Solution Architect role is defined with a specific technology focus.
• Design, evaluate and select technical specifications for solutions to
be developed (e.g. technologies used, application architecture,
data model, user interface)
• Plan the software and, if necessary, hardware requirements for the
solution to be developed
• Design the test and acceptance concept in coordination with
process and application consultants
• Prepare introduction, alternative and relapse concepts
• Involve in evaluation and selection of service providers for external
support
• Coordinate and cooperate with external service providers in the
design and implementation of solutions
• Identify and investige new technologies with potential benefits
• Support for major maintenance measures (2nd / 3rd level support)
Professional experience
• University degree (computer
science)
• Several years of professional
experience in the field of IT
application development, IT
project management
SKILLS
Qualification
• Knowledge of modern IT
methodologies, technologies,
architectural patterns and
development
• Experience in developing
modern software architectures
for agile and mission-critical
applications

Agenda

The Integrated Architecture Framework gives guidance on which EA
artifacts are required and how they are linked to each other
EA model: Integrated Architecture Framework
Conceptual
“What?”
Logical
“How?”
Physical
“With what?”
Contextual
“Why?”
Business
Architecture
Information
Architecture
Information
Systems
Architecture
Technology
Infrastructure
Architecture
Overarching goals, architectural scope and principles
Aspect areas
(“architecture aspects")
Architecture
layers
Business IT
Principles & services
Components &
interaction
Standards, guidelines &
actual products
 Business goals
 Business
services
 Business
processes
 Business
organization
 Business objects
 Information flow
 Application
landscape
 Application
domains
 Applications
 Technical
landscape
 Software
components
 Hardware
components
 Cloud platforms
Governance
Security

To reap the benefits of Enterprise Architecture, organizations need to
ensure certain EA prerequisites and integrate EA into operational and strategic
processes
EA governance model
EA
prerequisites
EA
enhanced
processes
EA
benefits
Transparency
Management
support
Governance
prerequisites
Planning
EA planning
consulting
Architecture
initiative
Alignment
EA portfolio
review
Project portfolio
alignment
EA project
review
EA documen-
tation update
Project portfolio
review
EA analysis and
control
 EA prerequisites provide the
ground for effective EA
involvement
 Existing client planning,
alignment, implementation and
controlling processes are
enhanced by dedicated EA
practices ("EA as catalyst")
 EA enabled benefits (can be
measured by client EA)
 Dedicated EA function
 Project portfolio and project processes (e.g.,
stage-gate)
 IT strategy and business planning processes
Examples
Implementation Control
Strategic Fit
Business IT
Alignment
Agility

Stakeholder involvement and Change Management will be key for
achieving a sustainable EA transformation
Stakeholder involvement and change management approach
Change Management Toolbox (excerpt)
Change management tools for the client EA project will be jointly selected while setting-up the project.
Change Vision &
People Strategy
Leadership
Commitment
& Engagement
Stakeholder
Mobilization
Organization &
Process
Alignment
People
Performance
Cultural
Development
Change
Sustainability
Change Management Framework
Stakeholder Analysis Focus Interviews Collaborative
Workshop
Change Readiness
Assessment
Change Roadmap Roadshow/ Info Fair Web 2.0 Tools Temperature Checks
Culture Analysis/
Radar
Communication
Concept
Change Impact
Analysis
Department/
Team Meeting
Change Story Change Agents Change Sponsor Knowledge transfer

Our Digital Platform Architecture Framework provides an architectural
blueprint for scalable and agile IT platforms that integrates on-premise and
cloud solutions
The Digital Platform Architecture Framework defines capabilities of a digital
platform that integrates on-premise and cloud-based digital services with
respective back end systems to enable business services
Reference architecture & accelerators:
 Integration – Integrate data, mobility services & applications quickly
 API Management – Unlock and leverage data via API enablement
 Identity & Access Management – Authenticate customers at every touch
point
 Service Management – Evaluate performance and support operations
 Automated Provisioning – Implement cloud services for continuous delivery
 Application Lifecycle Management – E.g. governance, requirements &
project management
Central integration components Business services
Identity&AccessManagement
ServiceManagement
Personalisation & Interaction
Customer, Supplier, Partner Management
Operational
Business
Services
Common
Data
Services
Business
Support
Services
Automated Provisioning
Application Lifecycle Management
Integration
API Management (external)
API Management (internal)
Business Domains
Back End Systems Integration

We propose leveraging our reference framework to develop a common
IT technology solution map
IT Strategy Framework 3: Architecture: Technology Framework
Identity&AccessManagement
Phone eMail SMS Mail Desktop Mobile Social
ServicesManagement
Integration
Integration
Connected DevicesTablet
External API API Management
Internal API / Services and Data Integration
Operations Management
Content & Knowledge Management
Automated Provisioning
Application Lifecycle Management
Customers Partners Employees Public Authorities
Leasing / Financing, Insurance, Fleet, Mobility Services, Banking
Customer Management
Interactions Management
Public Front Ends Enterprise Front Ends
Leasing /
Financing
Insurance Mobility Services
Back End Systems Integration
Fleet
Description / Best Practices
 Internal IT delivery focus should lie on
business services
 Unlock data held within the business to
enable innovation of new services
 Integrate new cloud services from
your ecosystem of partners with existing
IT
 Avoid vendor lock-in, enable the ability
to swap services
 Maintain reliable microservice-enabled
integration flows
 Deliver change quickly and consistently
exposing your business services using
APIs
 Enable the continuous and rapid delivery
in a DevOps model
 Integrate federated identity
management
 Secure provisioning and operation of
combinations of cloud-based and on-
premise applications
Banking

Agenda

Roadmaps should be used as migration paths from the as -is state
architecture to the target architecture
Roadmapping
Current State
Business
Processes
Information Systems
Infrastructure
Future State
Business
Processes
Information Systems
Infrastructure
Roadmapping
Constraints:
Budget, time, dependencies,…
Derivation of roadmap
alternatives

A three-step approach should be followed to increase the
architecture awareness in project phases
How to increase architecture awareness in project practices
Obtain more decision
rights for architects
and install governance
rules
Participate actively in
the project portfolio
process and institute
EA reporting and
governance rules on a
multi project level
Advising
Assist, and advise
on project execution
Participating
Control project
execution
Managing
Control EA
implementation

The TOGAFTM Architecture Development Method (ADM) Cycle is
a standard tool in the architecture profession
TOGAFTM Architecture Development Method (ADM) Cycle

Due to our comprehensive EA methodology and project experience
our approach for client will be tailored based on a set of essential lessons
learned
EA lessons learned
Lessons learnt Implications for client EA project
Clarify objectives and guiding principles and an EA charter
with business and IT sponsors as starting point of EA
project
Ensure a mandate for EA realization in a suitable scope,
e.g. collaboration projects
Integrate EA in IT decision processes, e.g. an EA check
before project or budget approval
Focusing on “high impact areas” which either carry large
data volumes (highways) or realize tangible business
differentiation
IT / business goals
as
a starting point
Management
sponsorship
Integration of EA
Pragmatic approach
Involve business and IT stakeholders early on e.g. by
focus interviews, workshops, solution development and
transparency on results
Involve stakeholders
and change
management
EA needs to be derived from business strategy – to prove
the value of IT the contribution of EA on business targets it to
be analyzed
Business process
orientation

Agenda

The consulting company guiding principles enable a sustainable and
prioritized approach towards digital architecture transparency
Approach to digital architecture transparency
Business Domains &
Processes
Information Systems &
Interfaces
Technology &
Infrastructure
... ENABLE THE TARGETED EVOLUTION OF YOUR ENTERPRISE
ARCHITECTURE
Understand
your
objectives
1
Collect &
validate
data
2
Identify
potentials
and pain
points
5
Visualize
the results
4
Analyze
your
architecture
3
Define goals of
the target
architecture
6
Evolutionary
documentation –
documentation
overhead is
minimized
Minimal viable
architecture – focus
on prioritized
artefacts to increase
efficiency and
flexibility

A 12 step methodology starting with the identification of business
goals and requirements to design to -be landscape and transformation roadmap
Overal EA tools and services
Identification of business
goals and requirements
- Pauschalreise
- Individualreise
- Reisebüro
- Internet
- Call Center
z.B.
- eigene Hotels
- Vorabeinkauf
- Bedarfseinkauf
- …
- ...
- Premiummarke
- Billigmarke
Kunden / Marken
Produkte
Kunden-
kanäle
Länge der
Wertschöpfungskette
. . .
1
Definition of architecture
guidelines2
Definition of business
dimensions and their
importance
3
Identification of business
services and objects4
Definition of domains5
Identification of application
services6
Design of application
architecture (components)7
Design of interface
architecture8
Survey of as-is application
landscape9
Evaluation of as-is application
landscape10
Design of to-be application
landscape11
Definition of transformation
roadmap12

We propose a four step-approach to help setting up the client’s
long term IT architecture
EA development approach
Validate To-Be
Enterprise
Functions and
Use Cases
Develop To-Be
Architecture
Decide on
Future To-Be
Architecture
Evaluation
Architecture
Alternatives
 Define To-Be enterprise
functions out of To-Be processes
 Gather critical IT functionality
and IT improvement solution
 Define functional domain model
 Develop To-Be alternatives for
domain architecture
 Identify options for IT
architectures and underlying IT
applications
 Define set of evaluation criteria
and weighting factors
 Conduct alternative architecture
evaluation
 Perform fit-gap analysis for
architecture and software
solutions
 Conduct decision workshops for
agreeing on To-Be architecture
1 2 3 7 8 10
9
4
5
6 New IT
Improvement
Critical IT
Functions
As-
Is
To-
Be
Refe-
rence
Requirements Best Practices
Application
Cost
Functionality
Technology
To-Be
Architecture
√
Detailed
Requirement List
Functional To-Be Architecture
Evaluation of Solution Alternatives
Agreed To-Be Architecture
0
100
200
300
O.K. O.K.
Limit
Alternative 1 Alternative 2 Alternative n
Cost Business Technology
1
2
3
4

The proposed project approach supports definition of the future
Service IT architecture with help of alignment workshops and stringent
delivery of work packages
Project Approach & Key Deliverables
Kickoff
 Analyze and evaluate
feedback
 Develop best-match
result matrix
 Conclude on given
vision and conduct fit-
gap analysis
 Develop final
recommendation paper
Assessment process development Final Result
Presentation
Client Project Team focus Consultant Team focus
Project Management
 Map required functio-
nalities to domain model
 Define high level archi-
tecture scenarios
 Draft IT application
alternatives and map to
architecture scenarios
 Kickoff project
 Review vision of Client
BT service portfolio
 Validate existing
requirements and use
cases and complete
 Analyze existing
solution and map
existing applications
 Stake-
holder
alignment
 Consolida-
tion exist.
docs
 Confirm
project
plan
Scenario
development
Milestone
Result
analysis
 Define & align on provi-
der assessment
approach with focus on
assessment process,
evaluation and weighting
criteria
 Identify potential
solution providers
 Initiate and manage
process
1 week 2 weeks2 weeks 3 weeks3-4 weeks
Decide on Future To-
Be Architecture
Develop To-Be
Architecture
Scenarios
Ramp
Up
Evaluate
Architecture
Scenarios
Validate To-Be
Enterprise Functions
Requirements
validation
ActivityDeliverable
 List of validated/ com-
pleted requirements and
use cases, aligned &
mapped w.
requirements
 Overview of existing
applications
 Detailed domain model
 2-4 identified,
visualized architecture
scenarios
 List of IT application
alternatives
 Defined and detailed
provider assessment
approach
 List of identified
solution providers
 Fit-Gap overview and
result matrix
 Final recommendation
on architecture,
applications and
providers
 Aligned
project
approach
 Outline de-
liverables
documents
1 2 3 4
Workshop
Steering
Committee
Stakeholder
alignment

A typical EA approach potentially suitable for client consists of three
phases – phase 1 defined the future EA solution with clear deliverables
Proposed project approach and deliverables
EA strategy development
As-Is analysis
Conceptua
li-zation*Target pictures Roadmap
SC
Realization
and Review
3-5 months
1
a b c
EA pilot / quick win
implementation
e
Benefits case
Stakeholder and Change Management
f
g
 Scope definition /
stakeholder dialogue
 3rd party assessment of
existing EA framework
 Current EA pain points
and improvement areas
 Analysis of as-is EA
landscape
WorkshopSteering Committee
ASEd
SC SC SC SC
P h a s e 1
 EA zoning model
 EA guidelines and
principles
 EA processes
 EA target pictures with
solution maps for focus
areas
 EA governance
 EA strategy
 EA roadmap on a 3-5
year horizon
 Start of EA
implementation pilots
 Benefits case
 Realization
of defined
EA projects
 Continuous
development
of EA target
 Further
detailing of
identified
solutions
 EA
prerequisites
 EA projects
D e l i v e r a b l e s
2 3
P h a s e 2 P h a s e 3

Agenda

Enterprise Architecture Mgmt. function can
be set up in a three step process
OBJECTIVES
 Common understanding of Enterprise Architecture Management function
 Involvement of future achitects in implementation
 Transparent IT landscape
Design
Specify Enterprise Architecture Management
blueprint for company with responsible senior
managers
 Objectives and principles
 Activities and Processes
 Roles and Governance
Establish
 Recruit or release suitable personnel
 Develop skills
 Communicate new processes
 Coach and implement training measures
Operationalisation
 Align objectives for the first iteration of Architec-
ture Management with all relevant stakeholders
 Detail and coordinate Architecture Management
processes
 Establish committees for the first iteration
 Define the artifacts to be created in the first
iteration (scope)
 Define tools & templates to be used
 Execute first iteration of architecture management:
 Conduct architecture transparency
assessment
 Design target picture
 Define Architecture Guidelines

Enterprise Architecture Management (EAM) I Best Practices I NuggetHub

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Enterprise Architecture Management (EAM) I Best Practices I NuggetHub

Similar to Enterprise Architecture Management (EAM) I Best Practices I NuggetHub (20)

More from RichardNowack

More from RichardNowack (10)

Recently uploaded

Recently uploaded (20)

Enterprise Architecture Management (EAM) I Best Practices I NuggetHub