EA Governance


What in the world is EA governance you may ask. The term governance as explained by The Business Dictionary means “establishment of policies, and continuous monitoring of their proper implementation, by the members of the governing body of an organization”. Well this is also true in the world of enterprise architecture. Governance is a key component to the EA process. Governance is not limited to policies and observation, it is also inclusive of activities that the organization performs so that efforts are supported by measures of culpability.
Think of EA as a great big trip. You have your Enterprise Roadmap for how to get from point A to B. Typically you don’t take trips without travel insurance, so why go in your EA journey without it? Governance as the protection plan for your EA journey. Those policies and monitoring provide checks and balances throughout the process.


With EA being such an intricate program, there are inherent pitfalls that come with implementation. Taking the time to invest in governance allows organizations to keep the EA team members, leadership and organization as a whole accountable. If for any reason your organization thinks that this step can be skipped because it is easy enough to address something when it comes up, they are sadly mistaken. Take heed and ensure that governance not an afterthought in your company’s EA program implementation by doing 2 key things.

1       Assemble an Architecture Review Board (ARB) to be the ones to make definitive decisions regarding the EA program. Who is supposed to approve the policies, methods of monitoring, changes to the program and/or content? Identify individuals who are:
·       Knowledgable about EA
·       Interested in participating
·       Have some hands-on role, but can be impartial
·       Willing to own missteps
·       Forward thinking/innovative
·       Problem solvers
2       Develop those critical artifacts such as policies and monitoring protocols as both a security net and a backbone. Know that the policies cannot simply be guidelines and flex as needed. These need to be well thought out so that they can provide the program support needed.

Reference:
The Business Dictionary http://www.businessdictionary.com/definition/governance.html

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