Towards a whole-enterprise architecture standard – Summary

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is a brief summary of the previous six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise

Towards a whole-enterprise architecture standard – Worked-example

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is a follow-on to a six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise architecture: Introduction

Towards a whole-enterprise architecture standard – 6: Training

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is Part 6 of a six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise architecture: Introduction

Towards a whole-enterprise architecture standard – 5: Practices and toolsets

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is Part 5 of a six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise architecture: Introduction

Towards a whole-enterprise architecture standard – 4: Content

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is Part 4 of a six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise architecture: Introduction

Towards a whole-enterprise architecture standard – 3: Method

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is Part 3 of a six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise architecture: Introduction

Towards a whole-enterprise architecture standard – 2: Core

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. This is Part 2 of a six-part series on proposals towards an enterprise-architecture framework and standard for whole-of-enterprise architecture:

Towards a whole-enterprise architecture standard – 1: Introduction

For a viable enterprise ­architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. What we need now are tools and techniques that can extend all the way out to

The role and rise of the business-anarchist

You may have noticed some new role-titles turning up in the enterprise space. Chief Disruption Officer, for example. Or Chief Transformation Officer. A fair few variants on that theme. But what you probably won’t see – not as yet, anyway

Making a knowledge-base for whole-enterprise EA more accessible

I have a problem. One that might be relevant for you too, if you work in enterprise-architecture or related disciplines. Here’s the situation: I have here this weblog on enterprise architecture and suchlike, built up out of almost a decade of

Dump the BDAT-stack!

For a viable enterprise-architecture [EA], now and into the future, we need frameworks, methods and tools that can support the EA discipline’s needs. Yet there’s one element common to most of the current mainstream EA-frameworks and notations – such as

Architecture as boxes, lines and glue

What do architects do? And why? At this point we’d usually reach out for some apposite metaphor… And yes, by far the most common metaphor is ‘boxes and lines’, or ‘boxes and arrows’. If we take the most stereotyped, ‘boxy’ view