Master Data – Limiting the Scope

April 7, 2011 by
Filed under: Business Impacts, Data Quality, Master Data, Metadata 

A few months back I shared a post about proper scoping of a master data management activity to focus specifically on a smaller subset of business activities that (a) are impacted by the absence of a unified view of data or (b) can be measurably improved through the facilitation of a unified view of data. Part of the actualization of that unified view involves selecting the right business activities and then getting a better understanding of the data needs of those business activities.

So I thought I’d share some more thoughts about how to get that done with a list of tasks that can help refine the list of business activities using an example of customer data:

  1. List the business applications that create, update, or use data associated with customers.
  2. List the business contexts or workflows that are critical to customer interaction.
  3. What basic data concepts are used in one or more business contexts, such as an individual in roles of customer or employee?
  4. Consider and document the roles that each conceptual data object plays in different business applications.
  5. Note the data characteristics that differentiate the contextual (business application) use of a data object.
  6. If the data object is used within multiple business contexts, list the data attributes that describe the core (intrinsic, non-changing if possible) aspects of the object.
  7. Document any different variations for each object concept.
  8. Determine if the basic data concepts can be organized within a logical hierarchy.

More to follow…


Tell me what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!