Queensland Government

Data governance guideline

Document type:
Guideline
Version:
Final v1.0.1
Status:
CurrentNon-mandated
Effective:
October 2019–current
Security classification:
OFFICIAL-Public
Category:
Information

Introduction

Purpose

A Queensland Government Enterprise Architecture (QGEA) guideline provides information for Queensland Government agencies on the recommended practices for a given topic area. Guidelines are generally for information only and agencies are not required to comply. They are intended to help agencies understand the appropriate approach to addressing a particular issue or doing a particular task.

This document provides guidance to Queensland Government agencies who have identified a need to better plan, monitor and control their data. Its focus is on defining what data governance is, outlining what it is that needs to be governed and providing context around why data governance is important.

This guideline steps practitioners through a process designed to help identify what elements should be given priority in your agency's data governance practice, how to plan your response and what some common components of data governance may look like. Depending on the business problem, your agency's maturity level, the data management issues identified and what elements you may already have in place, this guideline is designed to allow a modular and scalable approach to building data governance practice. You can enter the cycle at any point and work through the elements relevant to your business problem based on the unique priorities of your agency.

Audience

This document is primarily intended for:

  • Data governance bodies
  • Senior executives
  • Business users
  • Enterprise data architects
  • Audit and risk managers
  • Information asset custodians
  • Information owners
  • Data analysts
  • Data scientists

Scope

In scope

All data of business value which is currently collected, created, used and stored by Queensland Government departments.

Out of scope

Specific guidance regarding records governance which can been found in the Records governance policy and the Records governance policy implementation guideline.

Background

The Data Management Body of Knowledge (DMBoK) defines data governance as the exercise of authority, control and shared decision-making (planning, monitoring and enforcement) over the management of data assets (p.69). In simple terms, data governance is about implementing a set of rules, processes and structures to ensure that an agency's data can meet both its current and ongoing business requirements.

Data governance is at the core of effective data management and will therefore play a central role in any well-defined and effective data strategy. Data governance is about minimising risks and maximising the value of data through oversite of the management of an agency's data. However, while data governance oversees the appropriate management of data, it is not involved in day to day data management activities, ensuring adequate separation between oversight and implementation activities.

Data governance is also an exercise in risk management because it allows agencies to minimise risks and maximise the value of data by focusing on the management of data through increased oversight. To succeed, data governance should be business driven and encompass a range of accountabilities relating to people, processes and technology. Because data governance business drivers will vary from organisation to organisation, data governance strategies will also vary, with focus being placed on those elements required to address the most pressing business problems.

Data governance basics

Implementing data governance

Operationalise data governance

Data governance implementation scenarios