Definition of EA proposed by Len Fehskens at The Open Group and Eskil Swende at IRM

Value Driven Architecture

Don’t get stuck only documenting your process architecture, IT architecture, and Information architecture. Create a Value driven architecture to steer and govern value creation and change initiatives. Improve IT and take control of Digitalisation:

  • IT cost
  • IT acquisition
  • IT development
  • Reduce risk
  • Positioning

Architecture process

Our architecture process consists of three main processes, each with its own rhythm (frequency). First, the initial process that gives everyone an overview of the most important aspects of the business. This represents our “core architecture”. Next comes the process where changes are initiated and projects are defined so that we can both realise the desired changes and build the flexible digital platform. The third process supports the collaboration between architect and developers, and ensures that we deliver what was planned.

A SUSTAINABLE DIGITAL PLATFORM

Our architecture leads to a sustainable digital platform, which is necessary to build a flexible (agile) business when the environment, goals and strategies change. When in place, it must give support for quick and easy change. The digital platform should remain lean and flexible, without growing unnecessarily large and complex.

Information architecture
The information architecture is central to us. It is essential for business architects to create value. And it is important in the collaboration between architect and developer.
Process architecture
Business processes produce customer- and business value. The processes exist even if they are not documented. They must be documented, improved and changed as needed. Business process models are needed for other purposes than architecture. But it is important to have a common set of models for all use.
Application architecture

A new application architecture will be needed to create a sustainable digital platform that will enable easy and swift changes in business operations.

Architecture statements

Business architecture

The most important structures that make up the business.

High level

We start creating a “No detail up front” general high level architecture, showing us the main features of the As-Is situation and important areas for future attention. Weeks – not months or years.

Agile business

Our intention using architecture, is to create flexibility for change. Every business struggles with slow change.

Documentation

As little as possible. Our rule is “We are done, not when there is nothing more to add, but when there is nothing more that is unnecessary to remove. Short and focused on purpose.

Data oriented

We create and adhere to a data oriented application portfolio.

Data as a resource

Data is a resource and shall be governed after the same principles as all other resources. We show you how.

Data siloes

Old mental models create applications that own their own data. That creates data siloes and a considerable need for integrations. Unnecessary waste.

Waste

All businesses have duplicated solutions. Both data and software. An IRM architecture is necessary to eliminate duplication and waste.

Models

Models everyone can read, understand, and use to govern and make decisions.

Intent and result

Everyone can see and understand the situation and can agree on principles for creating efficiency and flexibility.

Cost

A high level architecture  is a cheap investment in models and insight that can be used to reduce future IT cost, and at the same time build flexible organisations

Principles

Learning from the the High level architecture, makes it easy to produce natural principles for acquisition of business applications

Lean

A lean approach to business processes is sensible. We have the same approach to IT. We eliminate waste.

Knowledge

People with knowledge about the business are necessary to create an architecture. We provide experience, methods , and techniques.

Coordination

The architecture is the framework for agile coordination between the development team and the acquisition of applications.

scope creep

All steering committees and project managers fear the scope creep in projects. A high level architecture eliminates the risk of scope creep.