In general, you can’t manage, what you don’t measure.
In User-centric EA, we measure both program and product metrics.
- Program metrics—measures of the major program areas in EA; these include development, maintenance, and use of architecture products and governance services. Examples of program measures includes: information products developed per time period, total information products under maintenance (‘the maintenance burden’), and under usage—EA system reviews conducted at the agency, Product and Standard reviews conducted at the agency, end-user information requests fulfilled, departmental decision requests supported, external data call responded to, EA website hits, and so on.
- Product metrics—measures of the amount of data (functions, information objects, systems, technologies, etc.) and their attributes in the EA products and repository; this is used to understand that breadth and depth of the architecture information being provided to end-users and to ensure that it is the ‘right’ information in terms of its scope to enhance decision-making. Additionally, the product measures help understand the general complexity of the information areas, and the challenge of maintaining them and keeping them relevant in terms of currency, accuracy, and completeness.
No comments:
Post a Comment