Intimations of arrogance? – an addendum

Carrying on from the previous post, with a bit of an explanation about why I’m becoming so much of ‘a grumpy old guy’… Here’s the blunt fact: I’m not a good thinker. I know that. Too many gaps in my knowledge,

SASSY Architecture

SASSY Architecture is a practice of combining two seemingly incompatible paradigms. The first one is based on non-contradiction and supports the vision for an ACE enterprise (Agile, Coherent, Efficient), through 3E enterprise descriptions (Expressive, Extensible, Executable), achieving “3 for the price of 1”: Enterprise Architecture, Governance, and Data Integration. The second is based on self-reference […]

Intimations of arrogance from a grumpy old guy?

Okay, I admit it: I’m at real risk right now of becoming a grumpy old guy: Getting snappy at people on LinkedIn and all that. More than a fair bit of that phrase about “Will not suffer fools gladly”. Patience strained

“Enterprise Architecture As A Service” – How – REACH for the STARS

In two prior blogs, I described why “Enterprise Architecture As A Service” (EA As A Service) would be a good thing and what it might look like.

Why? Because a properly implemented service delivery model would put the emphasis in more appropriate places:

Production and use value versus EA as a deliverable
Timely value along the way versus at the end
Clear expectations versus vague promise
Support and enablement versus ivory tower compliance
What? A portfolio of services provided on demand in service categories:

Planning Services to scope based on need
Buy-in/collaboration Services to ensure the right people in the organization are engaged
Development Services to build the right parts of an EA at the right time
Management Services to ensure that the EA efforts delivers value consistently
Usage Services to derive value from the EA
Decision Support Services to support Portfolio Governance decisions

Building effectiveness in a small business

One of the great things about doing my ‘Tetradian on Architectures‘ mini-video series is that I get to tackle real-world questions about everyday enterprise-architecture, sent in by people all around the world. In this case, for the current episode in

“Enterprise Architecture As A Service” – What

In my previous blog, I described why “Enterprise Architecture As A Service” (EA As A Service) would be a good thing. Fundamentally because a properly implemented service delivery model would put the emphasis in more appropriate places:

– Production and use value versus EA as a deliverable
– Timely value along the way versus at the end
– Clear expectations versus vague promise
– Support and enablement versus ivory tower compliance