Program Curriculum & Roadmaps
Drive folder: https://drive.google.com/drive/folders/1xlNQDavGJKN8NNQyX86w4-Rc0a7nGE0m
Authoritative formatted sources: Google Doc — Chapter-to-Lab Curriculum Map · PDF
Curriculum rule
The chapters should not all become SQL labs. Code is used when code makes the concept observable. Decision, governance, document, architecture, maturity, and change chapters use the medium that best represents the DMBOK concept. Meridian remains the same company so later labs can reuse and complicate earlier work rather than resetting the story.
This curriculum is a design map, not a replacement for the DMBOK and not an authorization to start later chapter production. Every final chapter lab must be source-checked against that chapter PDF before learner use.
Current build boundary: Chapter 1 is the only substantively built chapter package. Chapters 2–17 are USER-DEFERRED until the user deliberately starts the relevant chapter. The future curriculum pages may remain online as planning architecture only.
Online curriculum
- Chapters 1–8 — Foundation and Relational Core
- Chapters 9–17 — Information Products and Organizational Synthesis
Four-stage applied progression
| Stage | Chapters | Applied focus |
|---|---|---|
| Foundation | 1–4 | Company diagnosis, ethics, governance, architecture — learn to see the enterprise before building. |
| Relational core | 5–8 | Model, implement, operate, secure, and integrate the data environment. |
| Information products | 9–13 | Content, master/reference data, analytics, Metadata, and Data Quality — build trust and context. |
| Scale & organizational synthesis | 14–17 | Big-data awareness, maturity, roles, and change — assess and institutionalize the system. |
These stages describe future program architecture; they do not mean those later chapters are currently built or ready for execution.
Technical-intensity pattern
- Low: judgment/organizational reasoning dominates; technology is optional/supportive.
- Medium: some hands-on inspection or practical tooling, but the management artifact remains central.
- High: technical work makes the DMBOK concept concrete, with explicit prerequisite and stop boundaries.
Carry-forward rule
Use artifacts/data from earlier Meridian labs wherever genuinely relevant once later chapters are intentionally built. Do not reset the company unless a lab intentionally requires a clean baseline.
Source gate
Every later chapter entry is provisional curriculum design until the controlling DMBOK chapter has been completely read and blueprinted. Only that source may establish DAMA-specific rules, roles, process names, required sequences, metrics, or distinctions.