• English
  • Nederlands
HOME
SEARCH
CONTACT
NEWSLETTER
 
 
 
CONTENT
About us
Call for contribution
Contributions
The CIO talks
Proceedings
Blogs
Master thesis
Forum
Wiki
Events calendar
Links
Login/Register
advertisements
Zoek je een baan?
Zoek je hulp?
Zoek je een opleiding?
Zoek je een boek?
Zoek je een tool?












 
 
BLOGS
Enterprise Architecture Roadblocks, before you start
Adrian   
Friday, 27 June 2008
There are roadblocks all along the development lifecycle of an Enterprise Architecture, even before the effort starts. Would people accept it?

The Enterprise Architecture (and SOA) demands change. People have to be prepared in advance to see the benefits. So change management must be thought before you commence.

Your Enterprise, like many other, may suffer from cultural inertia; that is, it is hard to kick off any initiate and afterwards it is often hard enough to stop the development, as well.

Also, like in many other Enterprises, the thinking and especially the acting is predominantly tactical. Strategy is always an afterthought if there is time or resources left for it. And EA is about strategic planning. As such, it collides with the short term thinking in your Enterprise.

Does your company suffer from a silo organization? If yes, which is not uncommon, then you have a problem since nobody is disposed to make sacrifices for the greater good.

The existing divide between Business and IT makes the cross boundary communication and collaboration already difficult and you already know it. Should you try to talk to the business about Enterprise Architecture?



This is continued as a series of blogs on EA roadblocks.




Be the first to write a comment
RSS comments

Only registered users can write comments.
Please login or register.




Share / deel
Del.icio.us!Google!Technorati!Yahoo!
 

Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not permitted. Readers are requested to notify This e-mail address is being protected from spam bots, you need JavaScript enabled to view it of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.
feed image
ISSN: 1877-2994