Enterprise Architecture Methodology -

InSemble Pragmatic Enterprise Architecture Methodology (IPEAM)

IPEAM was created based on our knowledge of frameworks such as TOGAF and Zachman and our experience as a member and as a solutions provider to several Enterprise Architecture Groups of Fortune 500 Customers.

The key guiding principles of IPEAM are:

  • Lightweight
  • Quick Time to Value
  • Adaptable

With IPEAM, we follow a methodology which comprises of several frameworks to:

  • Document Current State
  • Create a Target State
  • Define a road map to get to Target State

IPEAM also defines a simple EA maturity model that organizations can progress towards after the initial baseline.

EA Methodology

Though the methodology and the steps appear to be similar to any other framework, the similarity ends right there. With our methodology, Customers see business benefit at every step, thus do not have to complete the entire exercise to see any value.

IPEAM is pragmatic and can be tailored to each customer's environment. The frameworks being applied are simple but provide significant insight as views from multiple perspectives are incorporated. The customer is in control as they do not have to make a big commitment, which is the fundamental reason why most customers shy away from the established methodologies such as TOGAF and Zachman. IPEAM, instead of focusing on how to apply EA frameworks to an organization, partitions the scope into initiatives, executes on them and applies lessons learned to the following initiatives.

EA Methodology

The other key differentiator in our methodology is that as we spend more time with the customer we try to identify problems the customer has not even named yet. We surface and highlight these problems and thus IPEAM, instead of focusing of architectural artifacts, focuses on delivering tangible value to the business.