What Is DAMA-DMBOK?

DAMA-DMBOK, the Data Management Body of Knowledge, is the reference guide to data management published by DAMA International, a vendor-independent, not-for-profit association of data management professionals. It defines what data management is, breaks it into knowledge areas, and describes the goals, activities, roles, and deliverables of each one. It is the closest thing the data profession has to a shared textbook, and it is the knowledge base behind DAMA's Certified Data Management Professional (CDMP) certification.

Most people meet DMBOK through its best-known picture, the DAMA Wheel: data governance in the center, surrounded by the other knowledge areas it steers. That picture explains why the framework is cited so often in governance programs. It gives everyone, from engineers to executives, a common map of what "managing data" actually includes, and it shows governance as the function that holds the rest together.

DAMA-DMBOK Defined

DMBOK is a body of knowledge, which is a specific kind of document. It does not tell you which tool to buy or the exact order of steps to follow. It describes the generally accepted scope, concepts, and practices of a profession, the way comparable bodies of knowledge do for project management or business analysis.

Three ideas carry most of its value:

• A broad definition of data management. DMBOK treats data management as the development, execution, and supervision of the plans, policies, programs, and practices that deliver, control, protect, and enhance the value of data across its lifecycle. The breadth is deliberate: strategy and architecture are in scope as much as daily operations.
• A decomposition into knowledge areas. Data management is split into areas with distinct goals and skills, so programs can be scoped, staffed, and assessed area by area.
• Governance at the center. Data governance is the knowledge area concerned with authority and control over how data is managed. Every other area depends on it for decision rights, policies, and accountability. The practical difference is explained in data governance vs data management.

The 11 Knowledge Areas

DMBOK2 organizes data management into eleven knowledge areas. Data governance sits in the middle; the other ten surround it.

• Data Governance - authority, control, and shared decision-making over data management: roles, policies, standards, and oversight. See the data governance framework, operating model, and data governance policy.
• Data Architecture - the blueprint for data assets and data flows, aligned with business strategy.
• Data Modeling and Design - discovering, analyzing, and representing data requirements as models.
• Data Storage and Operations - design, implementation, and support of stored data across its lifecycle.
• Data Security - policies and controls that protect data and ensure appropriate access.
• Data Integration and Interoperability - moving and consolidating data within and between systems.
• Document and Content Management - managing unstructured data such as documents, records, and content.
• Reference and Master Data - managing shared core data such as customers, products, and code lists, often through master data management.
• Data Warehousing and Business Intelligence - analytical data stores and the reporting built on them.
• Metadata Management - collecting, integrating, and providing access to data about data. See metadata management.
• Data Quality - planning and applying quality management so data is fit for its intended use. See data quality management.

How Each Area Is Described

Part of what makes DMBOK useful is its consistency. Every knowledge area is presented through a context diagram with the same building blocks, so a reader can compare areas like for like:

• Definition and goals - what the area is and what it is meant to achieve.
• Business drivers - why an organization invests in it.
• Inputs and deliverables - what the area consumes and what it produces.
• Activities - the work, grouped into planning, development, operational, and control activities.
• Suppliers, participants, and consumers - the roles involved on each side of the work.
• Techniques, tools, and metrics - how the work is done and how it is measured.

This structure is what makes DMBOK practical as a planning aid. For any area, a team can ask whether it has the roles, the deliverables, and the metrics the context diagram describes, and see where the gaps are.

Editions & DMBOK 3.0

The current edition is the second, known as DMBOK2. In 2024 DAMA International released a revision of DMBOK 2.0, which it describes as a maintenance release. According to DAMA, no material changes were made to the overarching framework, the knowledge areas, or their definitions. The revision focused on clarity and consistency:

• Terminology and acronyms were unified, and the context diagrams were redrawn.
• The "data governance program" became the data governance function, reflecting governance as a permanent capability rather than a project.
• AI governance and ethics were added to the data governance material, and the definition of the data owner was made more explicit.
• The data quality chapter gained clearer dimension tables, with currency added as a quality dimension.

In parallel, DAMA started the DAMA-DMBOK 3.0 project, with a kick-off on June 25, 2025. DAMA describes it as a community-driven modernization that will incorporate emerging topics such as AI, cloud, and modern data platforms while keeping the foundational principles. An editorial board of specialty editors develops the content, and a panel of CDMP Masters reviews it. DAMA has not published a release date on its project page, so DMBOK2 in its revised form remains the reference for now.

How Organizations Use It

Few organizations implement DMBOK end to end. Its value is in the ways it gets reused:

• A shared vocabulary. When engineers, governance leads, and auditors use DMBOK terms, a conversation about "metadata management" or "reference data" means the same thing to everyone.
• Program scoping. The knowledge areas work as a checklist for what a data strategy should address, and help explain to executives why governance needs more than a tool purchase.
• Role design. The participants in each context diagram give a starting point for job descriptions and for the governance operating model.
• Maturity and gap assessment. Many organizations rate themselves area by area against DMBOK practices as an input to a governance framework roadmap.
• Professional certification. DMBOK is the knowledge base for DAMA's Certified Data Management Professional (CDMP) program. DAMA is explicit that the DMBOK itself is not a certification; CDMP is the credential built on top of it.

DMBOK vs DCAM

DMBOK is often mentioned alongside DCAM, the Data Management Capability Assessment Model from the EDM Council. They answer different questions and are frequently used together.

• DMBOK describes the discipline. It is a body of knowledge: what data management includes, how each area works, and which roles and practices are involved.
• DCAM measures capability. It is an assessment framework that scores how mature an organization's data management capabilities are against defined criteria, originally with a strong financial services focus.
• In practice: teams use DMBOK to understand and design the program and DCAM, or a similar maturity model, to benchmark progress and report it to leadership.

For the wider picture of how these references fit into a governance program, see the data governance framework article.

Where Dawiso Maps

Dawiso does not cover all eleven knowledge areas, and no single platform does. It is a data governance and metadata platform, so it maps most directly to the center of the wheel and the areas closest to it:

• Data Governance. Ownership and stewardship assigned to real assets, plus configurable workflows with states such as draft, review, and approved, so decisions are recorded where the data is.
• Metadata Management. The data catalog documents assets across connected sources, and interactive data lineage shows how data flows between them.
• Shared business meaning. The business glossary holds governed definitions linked to the technical assets that implement them, which supports the definitions work that runs through governance, data quality, and reference data.

The remaining areas, such as storage, integration, security enforcement, and warehousing, are run in your data platforms. Dawiso connects to them as the place where their assets are described, owned, and governed.

Conclusion

DAMA-DMBOK is the reference map of data management: eleven knowledge areas, with data governance at the center, each described through the same context diagram. Its current edition, DMBOK2, was refreshed in 2024 without changing the framework, and a DMBOK 3.0 project is under way to add AI, cloud, and modern platforms. Treat it as a shared vocabulary and a checklist rather than a recipe. Use it to scope your program and design roles, pair it with a maturity model to measure progress, and put the governance and metadata areas into daily practice first, because every other area depends on them.

Sources

• DAMA International - DAMA Data Management Body of Knowledge (DAMA-DMBOK)
• DAMA International - The 2024 Revision of the DAMA-DMBOK 2.0
• DAMA International - DAMA-DMBOK 3.0 Project
• DAMA International - Certified Data Management Professional (CDMP)
• EDM Council - DCAM: Data Management Capability Assessment Model