EA 872 Week10: Simplifying EA Modeling

One of the main challenges perceived by enterprises and different teams about EA is the amount of documentation associated with the practice, and the time and effort usually spent on producing the artifacts. While it is true that producing documentation is not avoidable, a successful EA implementation will take the simplified approach of producing limited number of pages or slides per domain and thus set limits and provides framework for the EA modeling strategy.

For example, taking the approach recommended by Gartner on EA Modeling Made Simple, producing one slide high level conceptual views on each of the current state, future state, gap analysis and migration plan, is definitely a recommended method to view a complete EA strategy for the area of focus. The one slide approach per topic helps prioritize the efforts on defining the EA documentation deliverables in the early phases of EA kickoff as something that needs to be delivered in a short period of time and as a first iteration of the key elements of change needed within that area. Producing multiple iterations of a one slide is an easier process during review meetings (vs. a documentation with large number of pages). Having everything, at a high level, on one slide helps focusing the attention and priority on the important items that need change and is a perfect segway for a brief and to the point gap analysis illustration. Additionally, this approach leaves the complex graphs and diagrams as add-ons or appendixes to the EA model, while the main effort of the team is focused on the summarized slides. Having the migration plan on one slide is another strength of this approach where it can be used as reference during conversations, and concentrates effort on how the projects will adhere and accelerate (if any) the migration plan.

In summary, simplifying the EA modeling exercise by mainly listing a one slide high level of each of the current state, future state, gap analysis and migration plan is a highly recommended approach to defining an EA model and should be considered by all EA teams at the time of EA activities kickoff. At the simplest level, it helps to eradicate the facade of heavy documentation efforts typical of EA teams, and helps to assure the different teams in the enterprise that the approach will be one of speed, agility and concise effort.

References:

"EA Modeling Made Simple: ETA Domain Strategy Example". Bruce Robertson. (Gartner, Dec 2006)