This is a partial preview of the document found here: https://flevy.com/browse/business-document/enterprise-architecture-management-plan-37 Description: A management plan of 12 steps that could be used in inpmementing enterprise architecture for any type or size of company.

1. Enterprise Architecture Management Plan
By John Kyriazoglou* (author’s credentials at the end of this document)
An enterprise architecture (EA) is a conceptual approach that assists organizations with the
understanding of their own structure and the way they work. It provides a map of the enterprise
and is a route planner for business and technology change. Normally an enterprise architecture
takes the form of a comprehensive set of cohesive models that describe the structure and the
functions of your company.
When you implement enterprise architecture for your company on the basis of a disciplined
approach suited to your specific needs and requirements (e.g., analysis of requirements, design of
EA components, development of EA constituent software parts, linking IT systems to business
functions, etc.), you are bound to have several benefits, such as:
1. Better alignment of your business strategy with IT systems
2. Better control of business data and faster flow of information
3. A more efficient IT operation fully supporting your business
4. Better return on existing IT investments and systems development projects
5. Reduced business risk associated with IT operations
6. Increased business effectiveness and efficiency
7. Reduced operational risks in all business functions.
This can only be achieved in an organized, systematic, effective and efficient manner by a
enterprise architecture (EA) management plan. This is presented next.
Step 1. EA Preliminary Study: Carry out a requirements analysis and prepare a feasibility
study that includes a list of EA demands and expectations, focusing on critical areas of business
processes, information and data, and technology.
Step 2. EA Organization: Form an Enterprise Architecture (EA) Team by selecting an EA
coordinator and the other required EA and support staff, and appointing them on a formal basis,
and with a charter and specific time-table, budget and responsibilities.
Step 3. EA Users: Identify senior business and IT (technical) executives to gather knowledge
about the strategic and operational needs and requirements of the organization.
Step 4. EA Communication: Devise and execute communication plan with relevant methods,
tools and services.
Step 5. EA Demands Documentation: Review and document EA demands and expectations,
focusing on critical areas of business processes, information and data, and technology.

2. John Kyriazoglou: author’s credentials
John Kyriazoglou (jkyriazoglou@hotmail.com)
John Kyriazoglou, CICA, B.A (Hon-University of Toronto),
International IT and Management Consultant (with over 35 years of experience),
Editor-in-Chief for the Internal Controls Magazine, www.theiic.org
Author of several books:
(1) ‘IT Strategic and Operational Controls’, Publisher: www.itgovernance.co.uk
Direct Link: http://www.itgovernance.co.uk/products/3066
(2) ‘Addendum to IT Strategic & Operational Controls’
Direct Link: www.itgovernance.co.uk/products/3143
(3) ‘Corporate Strategic and Operational Controls’, Publisher: www.theiic.org
with Dr. F. Nasuti and Dr. C. Kyriazoglou.
Direct Link: http://www.theiic.org/publicationsbookstore/bookstore2.html
(4) ‘Implementing Management Controls for Small and Medium-Size Companies’
AMAZON Kindle Books:www.amazon.com
Direct Link: http://www.amazon.com/dp/B007Z1WTOM
(5) ‘Pearls of Wisdom of the 7 Sages of Ancient Greece’
AMAZON Kindle Books:www.amazon.com
Direct Link: http://www.amazon.com/dp/B007YNPR8Q
Profile (1): http://www.linkedin.com/pub/john-kyriazoglou/0/9b/919
Profile (2) http://www.managementexchange.com/users/nwstdt9cyq
Blog: http://businessmanagementcontrols.blogspot.com/
SSRN Free Publications: http://ssrn.com/author=1315434