From the course: Automating Data Quality in Dev Environments
Unlock the full course today
Join today to access over 24,600 courses taught by industry experts.
Write data requirements for your roadmap
From the course: Automating Data Quality in Dev Environments
Write data requirements for your roadmap
- If you work in tech, you've likely gathered requirements at some point. Requirements have two parts. User stories, which describe how specific user groups need a tool to function, and functional requirements, which describe how a product must work to bring user needs and stories to life. Between user stories and functional reqs, you'll want to get more granular about whom you're serving. This is especially crucial when writing requirements for your data product. Along with your standard user stories and functional requirements, you'll need to think critically about which data you need for your product. When you write out your requirements, make sure to include user roles, which titles do the user groups have per user story? A story can serve one or many groups of users. Make sure to note that when writing requirements. Trigger points, which actions must occur within your product to fulfill the user stories. Data points, which data do you need to fulfill each user story. And…
Contents
-
-
-
-
(Locked)
Write data requirements for your roadmap1m 51s
-
(Locked)
Confirm your data's source system(s)2m 17s
-
(Locked)
Establish the right data system integrations2m 34s
-
(Locked)
Define your source data's minimum acceptance criteria (MAC)1m 52s
-
(Locked)
Set up data lineage tracking3m 2s
-
(Locked)
Define levels of access per user2m 36s
-
(Locked)
Draft a to-be process map2m 33s
-
(Locked)
Define areas of data transformation2m 35s
-
(Locked)
Choose some super users to validate your product1m 44s
-
(Locked)
Give your data team room to fail2m 56s
-
(Locked)
-
-