Information Technology Reference
In-Depth Information
new architectural format. Existing skill sets and detailed knowledge
of localized network and system issues should not be overlooked when
planning for major change. Whenever possible, existing resources should
be reallocated, updated and reused—whether these resources are human
or technological.
In this chapter, we will examine examples of value that may be con-
served or sought during architectural realignment projects. The rest of the
book will then examine specific enterprise elements and network manage-
ment options in greater depth.
Impact and Return on Effort
The Pareto principle, also known as the 80/20 rule, is a management prin-
ciple that evolved from the observations of the Italian economist, Vilfredo
Pareto. Presented by Dr. Joseph Juran and named for Pareto's original
observations, the 80/20 rule states that in many settings, 80% of conse-
quences are derived from 20% of causes. This means that roughly 80%
of all trouble tickets will be opened by roughly 20% of the client base,
or that approximately 80% of available security options can be imple-
mented through 20% of the overall security effort. Applied to technology
management, this is a useful tool for understanding the impact of appli-
cation development, resource allocation, user productivity suite selection,
and a variety of other broadly applied strategies.
Applying the 80/20 Rule
When developing a new application, the 80/20 rule suggests that 80%
of the final product will be achieved during the first 20% of time
spent in development and testing. When user interface preferences
and feature creep are added into such a project, this can easily be the
case—it is if not 90/10 or worse. Conversely, users may only consume
20% of the features of a productivity suite to complete 80% of their
work, rendering further development effort beyond these core features
effectively “gold plating” (functionality beyond the specified scope of
the project).
The 80/20 rule can also be applied when selecting standard technologies
for use across the enterprise, by first identifying the key functionalities and
