www.flickr.com
This is a Flickr badge showing public photos and videos from Chief Architect. Make your own badge here.

Search ...

Powered by Squarespace
« Building enterprise architecture the right way | Main | Enterprise Solution Architecture Decision Making »
Friday
Sep042009

Enterprise Architecture Pitfalls

Brenda Michelson has put together a good summary of the recent Tweets following Gartner’s recent listing of EA pitfalls. 

The EA community seems to have come to the conclusion that Gartner has stated the obvious.  The Tweets have provided “real” EA pitfalls based on the experience of practitioners.

If you read the blogs of the community of practitioners then you will find not only the pitfalls but the solutions to them.  These solutions have been discovered through the sweat and tears of those who have been there, made the mistakes, and got the scars.

The Twitterverse and Blogosphere has enfranchised the “doers” who previously didn’t have a voice.  But more importantly, the current generation of decision makers and key influencers understand the value of the information that is out there and freely available.

If you read the blogs, you won’t get a neatly package “answer” to your problems.  But you will, after some time and effort, get insight.   You will have to work out for yourself what is relevant and what is not. You will have to work a little harder to get to a plan to take your organization further.  But you will learn, and you may just have a plan that can deliver meaningful results.

The criticism of the identification of EA pitfalls follows very close behind similar criticism by the EA community of Tweeters of “Emergent Architecture”.

The analysts need to demonstrate that they talking to the right people, that they are gathering the right information and finding genuine insights based on the experience of practitioners.  If they can deliver better results quicker and cheaper than doing it yourself then they will have a valuable offering.  The recent Twitter discussions suggest that they are behind the curve.

The analysts must engage and embrace those that do and know.  If they don’t then I suspect any deficiencies in their offerings will continue to be highlighted.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments (2)

I was involved in the twitter conversation on this matter, and have to agree with the overall sentiments. There is little or no value in a list of reasons for failure or things that are wrong, as these lists are generally uninformative, obvious, and potentially infinite in length. More useful are reports on how things should be done, rathen than how they should not.

Regards
The Enterprising Arcihitect
http://theenterprisingarchitect.blogspot.com

September 10, 2009 | Unregistered CommenterJon Ayre

Interesting article. Its good to know about it.

February 26, 2010 | Unregistered Commentermonicauk

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>