01

How data is tested on its way to production

Two paths: every change is tested before it ships, and every run before the business sees it.

Data Quality Gates
promotesame contractdeployspassfailresults · lineageChange path · every pull requestData path · every scheduled runObserve · every runData engineerPull requestcode + contractContract checkbreaking change failsCI testsunit · SQL · lintDevdeploy · smoke testQAtests on real shapePromotion gateapproved releaseProdsame definitionDrift checkenvs stay alikeSourceDB · app · filesIngestbatch · streamSchema gatecontract on landingBronzeraw · versionedTransformSpark · dbtData testsfresh · volume · rulesQuality gatepass or stopSilver · goldpublished productReports · ML ·agentsQuarantinefailed rows heldOwner alertedrunbook · fixCatalogowner · meaningLineagesource to reportDashboardssuccess · freshnessTest evidencekept per runRunbooksSRE on-call

Point at a component to light its links; select it for what it does here and the practice that makes it right.

Point at a component to see what it does; select it for the best practice.Open the architecture
02

Governance built into the platform

Part of the platform from day one, not a project that starts after go-live.

03

Who owns what

A typical split, agreed per engagement, removes the overlap between DevOps and data teams.

ActivityData engineeringDataOps (platform)Security
Data products and transformationsOwnsTemplates and CI/CDReviews sensitive data use
Platform, environments and IaCUsesOwnsSets baseline controls
Access policiesRequestsImplements as codeApproves policy
Quality rulesDefinesRuns them in every pipeline—
Monitoring and incidentsFixes data logicAlerting, runbooks, on-callSecurity incidents
04

Targets we agree at the start

Sample targets from NGT's DataOps catalogue, set per engagement and measured from day one. Targets, not results.

MeasureSample target (NGT)Why it matters
Platform infrastructure managed as code> 95%Rebuildable, auditable environments
Data deployments automated> 90%Changes ship through tested pipelines
Time to provision a platform environment< 30 minTeams start without tickets
Pipeline success rate> 95%Fresh data for reports and models
Platform availability99.9%A platform the business can rely on
Mean time to restore< 30 min to 1 hIncidents contained quickly
Manual access requests−80%Access follows policy, not tickets
Data projects on the standard platform> 90%One way of working across teams
SourcesNGT DataOps service offering drafts (Sep–Oct 2026)NGT DataOps & Data Platform Ops service catalogue (Sep 2026)NGT DataOps one-page offering and operating model (Sep 2026)NGT AI-First DevOps Transformation service offering (Oct 2026)NGT Google Cloud service offering v0.1