Understanding Business Context


As a part of the EA journey many different processes, methods and tools have been developed. One of the tools that was created was a matrix that illustrates the common requirements vision. This document encompasses four crucial things- business strategies of the enterprise, environmental factor impacts on the strategies, implications of the strategies and environmental factors on business process, information and technologies (see fig. 1 below). Bringing these vital pieces of information together in a format that allows for plan weaknesses to be seen prior to beginning implementation improves the likelihood of success. All components must be present in the array and be able to function without reducing any other components value or functionality within the matrix.

 In some organizations no matrix is made. The decision on what stakeholders to bring into the EA implementation process is based upon what a handful of people in leadership decisions determine to be appropriate. This puts the organization at a distinct disadvantage going into their EA journey. Typically possible issues with compatibility are able to be identified during the matrix completion. There will be much duplicated work and time lost when choosing to go this route. 

 Putting things into context prior to moving forward with an EA implementation is not required, but it might as well be viewed as a necessary function.
Image result for business anchor model

Fig. 1 Business Anchor Model
Source: https://www.slideshare.net/craigrmartin/digital-disruption-and

Comments

Post a Comment

Popular posts from this blog

Future-State Architecture: Conceptual Level

Building an EA program is not simply evaluating where your organization is and identifying how to put Band-Aids on your current state. A very large part of implementing an EA program is conception- perceiving what will be. An EA Architect must outline the future-state to create the roadmap that will be followed to get there. There are numerous items for consideration in the conceptual phase including principles, process patterns, process typologies, information patterns, application architecture, and data stewardship requirements.   In organizations that do not take the time to envision their future state and consider the elements within the conceptual phase there are typically very poorly implemented EA programs. At times organizations implement programs in haste out of necessity and this leads to inability to implement properly. My organization often implements in haste and runs into these types of issues and the product is not well known, well received or utilized well. The
Read more

IT Strategy

Image
Enterprise Architecture IT strategy is yet another area of the EA program that requires documentation. Document development is instrumental to the success of an EA program because it gives the structure and rules that are needed for the organization to follow. When developing the IT strategy document an organization must form the plan of action needed to reinforce and sustain the mission, strategy and objectives of the organization. Fig. 1- Support Image (http://www.okclipart.com/Support-Group-Clip-Art30jdhthnii/) The document is specific to the contributory efforts of the IT department and be relatively brief. To help with illustrating what will be done, there are change requirement matrix that can be developed. One axis will show IT strategies and business change requirements. The other axis will show enterprise business strategies. How the items listed on both axis relate to each other is denoted by a marking in the corresponding intersecting box. With the aid of this matrix
Read more

Future State Architecture: Logical Level

Image
There are levels to future state architecture. The logical level incorporates communication tools. The logical level is evident in more than just a specific area; it is seen over various business functions. The logical level supports strategy and therefore includes information flows to executive leadership, information architect and EA teams.  In the logical level of future state architecture the logical information flow the customer is at the center of the diagram. This is important to note because with the customer at the center, you ensure that the along with the information that needs to flow out from the customers the appropriate information comes to the customer as well. Being involved in the  EA process embeds the customer in the program and gives them the appropriate amount accountability.  Risk management and  satisfaction are managed through information flow. Proper updates go across banking, underwriting, credit reporting agency, fraud management, information security, m
Read more