HOW NOT TO FAIL IN EA: INTRODUCTION
HOW NOT TO FAIL IN EA: CONCEPT-CRITIQUE
The dangers of ‘term-hijack’
Magical-thinking and knowledge-management
The absurdity of belief
Intimations of hubris
Round in circles on enterprise-architecture
IT-centrism, business-centrism and business-architecture
Skills-shortages and ‘the market’
Showing my age, I guess…
The over-certainties of certification
On dubious definitions
“Who will lead us out of our uncertainty?”
If it’s not AE, it’s not EA
Efficient, effective, convenient?
“The history of enterprise architecture proves…”
Beware of ‘policy-based evidence’
- Implications for enterprise-architecture
John Zachman and the curate’s egg
Dump the BDAT-stack!
HOW NOT TO FAIL IN EA: METHOD-CRITIQUE
The autism of Enterprise Architecture?
Whuffie, currency and the ‘ready-fire-aim’ syndrome
How IT-centrism creeps into enterprise-architecture
Broken
Why broken?
A bit more broken
Unbreaking
- Conflict: Engineers versus scientists
- Conflict: Stability versus agility
Sometimes the small details do matter
The stench of systemic decay
Fail, to learn
Spot the difference
How architectures fail - 1: Architecture vs design
How architectures fail - 2: Scope of action
How architectures fail - 3: Constraints
Why ‘engineering the enterprise’ doesn’t work
Missing the point
Open Group, HERA and healthcare
- The good(ish)
- The bad(ish)
- The ugly (very)
- Real-world crosschecks