There are two key maturity
level indicators to analyze first when attempting to establish an Enterprise Architecture
program in an organization:
The first is the maturity
level of the organization with respect to project and program management. If an
organization is not very capable in managing projects and programs, they will similarly
not be able to manage the potential change outcomes of an Enterprise Architecture
program.
The second maturity level to
note is the architecture design, development and capture in both the business
and technology realms. If an organization does not capture its architecture for
reuse or for referenceable knowledge, then the outcomes of an Enterprise
Architecture program, which sometimes produces MORE abstract material then just
pure architecture, will not be consumable. An organization has to have the
ability to architect projects first before embarking on architecting the enterprise
– similar to walking before running.

No comments:
Post a Comment