Enterprise Architecture
Have you ever said to yourself...
My IT systems have become unmanageably complex and increasingly costly to maintain.
My IT systems are hindering the organization's ability to respond to current, and future, market conditions in a timely and cost-effective manner.
I have Mission-critical information that is consistently out-of-date and/or just plain wrong.
We have a culture of distrust between the business and technology sides of the organization.

These are just a few symptoms that indicate the need for a well-defined Enterprise Architecture.

But don't I already have an Enterprise Architecture?
Yes... every enterprise has an architecture; the difference is that some enterprises have an architecture that is planned, thought out, and deliberate while others have one that is random and haphazard. A well-defined Enterprise Architecture ensures a complete and consistent alignment between an organization's strategic objectives, mission, and business goals with its IT investment by taking into account four overarching organizational perspectives: Business, Data, Applications (Functionality), and Technology. Ultimately, such an Enterprise Architecture leads to an agile enterprise that can respond to changes in its business environment both proactively and with relative ease.

Just a few questions that I can help answer include:
How do I understand the current state, model the future state, perform a gap analysis, and establish a roadmap to take me from the “as-is” to the “to-be” state?
How do I establish a standard notation and consistent vocabulary to collect, document, maintain, and disseminate the information?
What is an Enterprise Architecture Framework (Zachman, TOGAF, etc.) and how can it help me design, implement, and regulate my enterprise architecture?
How am I affected by new legislation such as SOX?

<<Back to Skills and Benefits Continuum™