Communications Model for Data Governance Team Deliverable Template
From MIKE2.0 Methodology
| This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
|
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
|
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.
|
Communications and Awareness in the Communications Model for Data Governance team involves the following steps:
- Definition of a Communications Plan for communicating at multiple levels, including identification of the available communication methods or tools
- Analysis of key stakeholders to be targeted for communication and training activities
- Assembly of Data Governance standards, policies, and processes in a fashion that can be clearly understood
- Identifying how stakeholders will access the standards, policies, and processes
- Definition of a training plan and schedule
- Development of the required training materials to support the Data Governance programme
- Execution of training
- Definition of Data Governance performance metrics, by role
- Alignment of employee goals and performance objectives with the Data Governance programme and performance metrics
= Example of a Communications Model for Data Governance team
Principles, Policies and Standards
Data Principles - Owner: New Board
- Data is an Asset - data is an asset that has value to the enterprise and is managed accordingly
- Data is Shared - users have access to the data necessary to perform their duties; therefore, data is shared across Enterprise functions and organizations
- Data is Accessible - data is accessible for users to perform their functions
- Data Trustee - each data element has a trustee accountable for data quality
- Common Vocabulary and Data Definitions - data is defined consistently throughout the Enterprise, and the definitions are understandable and available to all users
- Data Security - Data is protected from unauthorized use and disclosure.
Policies – Owner: New Board
Policy
| Description
| Next Step
|
Data Security
| This policy identifies the security access required for key data across user groups.
|
- Review of groups with access to modify/delete master data
- Review of groups with access to extract data for reporting
|
Data Audit
| This policy identifies the logging required for changes to key data.
|
- Review of audit trail requirements for data update (to complement security policy)
|
Data Retention
| This policy identifies the minimum data retention requirements.
|
- Review of data retention requirements for key data subject areas
|
Master Data
| This policy identifies where master data resides and how master data is handled.
|
- Establish policy for ownership and maintenance of master data for key data subject areas
- This is required as an input to the data management process review.
|
Metadata
| This policy covers enforcement of metadata capture and maintenance
|
- Confirm ownership of this policy as the BI team and define this policy
|
Reference Data
| This policy governs the ownership of development and capture of shared reference data
|
- Confirm ownership of this policy as the BI team and define this policy
|
Data Quality
| This policy defines the strategic and operational direction for data quality management and improvement
|
- Establish current and target data quality position based on business requirements
|
Standards - Owner: New Board
Data Standard
| Description
| Next Step
|
Data Specification Standards
| These govern the definition of data, including minimum data interface standards.
|
- Confirm owner for this standard and required scope
|
Data Modelling Standards
| These provide a set of guidelines that should be followed for modeling data in operational or information systems
|
- Confirm owner for this standard
|
Data Capture Standards
| These govern the acquisition and update of data by operational staff
|
- Confirm owner for this standard
|
Data Security Standards
| These should be established to provide protection against unauthorized access and usage
|
- Confirm owner for this standard
|
Data Reporting Standards
| These are the baseline standards for end-user data in the reporting environment
|
- Confirm owner for this standard
|
Communication - Meetings
Communication Tool
| Description
| Audience
| Frequency
|
Data Governance Board
| Meeting to discuss key deliverables, issues and on-going activities.
| Data Governance Board
| Monthly, or as required
|
Data Quality Review
| Meeting to review the findings of each data quality assessment and next steps associated with resolving key issues.
| Working Group(s)
| Monthly, or as required
|
Data Critical Issue Meeting
| Discussion of Severity 1 issues status and plan for resolution.
| SWAT team of required individuals – to be determined based on issue.
| As Required
|
BI Team Meetings
| Regular meeting for BI team. Key data quality issues and status should be raised at this meeting.
| BI Team
| TBC
|
Communication - Reports
Communication Tool
| Description
| Audience
| Frequency
|
Data Quality Assessment Report
| Report that outlines findings on the data quality of source system extracts.
| Data Governance working group
| Quarterly, or as required
|
Data Issue Log
| A tool that captures the detail of data issues and is used to communicate and manage issues through the issue management process.
| Project(s) and Working Group(s)
| Weekly, or as required
|
Data Test Reports
| Report that indicates the quality (good and bad) of data provided in source system extracts.
| Data Governance working group
| Ongoing – as required
|
Data Acceptance Report
| Final report that outlines the overall quality of data as moved into target environment.
| Project(s) and Working Group(s)
| One-off per implementation
|
Meeting Minutes
| Minutes (including decisions and agreed action) from meetings
| Meeting attendees and interested parties
| Ongoing – as required
|
|