From the course: Data Quality: Analytics and Serving

Exercise: Issue scoping

From the course: Data Quality: Analytics and Serving

Start my 1-month free trial Buy for my team

Exercise: Issue scoping

“

- [Narrator] Your stakeholders has surfaced the issues with the New York City parking violations report and so now we need to start the data quality resolution process. And if you need a reminder for the steps, you can go to the root cause analysis report where we have all these steps here. Let's do a preview of it and we can see all the various steps. Now, for the pacing of this course, we're going to combine issue triage and requirement scoping into one step. Now, typically, you'll either have a process already in place via a ticketing system, or you may need to have a meeting with relevant stakeholders to align on what issue is worth solving, all of which is business and situation specific. This does not mean you accelerate through this in real life scenarios just because we're moving fast through these steps on the course. In actuality, this is the most important step in a business environment, and at times can take the longest. It just doesn't translate well to a coding course, and I don't want to bore you here. Now, some key things to note. Remember in the earlier course, data quality core concepts, we highlighted that data quality is not about pristine data, but rather being fit for use for your stakeholders. They're very well may be data quality issues in the original clean data, New York City parking violations report, but we need to determine what's in scope and what's out of scope so we can focus on what's important, especially if we need to fix the issue quickly. In this scenario, the priority is getting the data back into the baseline state so that the report matches stakeholder expectations of the original report. With that said, if we do find data quality issues that are out of scope, we should put it into our root cause analysis report as something to fix and triage accordingly. Again, all business and situation specific. Now that we have this information, you should take some time to go fill out the root cause analysis report and give it a shot for issue triage and requirement scoping. Again, there's no right or wrong answers. We're all learning right here, but one thing I do want to note that if you do switch branches, you will overwrite what's in the file. So I suggest keeping track with your own file on a local machine so you can compare your notes with the project walkthrough notes. As we go through the project, each branch, this will be slowly filled out, so don't worry about getting it perfect. It'll be filled out for you along the way.

Contents