Creating value fromEnterprise Architecture

EAM Gathering - Bern – 7 July 2020

Luc Alix

Agenda:

• The strategy & architecture process• Supporting the process• Architecture values and artefacts, the EA Building• Realizing the values• Tools, methods & viewpoints• Changing architects and architecture• Use best practices

The Strategy & Architecture process

A simple cyclic process:• Recurring interval speed depending on complexity of the question• Iterating upon upon new gained knowledge or information• Delivering and improving results upon each iteration• Recognized by multiple frameworks like IT4IT (PLAN), COBIT (Managed EA), etc …

Integrate with the IT4IT capabilities

Strategy

Mission

Vision

Enterprise ArchitectureBusiness Architecture Application & Information

ArchitectureTechnology & Infrastructure

ArchitectureBusiness Capabilities

Business Processes

Products & Assets

Business Landscapes

Information & Data

Roles

Applications

Organizations

Application Landscapes

Databases & storage

Infrastructure components

Platforms

Locations

Infrastructure Landscapes

The EA Building

Tools & Methods

Use standard viewpoints

Improved and Efficiënt architecture work requires architects to change

Roadmap based on MVP’s

Architecture documentation to prepare

for next investments

Just enough, just in time architecture

Input

Input

Input

Input

Digitalize the EA activities

Reduce throughput time through reusabilityIncrease quality through uniformityAutogenerate and automateArchitecture deliverables are results, not goals

And …

Work agile wherever possibleOrganize by Business DomainMaintain relationships between deliverables

Dependencies between “features” are Domain levelDependencies between “products” are Enterprise level

Use architecture work to ease development and motivate decisions

Digitalize the EA activities

Fill the repository by creatingdiagrams

“If you don’t understand it,

model it”

Use the repository toautomate, autogenerate,

reuse and verify

Deliver value to yourbusiness with reports that

matter

Interface with operationaldata where applicable:• CMDB• Asset management• Portfolio management• Demand management• …

• Consistency checks• Delivery guidance• Architecture flows

Answer your business’s questions:• Which applications serve my

domain?• If I adjust my goal what will be

the impact?• If a technology is obsolete, what

are the consequences?• …

If you want to use EA tooling as a drawing program, then stick with Paint, Visio!

12 reasons why

1. Faster Roadmap production through clear dependencies2. Integrate Roadmapping with architecture deliverables3. Work with consistent Enterprise and Domain models4. Reduce architecture throughput time5. Encourage and stimulate reusability6. Increase quality through consistency and coherency7. Automated diagram generation8. Automatic content validation9. Practical application of “theoretical” frameworks10.Create uniformity in deliverables11.Remove architectural ambiguity12.Make architects work as “one team”

Control Marketing

Adapt to your business’ needs

Structure your EA repositoryto comply to your

Enterprise environment

Build custom propertiesthat matter and deliver

business value

Build reports in languages, layouts andapplications that your business understands

and make sure they ownthe reports and the data

If needed and applicableFeed data back in the repository