Presented by Kelle O'Neal
With the shift toward augmented Analytics and the race to achieve digital business transformation, Data Governance may seem like yesterday’s news. In reality, Data Governance is more important than ever – and has evolved and matured along with other areas of Data Management. Companies able to ride the maturity wave and build upon a solid foundation of Data Management will be better poised for meeting new regulations, competing in the marketplace and deriving tangible results from new technologies and capabilities.
The scope of “Data Governance 1.0” is the foundation of many data-driven organizations, ensuring accountability, quality and control of critical data elements and master data. Largely focused on structured data, “Data Governance 2.0” will extend further up and down the data supply chain to include data acquisition and data usage. Therefore, Data Governance will extend to data in flight, not just at rest. This is where the use of catalogs and other solutions will enable the governance organization to provide guidance, standards and controls to ensure that the appropriate levels of rigor are maintained.
Data Governance 2.0 will also encompass other practice areas like data acquisition, data vendor management and reports/Analytics governance, among others. It will also incorporate Unstructured Data, extending to not only the Unstructured Data prevalent in Big Data and Analytics, but also a company’s intranet site, Sharepoint sites and content on externally facing websites.
Attendees will learn techniques for riding the Data Governance 2.0 wave including:
Leveraging the current scope of Data Governance and previous adoption to extend appropriate practices to cover other data types
Ensuring there is appropriate representation and accountability identified to cover the additional data types
Prioritizing effort based on business objectives
Recognizing that there will be varying levels of maturity across the different categories of data, as well as along the supply chain. This will mean that there will be additional burden on the Data Governance “Office” to maintain project plans, standards, artifacts, training, communication and other things needed to effectively manage the Program