80 likes | 89 Vues
Implementing Data Governance as the Foundation of a LDS. Corey Chatis, Director of Data Quality, TN DOE Rick Rozzelle, Interim CIO, TN DOE. Overview. Implementing Data Governance: Getting Started Successful Strategies Lessons Learned Benefits to the TN DOE and Districts
E N D
Implementing Data Governance as the Foundation of a LDS Corey Chatis, Director of Data Quality, TN DOE Rick Rozzelle, Interim CIO, TN DOE
Overview • Implementing Data Governance: Getting Started • Successful Strategies • Lessons Learned • Benefits to the TN DOE and Districts • Roles of Data Management • Handouts
Implementing Data Governance: Getting Started • Solicit support from agency leadership • Establish a data governance policy • Make one person responsible for overseeing the governance structure • Develop criteria for designating data managers • Have clearly defined and documented data manager roles and responsibilities • Collectively create a mission statement and core goals/objectives for the governance group
Successful Strategies • Make one person responsible for overseeing the data governance group • Frame data governance as a mechanism for issue identification and resolution • Implement a log of critical data issues • Publish a data collection calendar • Foster cross-program area responses to data issues • Include district representatives in the governance structure • Communicate tangible benefits to DOE and districts as result of data management
Lessons Learned • Assess the skill set and mindset of each data manager to determine the level and type of support they will require to be successful • Ensure each data manager receives some value back from participating in the governance structure – make it a resource instead of a burden • Celebrate successes of all sizes – don’t underestimate the power of acknowledgment • Prioritize identified data issues and ensure a data manager is accountable for resolving each one
Benefits to the TN DOE and Districts • Increased communication/collaboration across program areas and between program areas and IT • More consistent, frequent communication with the districts regarding data • Reduction in redundant collections • Closer to one version of the truth • Reduced collection burden on districts • LDS built according to program area needs – not just an IT project
Roles of Data Management • Chief Information Officer (CIO) • Data Quality Director • Data Stewards/Managers • Database Administrators • Business Analysts • Data Management Committee (DMC) • Data Policy Committee (DPC)
Questions? Corey Chatis, corey.chatis@state.tn.us Rick Rozzelle, rrozzelle@celtcorp.com