DAMA, the DMBOK, and Why It Exists

DAMA International + DMBOK² in one page

DAMA International is a non-profit founded in 1980 by enterprise data professionals who noticed every company was inventing the same vocabulary from scratch. The DMBOK (Data Management Body of Knowledge, currently DMBOK², 2017) is their flagship deliverable: a shared, vendor-neutral framework that names every discipline of enterprise data management and describes the goals, activities, deliverables, roles, practices, tools and metrics for each.

What DMBOK² actually contains

• The DMBOK Wheel — 11 knowledge areas (KAs) arranged around Data Governance as the hub.
• The Environmental Factors Hexagon — six lenses every KA is examined through: Goals, Activities, Roles, Deliverables, Practices, Tools (plus the cross-cutting Organisation & Culture context).
• Guiding principles — eleven statements that bind the framework together (data is an asset, governance is non-negotiable, metadata is a product, etc.).
• The CDMP certification — the exam track that uses DMBOK as its body of knowledge.

What DMBOK is NOT

• Not a methodology — it tells you what to do, not the prescriptive how.
• Not a tool catalogue — vendors come and go; the practices outlive them.
• Not a compliance regime — GDPR / HIPAA / SOX sit on top, not under it.

Think of DMBOK as the building code for an enterprise's data estate.

A building code doesn't draw your house — it specifies that electrical wiring must be in conduit, that load-bearing walls need a permit, that fire exits are required every N metres. Architects still design any house they like, but the code makes the result inspectable, insurable, and interoperable with the utility grid.

DMBOK does the same for data: each knowledge area is a chapter of the code. You still pick your tools (Snowflake or Databricks, Collibra or DataHub, Informatica or Fivetran) — the framework just ensures the result is inspectable (auditable lineage), insurable (defensible governance) and interoperable (other teams can plug in without a rewrite).

A team that says ‘we don't follow DMBOK because we're agile’ is the equivalent of an architect refusing the building code. The code isn't slowing them down — it's the minimum their insurer will accept.

The DMBOK Wheel — Data Governance at the hub directs the ten surrounding knowledge areas. Cycle through the nodes to see the canonical 11 KAs.