CDMP Visual Route Overview

🏠 Dashboard · 📍 Snapshot · ☑ Progress Hub · ▶ Session Launcher · 🔎 Finder · 🧭 Route Navigator

Purpose: answer “where does this part fit?” before you enter the detailed route. This is an orientation map, not a progress tracker and not a replacement for the execution cards.

flowchart TD
    A[Start<br/>Sequence 001]

    P1[Phase 1<br/>Orientation, Foundations & Governance<br/>001–067]
    G1[Technology Gate A<br/>068–087]
    P2[Phase 2<br/>Core Data Management<br/>088–211]
    CP[Career Data Governance Platform<br/>212–223]
    P3[Phase 3<br/>Quality, Maturity & Organization<br/>224–290]
    CAP[Cross-Chapter Capstones<br/>291–310]
    P4[Phase 4<br/>Final Review, Exam Handoff & Career Proof<br/>311–330]
    END[Route Complete<br/>Sequence 330]

    A --> P1
    P1 --> G1
    G1 --> P2
    P2 --> CP
    CP --> P3
    P3 --> CAP
    CAP --> P4
    P4 --> END

Phase 1 — Orientation, Foundations & Governance · 001–067

Purpose: establish the operating rules, DMBOK foundation, ethics, governance and architecture before deeper technical work.

Route:

Program Orientation 001–010 → Chapter 1 011–026 → Chapter 2 027–039 → Chapter 3 040–052 → Chapter 4 053–065 → Governance Bridge 066–067

Handoff: Technology Gate A — Sequence 068

Technology Gate A · 068–087

Purpose: build only the Windows, PowerShell, VS Code, SQL, PostgreSQL, DBeaver and Git fluency needed for the upcoming data-management work.

Boundary: technology supports the curriculum; it does not replace DMBOK study or turn the route into engineering specialization.

Handoff: Chapter 5 — Sequence 088

Phase 2 — Core Data Management · 088–211

Purpose: move through modeling, operations, security, programmatic readiness, integration, content, master/reference data, analytics and metadata.

Route:

Chapter 5 088–100 → Chapter 6 101–113 → Chapter 7 114–126 → Technology Gate B 127–144 → Chapter 8 145–157 → Chapter 9 158–170 → Chapter 10 171–183 → Chapter 11 184–196 → Chapter 12 197–211

Handoff: Career Data Governance Platform Specialization — Sequence 212

Career Data Governance Platform Specialization · 212–223

Purpose: translate governance concepts into Purview-primary / Collibra-secondary platform reasoning without drifting into data-engineering or security-operations specialization.

Handoff: Chapter 13 — Sequence 224

Phase 3 — Quality, Maturity & Organization · 224–290

Purpose: strengthen quality management, big-data/data-science governance awareness, maturity assessment, organizational roles and change/adoption.

Route:

Chapter 13 224–238 → Chapter 14 239–251 → Chapter 15 252–264 → Chapter 16 265–277 → Chapter 17 278–290

Handoff: Cross-Chapter Integration — Sequence 291

Cross-Chapter Integration & Capstones · 291–310

Purpose: combine completed chapter knowledge and Meridian evidence into end-to-end diagnosis, decision and proof.

Boundary: integrate prior work; do not restart Meridian and do not use future knowledge before its route point.

Handoff: Final Review — Sequence 311

Phase 4 — Final Review, Exam Handoff & Career Proof · 311–330

Purpose: interleave retrieval, repair repeated weaknesses, practice pacing/navigation, package evidence and make the final readiness decision.

End: Sequence 330 — Final readiness decision and handoff

Three measures that must stay separate

Measure	What it tells you
Route online	The GitHub execution route exists and is navigable.
Artifact available	A required 00A mastery artifact or 00B Meridian lab actually exists.
Learner complete	You completed the work and passed the card's completion gate; the live Google checklist is the authority.

How to use this map

Use the Progress Hub to find your first unfinished Sequence.
Use this page to understand where that Sequence sits in the overall journey.
Open the matching block/card through the Route Navigator or Sequence Finder.
Use the Study Session Launcher to choose how to work the card.
Follow the card—not the diagram—for required resources, stop gates, evidence and completion criteria.

Boundary: this visual is supplemental orientation only. It does not authorize skipping prerequisites, building deferred chapter packages/labs, or marking learner progress.