A charter is a vital deliverable for any EA start-up process. It sets out explicitly what EA is and what it can do for the organization, specifying these clearly within the organization's current culture and level of EA maturity. The charter can help reduce political friction, allowing management, stakeholders and peer groups to understand the role of EA and how it will be delivered in the organization. Having a charter that clearly defines the value proposition of EA and describes how it operates can be very useful in educating IT and business leaders about what EA is and how the team works.
The charter should be created at the beginning of your practice and revised at the beginning of each architecture iteration or project engagement. Revisions at regular intervals will ensure that the definition, function, and scope described in the charter are still accurate as your practice matures and your organization's needs change.
Referring to one of the templates or samples below will give you a good start on a first draft. Make sure that the scope of the practice described in your charter is challenging and of true value to your organization, but not overly ambitious at first; failure to reach clearly stated and formally approved goals would be too great a set-back. Make sure also that your charter is written in the language of your stakeholders, not in architect-speak. It must reflect the local culture and politics of your organization and communicate clearly both within your team and throughout the organization. Circulate the draft among your key stakeholders for comments and corrections to make sure it represents a shared understanding of your practice's mission, goals, structure, and scope. The final, revised version should then be formally approved by the governing body or executive sponsoring your practice.
The following two examples are taken from the readings referred to below. The first, from the Gartner Group, results in a substantial document of 10-20 pages and is meant for annual review. The second, from a book published by Springer, results in a "vision statement" of 3-5 pages and is intended to be written as a first step in every architectural engagement.
Panel |
---|
Gartner example (1):Preface:
Objectives and Metrics:
Scope:
Governance and Assurance:
Roles and Responsibilities:Role definitions and responsibilities may be expressly stated for various groups:
Related Process Integration:How the EA program may connect to and interact with various processes is described, including these processes:
Deliverables:The deliverables of the EA team and other groups related to EA, and their specific alignment with the identified target business outcomes to be addressed. Communications:The communications activities of the EA team.
|
Panel |
---|
Springer example (2):Reason:The business-driven motivation for developing an architecture.
Purpose:How the architecture will be used to address the business-driven motivation.
Definition:An explicit definition of what the organization considers enterprise architecture to be.
Services:A catalog of the specific services offered by the architecture group.
Organization:The structuring of the architect's role in the organization or engagement.
|
(1) An Enterprise Architecture Charter is a Basic Requirement for All Maturity Levels, Chris Wilson, Gartner Research, 15 October 2012
(2) Building an Enterprise Architecture Practice, Tools, Tips, Best Practices, Ready-to-Use Insights, Martin Van Den Berg and Marlies Van Steenbergen, Springer, 2006
(3) Why Write an Enterprise Architecture Charter?, Bard Papegaanij et al, Gartner Research, 18 February 2011
Attachments | ||
---|---|---|
|