Most organizations that claim to have an “enterprise” architecture practice are really only doing “IT” architecture (ITA). What leads us to say that? Our research shows that most organizations have limited their scope to include only IT elements like infrastructure, data and applications. That’s OK in and of itself and it is a step up for many organizations, but that’s not EA.
Now that everyone is back from the holidays, relaxed and enthusiastic, it is a good time to take a look forward and update your EA program’s objectives for the new year. In our experience, most organizations have a very short window to accomplish this. It doesn’t take long before the enthusiasm and vision for the future is replaced by the urgency and narrowness of the day.
Most current discussions on EA Maturity focus on backward-looking metrics and score them based on levels that are similar to the Capability Maturity Model (CMM) process improvement system developed by the Systems Engineering Institute at Carnegie Mellon University. Over the past several years we have started to develop a different opinion about using CMM-type assessments for enterprise architecture processes.
“Enterprise Architecture (EA) is an immature discipline and possibly getting even more immature. As the scope of EA extends beyond the areas that IT-centric efforts are prepared for (data, app, infrastructure), the competency, credibility and effectiveness of an EA team may decrease. However, there are a variety of ways to increase these characteristics for EA … Read more
Recently, we have discussed the HL classes for Business Archtiecture (functions, processes, services) and Application Architecture (application classes and platforms) and Technology Architecture (domains and components). Now let’s turn to Information Architecture, not Data Architecture. In order to get started with Information Architecture, you need to identify all of the major “things” that your business … Read more
Enterprise Architecture as long been considered a planning discipline. Many times when asked about the value of EA, people will comment with the old axiom, “What is the value of a plan?” While there is certainly some inherent value in the artifacts, processes, and relationships developed by EA in and of themselves, the real benefits … Read more
“Enterprise Architecture (EA) is an immature discipline and possibly getting even more immature. As the scope of EA extends beyond the areas that IT-centric efforts are prepared for (data, app, infrastructure), the competency, credibility and effectiveness of an EA team may decrease. However, there are a variety of ways to increase these characteristics for EA … Read more
Although the word “marketing” can elicit negative thoughts in the mind of a technologist, it is a necessary consideration for any EA program in order to maximize its impact on the business and establish an environment for continued contributions. George Paras will present on this topic and lead an interactive discussion at the November meeting of … Read more