Enterprise Architecture Body of Knowledge
Managing an EA


Many functions need to be performed across the EA program, such as drafting strategies, setting up and running board meetings, supervising teams, acquiring tools and personnel resources, conducting engineering trade-off analysis, and collecting and analyzing data on EA outcomes. To ensure a successful EA, organizations should have a clear understanding of the key functional roles, interrelationships, and types of communication necessary to complete the development and maintenance of the EA over time (CIO Council, 2001).

It's important that key roles be identified early in the EA program, and that those roles be re-assessed as the program evolves and conditions change. Responsibilities associated with roles should be clearly defined, including activities to be performed, personnel skills and qualifications, product development responsibilities, and quality/timeliness expectations. As the EA program is rolled out, personnel need to be assigned to the various roles, and their performance needs to be monitored and assessed.

This topic area offers guidance, case studies, and other references that help EA practitioners identify the types of roles needed within their organization to develop a successful EA program.

Reference: Chief Information Officer (CIO) Council. A Practical Guide to Federal Enterprise Architecture. Version 1.0, February 2001

We are soliciting content in this topic area. If you are an expert in this enterprise architecture domain please consider participating. To inquire about this topic area contact us today.

Managing an EA