TOP 10 architecture mistakes

Recently Gartner had a summit where the presented the top 10 of architecture mistakes

Scott Bittler, a research vice president at Gartner, says that “The key for enterprise architects is to create not the perfect or most elegant architecture for the moment, but the most adaptable architecture for the future. EA is a challenging discipline and careful attention to the basics can mean the difference between failure and success. Avoiding the pitfalls in the first place is much easier than climbing out of a hole you’ve inadvertently tumbled into. Applying the ways to avoid these pitfalls results in achieving EA benefits faster and reduced risk of programme failure. It will also improve the credibility of IT among business leaders”.

  1. The Wrong Lead Architect
  2. Insufficient Stakeholder Understanding and Support
  3. Not Engaging the Business People
  4. Doing Only Technical Domain-Level Architecture
  5. Doing Current-State EA First
  6. The EA Group Does Most of the Architecting
  7. Not Measuring and Not Communicating the Impact
  8. Architecting the ‘Boxes’ Only
  9. Not Establishing Effective EA Governance Early
  10. Not Spending Enough Time on Communications

I think these are big attention point when you come into a architect role. When looking at them more closely it comes down to communication, say what, why and how you are doing things (architecture). This covers point 2,3,7,9 and 10, 4,5,6 and 8 are about technical competences. So architects come out of you’re ivory tower and start communicating, i think communication is about 75% of the thing you have to do.

Think about a view point, they are there to communicate a solution to a stakeholder within his own context. The ultimate goal of architecture is to guide (communicate) how things should be made.

  1. No comments yet.
  1. No trackbacks yet.