What is the enterprise in ‘the enterprise’?

When we talk about enterprise-architecture, what is ‘the enterprise’? For that matter, what is ‘enterprise’? Seems they’d be fairly foundational questions, yet most of the answers we see seem, well, kinda thin… If we hunt around on the net, we’ll find plenty of definitions for ‘enterprise’: “a business venture”, “a project or undertaking, typically one […]

Six Reasons Why EA Should NOT be Assigned to the IT Department

Elements of Style

This is such a poignant post that I felt compelled to repost it here.  In a Linked in blog post by: Pallab Saha, he clearly positions why EA is a superset of IT architecture and why the two need to be kept separate.  I am reminded of my study of Strunk and White’s The Elements of Style – the classic treatise on clarity and brevity of written expression.  Pallab nailed it in these collection of key points:

Six Reasons Why EA Should NOT be Assigned to the IT Department

6. EA ≠ IT Architecture

5. True EA leads to redistribution of authority, which is beyond CIO jurisdiction.

4. EA value proposition (i.e. standardization vs. innovation) is solely business realizable.

3. The primary goal of EA is to build coherent enterprises, not better IT systems.

2. Synthesis takes precedence over analysis.

1. EA failure is an organization failure, not an IT failure.

A week in Tweets: 24-30 July 2011

It’s another week. Which means another (slightly-delayed) week’s-worth of Tweets and links. Usual categories, usual ‘Read more…’ link: Enterprise-architecture, business-strategy and all the business-big-picture stuff: jdevoo: How to set sustainability goals http://j.mp/qb6WX0 >> applying SMART principles #entarch jdevoo: Designing a sustainability dashboard? Modeling is not optional http://j.mp/p7PQA8 #entarch greblhad: Anyone has input on using  http://ideascale.com/ […]

Enterprise-architecture? – it’s all about story

Enterprise-architecture is all about story. The enterprise itself is a story; but the practice of enterprise-architecture is all about stories too. Let me tell you a story… There once was this half-crazed guy who used to go on about an even crazier idea that there might be a bit more to enterprise-architecture than just, well, […]

Four Rules of Engagement

You know how it is, you say stuff and you don’t expect it have any effect because you’ve said it over and over and no one’s listening. Well, did I get a surprise! Catching up with a couple of guys I’d done a project with quite some time back one of them ambushed with my […]

A week in Tweets: 17-23 July 2011

Catch-up time again, with another (somewhat delayed) week’s-worth of Tweets and links. Usual sort-of-categories in the usual sort-of way, with the usual no-quite-sort-of ‘Read more…’ link first: Business-oriented ‘big-picture’ stuff – enterprise-architecture, innovation, business-models, that kind of thing: unorder: New post – No fun at work: values in action http://is.gd/MIMMA4 >oops… espoused vs enacted values… […]

Cloud Talk with Dave Linthicum: Top Stories for July

This morning, Dave and I exchanged top cloud computing stories for July.  During the podcast, we nominated mutual friend Lori MacVittie of F5 to be the official arbitrator of “cloud / not cloud” labeling.  We were inspired by Gartner’s July Cloud Computing Hype Cycle, in which everything is suddenly cloud.  Perhaps we need a #snark warning for parts of this podcast.  Give it a listen.

Related posts:

  1. Cloud Talk with Dave and Bill: Top Stories for May
  2. Chattin’ with Dave Linthicum – Top Cloud Computing Stories for 2010
  3. On David Linthicum’s Cloud Computing Podcast: Top 3 Stories for October

Two kinds of Why

What is ‘Why?’ And why, anyway? “Oh no, not again“, do I hear you cry? Actually, it’s not as bad as that: it’s not going to be yet another of those long tedious technical posts – honest! (It is a sort-of technical question, I’ll admit. And, in the event, quite long. But interesting to just […]

Basics of consolidation

Nothing new, just a reminder of how-to… There is perhaps nothing new in this post, still it may remind us of the fact that continuous improvement cycles should not stop. Five basic codes of conduct when doing consolidation Be inclusive – As you take inventory gather as much data as possible. Don’t be hampered by […]

Unravelling the anatomy of Archimate

The Archimate notation aims to be the standard to be used by everyone in enterprise-architecture and related fields. But what exactly is its anatomy – its underlying structure? And if it’s aimed at enterprise-architecture, what is it about that structure that makes it seem only to support IT-architecture, and in such an awkwardly IT-centric way?
(Apologies, folks, […]