Pragmatic Enterprise Architecture

Friday, August 24, 2007

So Many Frameworks So Little Time

By now you have sold your Enterprise Architecture (EA) program to your CXO. The next step is determining which EA framework to use.

A few examples of these frameworks are: Open Group Architecture Framework (TOGAF), Federal Enterprise Architecture Framework (FEAF), National Association of Chief Information Officers (NASCIO) Framework, The Gartner Enterprise Architecture Framework, and the Zachman Framework.

Not All Frameworks Are Created Equal

Unfortunately none of these frameworks are complete; however, each have their strong points. For example, if you are a federal government agency, your best option would be FEAF just as NASCIO would be most appropriate for state government.

As an Enterprise Architect or an aspiring one, you must become intimate with these frameworks and your business in order to choose the right one. Identify the quick wins or low hanging fruits in your organization and then match the framework that best addresses those.

Once you have chosen a framework, you are one step closer to framing your organization.

Pragmatic Advice

  • Develop a list of your organization’s most troublesome areas or those which need addressed immediately. Think quick wins.
  • Compare that list to your existing EA framework research.
  • Seek peer advice when making your decision. For example, the Open Group has several Enterprise Architecture groups throughout the country or starts your own.
  • Choose your framework and start your planning.

Labels:

Thursday, August 16, 2007

Enterprise Architect: Why do you need one?

This is a very good article from CIO magazine about the Enterprise Architect role:

http://www.cio.com/article/127751/Enterprise_Architect

Labels: , , , ,

Saturday, August 11, 2007

Educate then sell the Value!

You must sell your CXO on the Enterprise Architecture (EA) program before you begin. Before you can sell your CXO on EA, you must educate him/her on the value of EA.

Don’t use the fancy definitions that don’t make sense.

Don’t use fancy definitions when explaining EA. If you don’t catch your CXO’s attention in the first few sentences, then you’re not likely to sell him/her. Educate on the value.

Don’t try to explain the divisions of EA. Focus on the value.

Don’t waste time trying to explain the divisions between your Business, Information, and Technology Architectures. Instead focus on educating your CXO on the value of EA. Value statements could be as follows:

- Common future vision shared by the business and information technology group.
- Support the business through improved information sharing.

- EA provides guidance in business driven information technology solutions.

- EA provides a way to manage complexities of a large IT shop by setting enterprise-wide IT standards.

- Assurance to the business and customers that new IT systems are implemented through a consistent and measurable process.

Guilt always helps.

Make your CXO feel as if he/she is behind the curve. Several large organizations such as Intel, Microsoft, and BP practice EA. In addition, several federal agencies and state government agencies practice EA as well. By referencing other high-performing companies, you can instill the fact that practicing EA can create strategic value for your organization.

In the end, your EA program will never be successful unless your CXO has full buy-in. As you begin your EA Program, you’ll need you CXO’s credibility and backing to implement many of your new governance practices and EA processes. Without support, your EA program will never get off the ground.

Pragmatic Advice

  • Create an EA presentation that is no longer than five slides.
  • Get time on your CXO’s calendar (ask your boss to help).
  • Memorize your presentation.
  • Make sure you know enough to answer any high-level or detailed question your CXO may ask. Practice, Practice, Practice.
  • Remember you are now your company’s EA expert!

Labels: ,

Getting Started

Welcome to my Enterprise Architecture blog. The intent of this blog is to share my experiences in starting an Enterprise Architecture program from scratch.

Step 1: Commission an Enterprise Architecture Program
Step 2: ??????
Step 3: Profit

This blog focuses on Step 2.

Labels: