Build and reconciliation run as Agile sprints inside each Waterfall wave. The TPM's job here is visibility and momentum: everyone can see health at a glance, blockers surface early, and decisions get made once and recorded.
Delivery model
Each wave is a mini-project: build the objects, convert the code, load history, reconcile, and fix. Sprints carry the work; the wave's phase gate — "every object reconciled and signed off" — is what lets it exit. Progress is tracked as % mapped → % built → % reconciled per wave, so "80% done" means something specific.
Leadership visibility
One screen the steering committee reads in two minutes: health per workstream, what moved, what's blocked, and what needs a decision.
Sales + Mktg objects built; history loaded. 92% reconciled.
Revenue by Segment rebuild behind by 1 sprint — SME review slot slipped.
Reconciliation suite passing; report-parity in progress.
Champions onboarded for Sales; training content in build.
| Milestone | Status | Decision needed |
|---|---|---|
| Wave 3 reconcile complete | At risk | Approve extra SME hours to recover BI slip |
| Wave 4 build start | On track | — |
Operational heartbeat
Risks, assumptions, issues, dependencies — the living tracker the whole program runs off. An issue is a risk that already happened; a dependency is what one team needs from another.
| Type | Item | Status | Owner · action |
|---|---|---|---|
| Issue | Revenue sum in Snowflake exceeds source by 6% | Open | TPM · traced to snapshot grain — see decision log D-07 |
| Risk | SME availability for Wave 4 UAT | Monitoring | Change Lead · slots booked 3 weeks out |
| Assumption | Historical FX rates available for USD normalization | Confirmed | Data Gov · rate table sourced |
| Dependency | Wave 3 facts need Wave 1 shared dimensions | Met | Data Eng · dims signed off |
Change control & decisions
Scope changes go through impact assessment and approval — not the keyboard. And the ambiguous calls are ruled by the business, logged, and never re-litigated.
| ID | Decision | Ruling | By |
|---|---|---|---|
| D-07 | Does "close amount" mean booked or forecasted revenue? | Booked. Forecast moves to a separate measure. Resolves the 6% variance. | Sales Finance SME |
| D-08 | Retire or migrate the legacy Quota v3 report? | Retire — confirmed duplicate, no 12-mo access. | Sales Ops |
Defining done
Reconciliation, then system integration, then report parity, then UAT sign-off by the business. The value of the strategy shows when it catches something.
Golden thread · the catch
Reconciliation flagged the Sales/Revenue close-amount sum running 6% high in Snowflake. Not a load bug — a grain mismatch: the source carried one row per opportunity per daily snapshot, and the join fanned it out. The fix wasn't code; it was the D-07 ruling that fixed the definition and the grain. Caught in test, not by a controller three weeks after go-live.