The need for an EA charter is debated somewhat due to either the perceived nature of the charter document as a tactical project document or the amount of time that is required to do more than a cursory job of creating an organizational document. Our experience has been that not only is there value in … Read more FAQ – Is there really a need for an EA Charter?
In a word, no. There are always exceptions, of course, but it is in the best interests of the organization, and of the EA Team, that the EA Team be free to make objective future state recommendations in the context of a longer-term horizon. The organization’s leadership team should then approve those recommendations through an … Read more FAQ – Should the EA Team also be the EA Police?
Simply telling a business audience all the wonderful things that EA will do for you is not enough. Light bulbs go on only when you have a chance to show them what it means to them. So, don’t try to “sell” an audience on the academic virtues of EA. Show them. Use relationships among component parts and expose mappings that they always thought existed, but never quite had a chance to see before.
Lately, there has been a lot of focus on business architecture within the EA community. We would like to expand the thinking of business architecture to include the element of information. Traditionally the focus of many IT shops has been in the delivery and enhancement of information systems that automated manual business processes. However, over time, … Read more True-IA? A True-EA Perspective for Information Architecture
In this next podcast in the “EA Rediscovered” series we will address various organizational models for Solutions Architects. Should they report directly to a centralized EA team, provisioned as needed to guide project designs? Should they report directly to development group leaders and be permanently resident in those communities? We are asked this question on an almost daily … Read more EA Rediscovered – Solutions Architects
I was recently asked to reflect on the strengths of some of the EA practitioners I have worked with over the years. They have been an inspiring group who collectively and individually were drawn to EA because they aspired to make a difference in their companies. Fulfilling that aspiration isn’t always an easy path.
Through ten years of working with dozens of companies, we have seen a lot of good and some not so good developments related to Enterprise Architecture. In recognition of those 10 years, those dozens of companies, and continued success, we would like to share them with you.
Of the many reasons to have EA as part your company’s approach to decision-making, the one that is most often overlooked is that it will save you TIME. Saving time means moving forward faster.