59 lines
1.4 KiB
Markdown
59 lines
1.4 KiB
Markdown
# Data Product Sheet
|
|
|
|
- Description
|
|
- Depends on
|
|
- Transformations
|
|
- Audience
|
|
- Ownership
|
|
- Technical
|
|
- Business
|
|
- Freshness and historical requirements
|
|
- Tooling
|
|
- Links/Accesses
|
|
|
|
## Description
|
|
|
|
General overview. Business context around it.
|
|
|
|
## Depends on
|
|
|
|
Where is the data coming from? What systems are integrated? Any pesky spreadsheets that are key for this?
|
|
|
|
## Transformations
|
|
|
|
Is this product showing data raw from source, or is it doing any logic? If so, how complex is it? Is it properly documented? Is it done manually or in an automated way?
|
|
|
|
## Audience
|
|
|
|
Who is consuming this data product? What is their user story around it?
|
|
|
|
## Ownership
|
|
|
|
### Business
|
|
|
|
Who is responsible for this domain? Who is responsible for the cleanliness/accuracy of the data?
|
|
|
|
### Technical
|
|
|
|
Who keeps this product up and running? Who's monitoring it? Who will take care of updates/upgrades? Who develops new stuff on it?
|
|
|
|
## Freshness and historical requirements
|
|
|
|
How fresh does the data need to be? Real-time, hourly, overnight, weekly, ...?
|
|
|
|
How far into the past do we need to show? How far into the past do we need to keep in case?
|
|
|
|
## Tooling
|
|
|
|
How is this data product built?
|
|
|
|
## Links/Accesses/Permissions
|
|
|
|
Where/how can the product be accessed?
|
|
|
|
How are accesses and permissions being managed?
|
|
|
|
## Additional docs
|
|
|
|
Any references to docs that might be found elsewhere. Typically, technical documentation and detailed data models.
|
|
|