concept of enterprise architecture is dealt with properly, the average
duration of anticipative projects will shorten, as use can be made
increasingly of the already implemented architecture. As more work is
carried out according to the architecture, lasting satisfaction with the
IT solutions should increase and development costs should drop.
Efficiency is measured, among other things, by the speed with which
enterprise architectures and project-start architectures are set up and build-
ing permits are issued. The care with which this is done (the number of
required adjustments afterward) is also indicative of an efficient process.
Development with Architecture
The Development with Architecture process is intended to create IT
solutions with a high anticipatory content that fit in with the informa-
tion system as a whole.
The KPIs for Development with Architecture are shown in Exhibit 8.4.
190
Dynamic Enterprise Architecture
Effectiveness
Efficiency
· Degree to which standards and
templates are used.
· Number of coordination sessions
with other projects.
· Satisfaction with the project result
of the anticipative projects after
two years.
· Average time spent on making
adjustments in applications,
classified by strategy.
· Percentage of maintenance effort
resulting from adjustments in
other applications.
· Percentage of building permits
that are refused.
· Percentage of building permits
that are revoked.
EXHIBIT 8.4
KPIs of Development with Architecture
The anticipative strategy strives to produce an IT solution that is
prepared for the future, whatever that future may look like. Whether
c08_wagter.qxd 12/10/04 12:29 PM Page 190