Page 64 -
P. 64
Scope and Initiation 43
In this chapter, the phases are listed along with key considerations. We provide a list of key activities
and an example to provide context. The following chapters delve into the details of the activities and
look at specific cases and deliverables.
Each step builds upon the previous one. However, the steps can also be conducted as a “stand-alone”
process if the required artifacts or information for that step are available from another EIM-related
effort. There is a reference table in the appendices that can be printed or imported into a project plan.
SCOPE AND INITIATION
Anyone who has done any kind of program or project knows you need to start with an understanding of
scope. It is no different for deploying DG. After all, there is a great likelihood of affecting several
segments of your organization. Figure 5-1 shows how DG can be applied differently based on the type
of organization. In addition, there needs to be an understanding of how “deep” the DG program will be
going. There are also the traditional activities associated with starting any program or project.
Considerations
For example, right or wrong, most DG programs get started within an information technology (IT)
area. If a CIO is gung-ho about cleaning up the treatment of data and making it a powerful asset, she
had better verify that the scope of DG includes the creation and enforcement of broad-spectrum
policies. If an organization is highly regulated, then the compliance area needs to be brought into the
DG effort.
FIGURE 5-1
This figure shows a static view of the stand-up process we will cover.