From the course: Automating Data Quality in Dev Environments

Unlock the full course today

Join today to access over 24,800 courses taught by industry experts.

Define your source data's minimum acceptance criteria (MAC)

Define your source data's minimum acceptance criteria (MAC)

From the course: Automating Data Quality in Dev Environments

Start my 1-month free trial Buy for my team

Define your source data's minimum acceptance criteria (MAC)

“

- [Instructor] Once you know which data you need for your product, you'll need to find it in the system where it lives. This data will flow throughout your tech stack, so it's crucial to ensure that it meets your quality standards at the start. If you've worked in tech for some time, you've probably written requirements at some point. These look different depending on your role. If you're in product or user research, you've probably written user stories, which are sentences that share first-person accounts of what users need a product to do. If you're in development, architecture, or engineering roles, you've likely worked with functional requirements, which share how the product will work. While it's not an exact one-to-one, you can apply these principles to requirements for data. This is a big part of the process to build data products. Your Quality Assurance Engineers need to know if the data flowing throughout your pipelines meets pass or fail conditions, so they can do their…

Contents