Page 109 -

88 CHAPTER 8 Vision

• Where DG processes, IM processes, and project-related processes intersect.
1
• The effects and details of long-standing requests to “fix” data in major applications.
If you are standing up DG as part of MDM or something similar and cannot find any business drivers,
you will need to execute a business-alignment exercise. The MDM team is in a lot of trouble but does
not realize it.
Activity Summary Table
Objective Develop an initial view of DG requirements that shows
how DG will support business needs.
Purpose This activity will provide focus for the DG team, help
identify stakeholders and stewards, and provide more
insight into metrics and additional tasks to help sustain
DG.
Inputs 1. Business drivers, goals, and objectives
2. Data artifacts affected by DG
3. Outstanding application issues
4. Knowledge of organization risks
Tasks 1. Gather levers or stated goals and strategies and
examine required content to enable them.
2. Gather existing artifacts such as data or process
models or DQ surveys.
3. Examine backlogs of report requests, website
updates, and requisitions for external data, data
issues, and anecdotal requests for DG.
4. Identify obvious targets for improved quality or those
that would benefit from external scrutiny.
5. Examine significant business events and activities for
content affecting risk such as safety, regulated
products, rate filings, etc.
Techniques
Tools Word, PowerPoint, and similar; requires
management tools, and strategic planning or enterprise
architecture tools
Outputs 1. Business goals affected by DG
2. Data artifacts affecting DG
3. Direct and indirect requests for DG
4. Data quality opportunities for DG
5. Risk areas benefitting from DG
FIGURE 8-4

Activity Summary Table.

1
After several decades of doing this type of work, we are always amazed that among all of the needs and issues we
document, all organizations can be counted on to have at least one of the following two DG drivers. First is the eternally
lasting request to fix an old operational applications database. This application is the one that is so old no one can actually
risk touching the codedso they try to fix the data, but the request has always fallen off the priority list. Second is that every
organization has its legacy “data dumpster”dthe ancient database that the data warehouse (and the second-generation data
warehouse) was supposed to replace. There is one individual who has mythical powers and is able to navigate and support
this database. Managers lay awake at night when they realize she will retire someday. Our theory is that all of the people
supporting the legacy data are related, and originated from an ancient medieval guild.