Skip to content

Applied Labs

Drive folder: https://drive.google.com/drive/folders/1tnQkcpBu8r5qSdtH8A0Wi2xYulc-8ilS

← 00B Home

This is the canonical GitHub entry point for Meridian applied labs.

Current executable chapter lab

Deferred chapter labs

Chapters 2–17 are USER-DEFERRED. Their Drive/source folders may exist for future use, but no substantive applied-lab package should be authored merely because a folder exists. Build each later lab only after the user deliberately starts that chapter and its controlling DMBOK mastery package has passed source QC.

Cross-Chapter Capstones & Incidents

  • Capstone Roadmap — roadmap is online and source-gated.
  • Authoritative formatted roadmap: Google Doc · PDF
  • Drive folder: https://drive.google.com/drive/folders/1wFauMYRFBEJmAkmQKl1GrYJBwqgvSeXo

The roadmap may identify future integrated cases, but detailed capstone execution packages are not activated until the necessary chapter foundations exist and 00C reaches the relevant gate.

Historical chapter-lab tree

An earlier three-part Chapter 1 lab remains under chapter-labs/ as a legacy/superseded working structure. It is not the current learner route. The canonical Chapter 1 lab is the direct chapter-01-data-management/ package above.

Source-gate rule

A chapter-specific lab is not finalized from memory. The controlling DMBOK chapter must be fully read and blueprinted first. Meridian supplies the scenario, data, tools, and implementation design, while DAMA-specific meaning remains controlled by the source chapter.

Lab completion rule

Every applied lab follows the internal 00B control standard:

DMBOK target → business situation → prerequisite gate → predict → perform → interpret → vary/break → repair → independent rebuild → evidence → DMBOK debrief → retrieval/scenario check.

Use the 00B Internal Control Center for lab-build/evidence/QC standards and 00C for the learner’s integrated execution order.