Data Governance Executive Sponsors

Executive Sponsors

Data Governance Executive Sponsors Meeting
November 5, 2007

Attending: Lori Temple, Cem Sunata, Suzanne Carlson, Larry Hamilton, Kari Coburn, Brent Morgan, John Tully, Lynne Personius, Monty Young.

1. Data User Groups in the Data Governance Structure
Discussion based on the attachment. There was general agreement that these should be formed, with the membership represented on the DGCouncil web site. Executive Sponsors agreed to help data stewards as necessary to bring them together. The target date to have the groups in place was mid-January.

2. Oversight  - data stewards need oversight from Executive Sponsors
We discussed how Executive Sponsors can provide oversight for the work of the data stewards. We covered reports, the need for help resolving some projects, and the project management tools to executive sponsors carry out this responsibility. We agreed that data stewards need oversight from this group.

    1. Reports are issued each month from the DGCouncil  Executive Sponsors will review them to:
      1. Ensure that data projects are moving at a reasonable rate
      2. Check to be sure they are areas that you feel should be addressed
      3. Some projects need decisions to come to resolution. Executive Sponsors can take guide in sever ways.
        1. Remove this project from consideration
        2. Encourage staff in the culture of data governance, ie work together across department boundaries
        3. Track projects in your area, and get information from data stewards if there are questions
        4. Intervene when you feel a need
        5. Establish new data governance principle – don’t complain without contributing
      4. Help establish data user groups
    2. Project management tools to help provide updates on progress.
      1. Presently using prototype from the DGCouncil web site.
      2. Project management module of TMA will be used
        1. Demonstration in December, with progress updates along the way
        2. Many thanks to Facilities for helping with this implementation.

3. Transparency – how to get data stewards to openly (and comfortably) share work.

  1. The purpose is to allow them to have power over what is happening in their systems.
    1. Crucial to successful “horizontal” view of data

4. Responsibility for data elements based on NSHE common data element list
The rationale and implications for using NSHE’s common data element list to determine campus level responsibility, was discussed, and we agreed to use this as the basis of many efforts of the data stewards.

    1. NSHE is establishing a dictionary of common data elements. It is being reviewed and will be posted to web site. when complete. 
    2. This will be the starting point for data governance, these elements will be included as a UNLV data dictionary.
    3. The data stewards need to review to determine the appropriate person for each element.
    4. Data elements will grow as situations warrant
      1. Building/room codes
      2. Highest degree
      3. Person ID  - SIS ID will be the same as Instructor ID
    5. NSHE is beginning with SIS data elements. We will begin working with these elements as well, and work toward data governance becoming a principle. Data stewards will learn to question every element – is this owned by us? Elements in our system may be owned by someone else.

     

    We will meet again to review progress on the new TMA project management tool.