Episode 81: Demise of Enterprise Architecture
Have you lately looked at job adds? If so you will see that there is less demand for enterprise architects. Why could that be?
Well I will try to tell you some of the pitfalls of enterprise architecture and how they can be avoided, but it really boils down to the fact that we as enterprise architects have not succeeded in one of our main tasks and that is to reduce costs and improve time of delivery. Actually some studies show that building up enterprise architecture groups have dramatically heightened costs and made deliveries of projects 60 % longer on average.
So will discuss some problematic areas (there are many more) more in details such as:
Reuse, Skills of EA, Frameworks, Message hubs, ESB or however you want to call it.
Neatness or clean is not cheap.
Missing TCO
Effectiveness Standardisation
If you do not like rants I properly suggest that you skip this one.
Cay Hasselmann
Anyone knows a sponsor for this show? Could you please contact me at cay@accent.li. Thanks
Standard Podcasts [ 17:11m]: Play Now | Play in Popup | Download | Embeddable Player | Hits (117)| Rate it: |
 Email it
|
2 Comments »
RSS feed for comments on this post. TrackBack URI
Leave a comment
| ||
Recent Posts
- Episode 84: The Enterprise Architecture life cycle – Part 3
- Technical problems
- Episode 83: The Enterprise Architecture life cycle – Part 2
- Episode 82: The Enterprise Architecture life cycle – Part 1
- Episode 81: Demise of Enterprise Architecture
- Episode 80: NAC - A critical EA view
- Episode 79: The dream of the paper less office
- Episode 78: CRM- A critical EA view Part 3
- Episode 77: CRM- A critical EA view Part 2
- Episode 76: CRM- A critical EA view Part 1
Hi Cay,
so, if I get you right, your opinion is that the market for EAs is really declining because of the bad or unsatisfied experiences of CxOs on their EA-initiatives concerning generating more costs than saving costs, extending time-2-market timelines rather than shortening them, correct?
Where do you think is EA located on its “lifecycle”? Just a hype of the recent years? Desillusion-phase now? Or maybe just consolidating and gaining growth afterwards? Is it worthwhile for one’s personal growth / career to move from project solution architecture to EA?
Comment by Bernd Albersmann — November 14, 2009 @ 3:39 pm
Bernd,
the whole part just shows that it is not good enough to call yourself EA and to know about theoretical concepts. You need to know knowledge about about all the different parts such as to work in business architecture and spot a standard business process, to know about best practices in solotion and infrastructure and to then transition anyt architecture into a robust service management, further to reduce costs and risks, shortening time of delivery. If this knowledge and experience is not delivered you could just hire some graduate and call him EA, as many consultancy have done. So EA will in future be judged more on its merrits and less on the title and status.
Hope this helps.
Cay
Comment by cea — November 14, 2009 @ 7:13 pm