Page 84 -

Overview 63

sure the nascent team gets sufficient “air coverage” (i.e., be introduced or initially sponsored by
a respected executive). If an MDM project is initiating DG, then the project sponsor needs to kick
this off.
Activity: Propose Scope and Initial Approach to Define and Deploy DG

This set of tasks develops the plan for the definition and rollout of the DG program. Any required
constraints are applied and any required assessments are determined.
Activity Summary Table

Objective Define the final areas subject to DG. Based on a standard
definition of DG, adjust the scope based on any
constraints such as timing, market conditions, or
regulations, then define the DG rollout plan.
Purpose Refine the proposed scope based on realities of timing and
develop a detailed approach to deploying the DG program.
Inputs 1. Initial scope
2. Basic DG deployment template (see appendices)
Tasks 1. Define DG specific tasks.
2. Define known constraints within proposed scope.
3. Define required assessments.
4. Define standard startup tasks.
Techniques None
Tools Word, PowerPoint, or similar
Outputs 1. DG tasks
2. Known constraints (e.g., market, time, regulations)
3. Required assessment tasks
4. Standard enterprise program startup tasks (if any)
Outcome DG project plan
FIGURE 6-6

Activity Summary Table.
Business Benefits and Ramifications

When the team starts the detailed planning, the full extent of required activity will become apparent.
Scope can be adjusted here. This prevents the DG effort from possibly going after too much at one
time. For a program-driven DG effort, such as one under an MDM umbrella, the benefit comes from
beginning to grasp the impact and interactions with the sponsoring effort.
Approach Considerations

Obviously, the final scope determination will be dependent on whether the DG program is based on
a program like MDM or is part of a larger EIM program.
Sample Output

There is a sample DG project plan in Appendix 1.