Data Governance - Revision history

User at 19:27, 10 August 2023

2023-08-10T19:27:42Z

User at 19:50, 14 March 2023

2023-03-14T19:50:58Z

Show changes

User at 23:50, 19 January 2023

2023-01-19T23:50:53Z

Show changes

User at 00:23, 6 January 2023

2023-01-06T00:23:59Z

User: /* See Also */

2021-09-29T16:31:21Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T15:09:10Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

Show changes

User at 02:34, 22 February 2019

2019-02-22T02:34:58Z

User: /* Further Reading */

2019-02-21T23:33:53Z

User at 23:24, 21 February 2019

2019-02-21T23:24:46Z

User at 22:48, 21 February 2019

2019-02-21T22:48:53Z

@@ Line 93: / Line 93: @@
 == Data Governance Success Factors<ref>[http://agiledata.org/essays/dataGovernance.html Successful Efforts in Data Governance]</ref> ==
 The following factors are critical to the success of your data governance efforts:
-*Recognize that IT governance is the real goal. Data governance is just one part of your IT governance program, and it's highly coupled with other aspects such as development governance, security governance, and so on. Focusing just on data governance puts you at risk of optimizing data governance in such a way that it doesn't work well with the rest of your governance efforts, putting the entire governance program at risk.
+*Recognize that [[IT Governance]] is the real goal. Data governance is just one part of your IT governance program, and it's highly coupled with other aspects such as development governance, security governance, and so on. Focusing just on data governance puts you at risk of optimizing data governance in such a way that it doesn't work well with the rest of your governance efforts, putting the entire governance program at risk.
 *The governance effort must be owned. If someone is not responsible for the IT governance effort, it will very likely die a quick death in your organization. The people most suited to be the owners of IT governance are the executive business stakeholders. When it comes to data governance, the people least suited to govern are the data management professionals as they're the ones being governed (amongst others). In short, don't let your data governance efforts devolve into yet another political ploy of your data management group,
 *Have clear, quantifiable goals. What are you trying to achieve? Improved quality? Improved productivity? Improved time to value? Improved stakeholder satisfaction? Combinations thereof?
@@ Line 124: / Line 124: @@
 *[[Data]]
 *[[Information Governance (IG)]]

@@ Line 58: / Line 58: @@
 == Data Governance Framework ==
-'''[[Framing]] Data Governance'''<ref>Framing Data Governance [https://www.sas.com/content/dam/SAS/en_us/doc/whitepaper1/sas-data-governance-framework-107325.pdf SAS]</ref><br />
+'''Framing Data Governance'''<ref>Framing Data Governance [https://www.sas.com/content/dam/SAS/en_us/doc/whitepaper1/sas-data-governance-framework-107325.pdf SAS]</ref><br />
 Data governance is a combination of strategy and execution (Jill Dyché and Evan Levy Customer [[Data Integration]]:Reaching a Single Version of the Truth). It’s an approach that requires one to be both holistic and pragmatic:
 • Holistic. All aspects of data usage and maintenance are taken into account in establishing the vision.
@@ Line 64: / Line 64: @@
 To accomplish this, data governance must touch all internal and external IT systems and establish decision-making mechanisms that transcend organizational silos. And, it must provide accountability for data quality at the enterprise level. The SAS Data Governance
-[[framework]] (illustrated below) is a comprehensive framework for data governance that includes all the components needed to achieve a holistic, pragmatic data governance approach.
+framework (illustrated below) is a comprehensive framework for data governance that includes all the components needed to achieve a holistic, pragmatic data governance approach.
 [[File:Data_Governance_Framework.png|400px|Data Governance Framework]]<br />

@@ Line 134: / Line 134: @@
 == See Also ==
-[[Governance]]<br />
+* [[Governance]]
-[[IT Governance]]<br />
+* [[IT Governance]]
-[[IT Governance Framework]]<br />
+* [[IT Governance Framework]]
-[[Corporate Governance]]<br />
+* [[Corporate Governance]]
-[[Big_Data|Big Data]]<br />
+* [[Big_Data]]
-[[Master Data]]<br />
+* [[Master Data]]
-[[Master Data Management (MDM)]],br />
+* [[Master Data Management (MDM)]]
-[[Data_Mining|Data Mining]]<br />
+* [[Data_Mining|Data Mining]]
-[[Data_Management|Data Management]]<br />
+* [[Data_Management|Data Management]]
-[[Data_Warehouse|Data Warehouse]]<br />
+* [[Data_Warehouse|Data Warehouse]]
-[[Customer_Data_Management_(CDM)|Customer Data Management (CDM)]]<br />
+* [[Customer_Data_Management_(CDM)|Customer Data Management (CDM)]]
-[[Business_Intelligence|Business Intelligence]]<br />
+* [[Business_Intelligence|Business Intelligence]]
-[[Data_Analysis|Data Analysis]]<br />
+* [[Data_Analysis|Data Analysis]]
-[[Data_Analytics|Data Analytics]]<br />
+* [[Data_Analytics|Data Analytics]]
-[[Predictive_Analytics|Predictive Analytics]]
+* [[Predictive_Analytics|Predictive Analytics]]
+* [[Cloud Computing Governance]]
 == References ==

@@ Line 10: / Line 10: @@
 Data Governance is frequently confused with other closely related terms and concepts, including data management and master data management.<ref>What Data Governance is Not [https://www.talend.com/resources/what-is-data-governance/ Talend]</ref><br />
 *Data Governance is Not Data Management
-Data management refers to the management of the full data lifecycle needs of an organization. Data governance is the core component of data management, tying together nine other disciplines, such as data quality, reference and master data management, data security, database operations, metadata management, and data warehousing.
+[[Data Management]] refers to the management of the full data lifecycle needs of an organization. Data governance is the core component of data management, tying together nine other disciplines, such as data quality, reference and master data management, data security, database operations, metadata management, and data warehousing.
 *Data Governance is Not Master Data Management
-Master data management (MDM) focuses on identifying an organization's key entities and then improving the quality of this data. It ensures you have the most complete and accurate information available about key entities like customers, suppliers, medical providers, etc. Because those entities are shared across the organization, master data management is about reconciling fragmented views of those entities into a single view—a discipline that gets beyond data governance. However, there is no successful MDM without proper governance. For example, a data governance program will define the master data models (what is the definition of a customer, a product, etc.), detail the retention policies for data, and define roles and responsibilities for data authoring, data curation, and access.
+[[Master Data Management (MDM)]] focuses on identifying an organization's key entities and then improving the quality of this data. It ensures you have the most complete and accurate information available about key entities like customers, suppliers, medical providers, etc. Because those entities are shared across the organization, master data management is about reconciling fragmented views of those entities into a single view—a discipline that gets beyond data governance. However, there is no successful MDM without proper governance. For example, a data governance program will define the master data models (what is the definition of a customer, a product, etc.), detail the retention policies for data, and define roles and responsibilities for data authoring, data curation, and access.
 *Data Governance is Not Data Stewardship
-Data governance ensures that the right people are assigned the right data responsibilities. Data stewardship refers to the activities necessary to make sure that the data is accurate, in control, and easy to discover and process by the appropriate parties. Data governance is mostly about strategy, roles, organization, and policies, while data stewardship is all about execution and operationalization. Data stewards take care of data assets, making certain that the actual data is consistent with the data governance plan, linked with other data assets, and in control in terms of data quality, compliance, or security.
+Data governance ensures that the right people are assigned the right data responsibilities. [[Data Stewardship]] refers to the activities necessary to make sure that the data is accurate, in control, and easy to discover and process by the appropriate parties. Data governance is mostly about strategy, roles, organization, and policies, while data stewardship is all about execution and operationalization. Data stewards take care of data assets, making certain that the actual data is consistent with the data governance plan, linked with other data assets, and in control in terms of data quality, compliance, or security.

← Older revision		Revision as of 23:33, 21 February 2019
Line 157:		Line 157:

	== Further Reading ==		== Further Reading ==
		+	*Effective Data Governance [https://www.infosys.com/data-analytics/insights/Documents/effective-data-governance.pdf Infosys]
		+	*An Overview of Data Governance [https://www.researchgate.net/publication/321899578_An_Overview_of_Data_Governance Zhang Ning]
		+	*Data Governance is Imperative for Big Data Analytics [https://journal.ahima.org/2017/10/27/data-governance-is-imperative-for-big-data-analytics/ Ahima]
		+	*The Role Of Data Governance In An Effective Compliance Program [https://www.forbes.com/sites/forbestechcouncil/2018/12/17/the-role-of-data-governance-in-an-effective-compliance-program/#3216523d6fc5 Thomas Sehested]
		+	*The Ethics Of Data Governance - 'Data Comes With Benefits And Liabilities' [https://www.forbes.com/sites/charlestowersclark/2019/01/23/the-ethics-of-data-governance-data-comes-with-benefits-and-liabilities/#6c874155215a Charles Towers-Clark]

← Older revision		Revision as of 23:24, 21 February 2019
Line 96:		Line 96:

	Common themes among the external regulations center on the need to [[Risk Management\|manage risk]]. The risks can be financial misstatement, inadvertent release of sensitive data, or poor [[Data Quality\|data quality]] for key decisions. Methods to manage these risks vary from industry to industry. Examples of commonly referenced best practices and guidelines include [[COBIT (Control Objectives for Information and Related Technology)\|COBIT]], ISO/IEC 38500, and others. The proliferation of regulations and standards creates challenges for data governance professionals, particularly when multiple regulations overlap the [[Data Management\|data being managed]]. Organizations often launch data governance initiatives to address these challenges.		Common themes among the external regulations center on the need to [[Risk Management\|manage risk]]. The risks can be financial misstatement, inadvertent release of sensitive data, or poor [[Data Quality\|data quality]] for key decisions. Methods to manage these risks vary from industry to industry. Examples of commonly referenced best practices and guidelines include [[COBIT (Control Objectives for Information and Related Technology)\|COBIT]], ISO/IEC 38500, and others. The proliferation of regulations and standards creates challenges for data governance professionals, particularly when multiple regulations overlap the [[Data Management\|data being managed]]. Organizations often launch data governance initiatives to address these challenges.
		+
		+
		+	== Data Governance Success Factors ==
		+
		+	'''Successful Efforts in Data Governance'''<ref>Data Governance Success Factors [http://agiledata.org/essays/dataGovernance.html Agile Data]</ref><br />
		+	The following factors are critical to the success of your data governance efforts:
		+	*Recognize that IT governance is the real goal. Data governance is just one part of your [[IT Governance\|IT governance]] program, and it's highly coupled to other aspects such as development governance, security governance, and so on. Focusing just on data governance puts you at risk of optimizing data governance in such a way that it doesn't work well with the rest of your governance efforts, putting the entire governance program at risk.
		+	*The governance effort must be owned. If someone is not responsible for the IT governance effort it will very likely die a quick death in your organization. The people most suited to be the owners of IT governance are the executive business stakeholders. When it comes to data governance, the people least suited to govern are data management professionals as they're the ones being governed (amongst others). In short, don't let your data governance efforts devolve into yet another political ploy of your data management group,
		+	*Have clear, quantifiable goals. What are you trying to achieve? Improved quality? Improved productivity? Improved time to value? Improved stakeholder satisfaction? Combinations thereof?
		+	*Measure and honestly report the results. It's easy to talk about quantifiable goals, but it takes a fair bit of integrity to live up to promises. It's easy to manage direct costs such as the salaries of the people involved with the governance effort, but a bit more difficult to measure indirect costs such as the opportunity cost of potentially lengthening decision and development life cycles due to increased governance (this issue is particularly acute for traditional governance strategies). Measuring the benefits can also be challenging, although as Doug Hubbard points out in How to Measure Anything: Finding the Value of Intangibles in Business, it is possible if you think outside the box a bit. Automating metrics collection is an important aspect of lean governance.
		+	*Less is more. You need a lot less governance than what the pro-governance people believe, although probably a bit more governance than what the anti-governance people think. If you find that you need more governance it's a lot easier to add it than it is to remove unnecessary governance activities once they're in place.
		+	*Educate the people affected. If the people involved, including those being governed, don't understand what you're trying to achieve and or don't believe that any additional effort on their part is worthwhile then your governance effort will quickly fall apart. Furthermore, this sort of education must be ongoing.
		+
		+
		+	== Data Governance Challenges ==
		+
		+	'''The Challenges of Data Governance'''<ref>What are the Challenges of Data Governance [https://www.eolitservices.co.uk/2018/02/05/biggest-challenges-data-governance/ EOL]</ref>,br />
		+	Data Governance is one of the biggest challenges that companies face and failing to get it right can not only result in financial implications, but reputational damage too.
		+	*Data Volumes Are Growing: On one hand, the fact that businesses are developing more and more data is a great thing; it shows that they are expanding and becoming more complex. However, it also means that data governance becomes more complex, as you must consider each individual piece of data, its sensitivity and storage and distribution needs. In order for your data governance strategy to be effective, you must maintain an inventory of all your data, which is naturally more challenging the more data you have.
		+	*Encouraging Employee Compliance: Unfortunately, one of the biggest challenges in data governance is ensuring that your employees comply with your overall data strategy, something often borne out by a lack of understanding rather than a lack of desire. To combat this you can present your data governance strategy in a centralised and easy-to-access location and you might also invite your employees to give their own opinions and suggestions to improve your strategy and to make it more accessible. Employees are more likely to comply with procedures they have helped to create, as it will not feel like such a restriction.
		+	*Ensuring Accountability: One of the most important aspects of data governance is assigning accountability. Under the GDPR, it will be compulsory for certain businesses to appoint a Data Protection Officer, who will be accountable for data governance as a whole. However, even if your business is not legally required to do so, it may be prudent to establish a data governance council (with representatives from each department) to define data procedures and policies. This will help to individualise accountability, as procedure and policy can be implemented on a smaller scale, to ensure the business’ overarching data governance strategy is effective.
		+	*Dealing with Redundant Data: It is only natural that a business will accumulate data that they no longer need. However, it is important that you have a policy for dealing with this redundant data, as storing it unnecessarily will just make the management of your most valuable data even more more of a challenge. Identifying redundant data is only one step, perhaps the most important step is to ensure that your data governance strategy is followed, and that the data is disposed of securely.
		+
		+
		+	== Data Governance Best Practices ==
		+
		+	Essentially, there are 4 data governance best practices when launching a data governance program:<ref>What’s the data governance best practices you should start with when kicking off a governance program? [https://www.collibra.com/blog/4-data-governance-best-practices Collibra]</ref><br />
		+	1. Focus on the operating model: The operating model is the basis for any data governance program. It includes activities such as defining enterprise roles and responsibilities across the different lines of business. The idea is to establish an enterprise governance structure. Depending on the type of organization, the structure could be centralized (if a central authority manages everything), decentralized (if operated by a decentralized or group of authorities), or federated (if controlled by independent or multiple groups with little or no shared ownership).<br />
		+	2. Identify Data Domains: After establishing the data governance structure, the next step is to determine the data domains for each line of business. The most famous examples include customer, vendor, and product data domains. Depending on the type of industry, we come across different kinds of domains. But everything boils down to identifying domains and capturing information about a business and its consumers.<br />
		+	3. Identify critical data elements within the data domains: After defining the data domains, now, we are standing at the pinnacle. From here, evidently, we see data domains touching 10s, 100s, and 1000s of systems and applications containing key reports, critical data elements, business processes, and more. Obviously, we don’t want to boil the ocean by focusing on all the data artifacts at once. Instead, we should only identify what’s critical to the business.<br />
		+	4. Define control measurements: The next step is to set and maintain control to sustain the data governance program. Data governance is not a one-time project. It is an ongoing program to fuel data-driven decision making and creating opportunities for business. It prepares an organization to meet business standards. Control measurements include the following key activities:
		+	*Define automated workflow processes and thresholds for approval, escalation, review, voting, issue management and more
		+	*Apply workflow processes to the governance structure, data domains, and critical data elements
		+	*Develop reporting on the progress of steps 1 through step 4
		+	*Capture feedback through automated workflow processes

@@ Line 1: / Line 1: @@
-According to DAMA International, "'''Data Governance''' is the exercise of authority and control (planning, monitoring, and enforcement) over the management of data assets.”<ref> Definition: What is Data Governance? [https://dama.org/content/body-knowledge DAMA International]</ref>
+According to DAMA International, "'''Data Governance''' is the exercise of authority and control (planning, monitoring, and enforcement) over the management of data assets.”<ref> Definition: What is Data Governance? [https://dama.org/content/body-knowledge DAMA International]</ref> Data governance is the discipline of cataloging and defining important data, assigning ownership of data and incorporating governance of data into the everyday business process.
@@ Line 7: / Line 22: @@
 To truly manage data as a valued enterprise asset, data governance must be managed as a business function like finance or human resources. The primary business processes (illustrated in the figure below) enable data governance and stewardship, which include processes that cleanse, repair, mask, secure, reconcile, escalate, and approve data discrepancies, policies and standards. There are over twenty distinct processes segmented into four core process stages – all of which are iterative and encompass many parallel activities depending on the stage of maturity:
-[[File:Data_Governance.png|300px|The Process Stages of Data Governance]]<br />
+[[File:Data_Governance.png|400px|The Process Stages of Data Governance]]<br />
 source: [https://blogs.informatica.com/2014/01/02/the-process-stages-of-data-governance/#fbid=bv-w_k8ttM1 Informatica]
@@ Line 16: / Line 31: @@
 A data governance initiative must build competencies, assign roles and responsibilities and invest in technologies to enable these core processes no matter the scope and scale of your business objectives.  A pilot data governance project focusing on improving the quality or security of a single data item, phone number as an example, should follow the same approach as a holistic data governance function that’s managing all business critical data assets.
 == Benefits of Data Governance ==
@@ Line 37: / Line 96: @@
 Common themes among the external regulations center on the need to [[Risk Management|manage risk]]. The risks can be financial misstatement, inadvertent release of sensitive data, or poor [[Data Quality|data quality]] for key decisions. Methods to manage these risks vary from industry to industry. Examples of commonly referenced best practices and guidelines include [[COBIT (Control Objectives for Information and Related Technology)|COBIT]], ISO/IEC 38500, and others. The proliferation of regulations and standards creates challenges for data governance professionals, particularly when multiple regulations overlap the [[Data Management|data being managed]]. Organizations often launch data governance initiatives to address these challenges.