By Topic

Top 10 architecture land mines [enterprise]

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)

IT professionals hear plenty of advice regarding enterprise architecture. Although good in theory, many of the recommendations are impractical because they are time-consuming or just plain difficult. People and organizations tend to repeat common mistakes that make a mess of their enterprise architecture. The implications of these mistakes are not immediately apparent. By the time you take corrective actions, it is often too late to undo the direct damage, much less the collateral damage. Rather than offering recipes for success, this article points out the top 10 list of land mines along the architecture roadway. The list are as follows: declaring the architecture effort done; assuming that technical people make good architects; saying no; failing to communicate early and often; speaking in tongues; mistaking standards for architecture; forgetting to assess people and process impacts; aligning (and realigning) with strategies, rather than with business goals and cultural values; crashing the party when you are not invited; and introducing technology before its time. The correct measure of success is not how fast you can introduce a new technology. Instead, it is whether you can make the correct or appropriate investment decision. Avoiding the 10 pitfalls will not guarantee your architecture program's success, but will certainly increase your profitability of avoiding failure.

Published in:

IT Professional  (Volume:5 ,  Issue: 6 )