For past few weeks I have had the pleasure of working with Adrian (he is a Principle in Architecture and Strategy Team), during this time we have had numerous discussions about what should make an Enterprise Architecture. Surprisingly we have been in violent agreement all the time. He shares the same view as me EA is more that IT it should encompass all aspects of an organisation including manual tasks. Often when we focus too much on IT aspect is when we miss the flow on effects manual tasks have on IT dependent processes.
Adrian being more experienced than I am (having been Chief Architect for 3G at Vodafone in UK), has written a simple book on the EA framework that he has developed during his career. I would recommend it to anyone considering some light reading on the topic.
Book Details:
"An Enterprise Architecture Development Framework: The Business Case, Framework and Best Practices for Building Your Enterprise Architecture" : by Adrian Grigoriu
Link: http://www.amazon.com/gp/product/1412086655/sr=1-1/qid=1154835650/ref=sr_1_1/104-0229407-0975133?ie=UTF8&s=books
Tom,
ReplyDeleteI could not agree with you more. Sometime back reading Dana Bredemeyer's article on "What It Takes to Be a Great Enterprise Architect", one of the first works of Enterprise Architecture she talks about is US Constitution and how James Madison executed the role of an Enterprise Architect. Before there was IT Enterprises still existed and there was a blueprint or Architecture on how they worked.
In my opinion fundamental to what we do is how the business benefit get realises and in that what role does IT play. Instead of in an IT project searching for business benefits.
Thanks for your comments.
Dude, you should've called me! Firm offer stands anytime.
ReplyDeleteAhhh, cr*p ... posted on wrong entry, but you know what I meant.
ReplyDeleteNow I am confused, is that you brad?
ReplyDelete:-) ... yuppers. Was responding to "Some chages for the good in my life" post, but was reading the EA books post ...
ReplyDelete