Data Product Maturity Checklist
Use this tool to assess a data product against DPCH01–DPCH14, calculate a maturity %, and get prioritized recommendations. Your selections are saved locally.
📊 Data Product Maturity Checklist
0.0% — Data Asset (Non-Productized)Mark each characteristic as Yes, Partial (50%), or No. Add optional evidence links/notes for governance.
| # | DPCH | Characteristic | Checklist Item | Description | Weight | Status | Evidence (URL or note) | Points |
|---|---|---|---|---|---|---|---|---|
| 1 | DPCH01 | Domain-Owned | Named Data Product Owner (DPRO) Assigned | Product is owned by a specific business domain and managed by a named DPRO with lifecycle accountability. | 8% | 0 | ||
| 2 | DPCH02 | Deployable | Independently Deployable Unit | Product can be deployed, updated, and versioned via CI/CD or infrastructure automation without affecting other products. | 8% | 0 | ||
| 3 | DPCH03 | Declarative | Defined via Declarative Specification | The product structure, transformations, and configurations are expressed through DPDS/YAML-based declarative specs, not manual scripts. | 8% | 0 | ||
| 4 | DPCH04 | Discoverable | Registered in Data Marketplace or Catalog | Product is discoverable with searchable metadata, tags, glossary terms, and ownership details. | 7% | 0 | ||
| 5 | DPCH05 | Self-Describing | Rich Metadata Embedded | Product contains descriptive metadata on schema, purpose, lineage, data quality, and usage context. | 6% | 0 | ||
| 6 | DPCH06 | Trustworthy (via Trust Signals) | Emits Trust Signals | Product generates and exposes measurable trust metrics — data quality, lineage, control adherence, and policy conformance. | 8% | 0 | ||
| 7 | DPCH07 | Reusable | Reused Across Use Cases or Domains | Product is actively consumed by multiple applications, teams, or AI models beyond its initial creation context. | 5% | 0 | ||
| 8 | DPCH08 | SLA–SLO Backed & Observable | Observable with SLAs and Quality Guarantees | Product includes defined SLAs, SLOs, and observability hooks (freshness, availability, latency, quality). | 8% | 0 | ||
| 9 | DPCH09 | Compliant by Design | Policy-as-Code and Entitlement Controls Enforced | Product integrates data access, residency, and regulatory controls via declarative policy enforcement. | 8% | 0 | ||
| 10 | DPCH10 | Addressable | Provides Well-Defined Output Interfaces | Product exposes documented APIs, SQL endpoints, SDKs, or data ports for human and machine access. | 7% | 0 | ||
| 11 | DPCH11 | Semantically Aligned | Aligned to Enterprise Vocabulary / Ontology | Product uses canonical identifiers (UBRs), conforms to shared vocabularies, and maps to enterprise domain models. | 8% | 0 | ||
| 12 | DPCH12 | Consumption-Driven Intent | Built for Clear Business or Analytical Purpose | Product was designed with a specific business, regulatory, or AI/ML use case as its driving rationale. | 7% | 0 | ||
| 13 | DPCH13 | Testable & Versioned | Version-Controlled and Contract-Tested | Product lifecycle includes automated contract tests, semantic versioning, and backward compatibility guarantees. | 8% | 0 | ||
| 14 | DPCH14 | Economically Accountable | Included in Chargeback/Showback Model | Product’s cost, usage, and platform resource consumption are tracked and visible to stakeholders. | 4% | 0 | ||
| TOTAL | 0.0 | |||||||
🎯 Prioritized Recommendations
High Priority — Not Met
- DPCH01 (8%): Assign a named DPRO with clear lifecycle accountability and publish ownership metadata in catalog.
- DPCH02 (8%): Containerize artifacts, define infra-as-code, and set up a CI/CD pipeline that versions and deploys independently.
- DPCH03 (8%): Author a DPDS spec; validate it in PR checks; deprecate ad-hoc/manual scripts with declarative pipelines.
- DPCH06 (8%): Instrument trust metrics (freshness, completeness, lineage depth, policy checks) and publish as a product SLO feed.
- DPCH08 (8%): Define SLIs & SLOs; set alerts/dashboards; document incident runbooks and escalation paths.
- DPCH09 (8%): Codify and test ABAC/PBAC policies, residency, PII classification; add pre-access checks and audit trails.
- DPCH11 (8%): Map schema to enterprise ontology; resolve UBRs; publish semantic contracts and test conformance.
- DPCH13 (8%): Introduce contract tests and semver; add backward-compatibility gates to CI; publish changelog & deprecation policy.
- DPCH04 (7%): Onboard to the marketplace/catalog with rich tags, glossary links, owners, and sample queries/consumption guides.
- DPCH10 (7%): Define output ports (SQL, REST, gRPC); add OpenAPI/specs and quickstart notebooks for consumers.
- DPCH12 (7%): Document primary use-cases and KPIs; include sample queries and dashboards linked to those outcomes.
- DPCH05 (6%): Publish schema, dictionaries, lineage and data quality profile; auto-generate docs from source-of-truth.
- DPCH07 (5%): Abstract product interfaces, add SDK/SQL examples, and evangelize cross-domain use with reference integrations.
- DPCH14 (4%): Integrate FinOps telemetry; expose cost-per-consumption unit; agree showback/chargeback with stakeholders.
ℹ️ Scoring Guidelines
- Yes = full weight
- Partial = 50% of weight
- No = 0%
≥ 80%: Production-Grade Data Product · 50–79%: Evolving / MVP Product · < 50%: Data Asset (Non-Productized)
🔐 Governance Tips
- Store evidence links to DPDS/DPROD files, dashboards, and policy repos.
- Export JSON for audit trails; attach to PRs or catalog entries.
- Review prioritized recommendations to plan next quarter improvements.