|
You can refer Data Quality Assurance and Control guidelines tool as part of our Data Quality Management+ Toolkit package. In brief, an organization needs to define standard set of data quality assurance guidelines, which all the process, business and systems owners can follow.
Data Quality Assurance and Control guidelines are the easiest and among the first quick steps you can undertake. The DQ assurance controls are generic, common-sensical and easy to appreciate. The challenge will lie in ensuring the adherence to those guideline in the new projects as well as 'business as usual', when you will be tracking and reporting the adherence.
Therefore, we would suggest that, creating guidelines document is something, which you can do as of yesterday. We have given many examples and there is a listing of these methods in our DQ assurance chapter. We suggest following steps:
- Adopt our list of assurance methods and create the first draft, get it signed-off and publish. Do not include, on how you will be measuring the adherence.
- Add the specific controls which are relevant for your organization. For example a bank will have a different set of additional guidelines compared to a logistics company. Keep on upgrading your control guidelines document accordingly.
- You may also look at making this document as part of the overall control guidelines. We have mentioned it in our help guide that, the DQ assurance controls are not the only controls you need to maintain robust operations. For example, expense approval matrix is not part of DQ Assurance, but it a key component for maintaining financial controls.
- Over few months, you will be able to get the feedback on the ground regarding the adoption and understanding. You can then identify 4-5 initiatives, whereby you will adopt the DQ assurance tracking tool. This will provide you a phased and high-confidence approach.
- Implement 'Business as Usual' object level inventory tool for key objects in the last stage. This inventory is essentially the tracking of the state of DQ assurance in top-priority objects (interfaces, input forms, batches, data entities etc...).
|
