clement13.net
Original photo: The reading room of the Library of Congress
Description
The reading room of the Library of Congress
Source
Carol M. Highsmith · original page
Licence
PD Public domain
Original photo, unretouched. The background is a version of it stylised by the site.

Data governance — DAMA-DMBOK

How do you place an organization's data management maturity, area by area, with the DAMA-DMBOK framework?

≈ 3 min readReading
At a glance
  • Scale from 0 to 5.
  • 11 areas assessed separately.
  • Assess with evidence, set a target per area.
On this page
  1. Profile
  2. Why this matrix matters in my field
  3. The maturity scale
    1. No capability
    2. Initial (Initial / ad hoc)
    3. Repeatable
    4. Defined
    5. Managed
    6. Optimized
  4. The dimensions assessed
    1. Data Governance
    2. Data Architecture
    3. Data Modeling and Design
    4. Data Storage and Operations
    5. Data Security
    6. Data Integration and Interoperability
    7. Document and Content Management
    8. Reference and Master Data
    9. Data Warehousing and Business Intelligence
    10. Metadata
    11. Data Quality
  5. How to use it
  6. Limitations and precautions
  7. Sources and verification

Profile#

Organization
DAMA International (Data Management Association)
Framework
DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (DMBOK2, 2017), Technics Publications
Purpose of the grid
Assess data management maturity across the 11 DMBOK2 knowledge areas (chapter devoted to maturity assessment)
Scale
6 levels, from 0 (no capability) to 5 (optimized)
Dimensions
11 knowledge areas
Access
Paid book; the detailed grids are in the book

Why this matrix matters in my field#

The DMBOK2 is the profession's reference for vocabulary: it sets what “managing data” covers. Its maturity grid lets you say, area by area, where you stand — governance, modeling, quality, metadata, integration, security, data warehousing and BI. For anyone designing decision-support platforms, it is the framework that links the technical side (model, pipeline, warehouse) to the organizational side (roles, policies, quality).

The maturity scale#

The DMBOK2 assessment relies on a six-level scale, in the spirit of CMMI. The wording below is a synthesis; the exact titles and their criteria should be checked in the book.

  1. No capability#

    No recognizable practice in the area.

  2. Initial (Initial / ad hoc)#

    Ad hoc, person-dependent responses. Little or no documentation; successes are not repeatable.

  3. Repeatable#

    Minimal processes exist and are followed in some teams; repeatability still depends on local discipline.

  4. Defined#

    Processes, standards and roles are formalized and applied consistently across the organization.

  5. Managed#

    Processes are measured and driven by indicators; deviations trigger action.

  6. Optimized#

    Continuous improvement is tooled and automated; processes evolve based on measurements.

The dimensions assessed#

The 11 DMBOK2 knowledge areas; each area can be assessed at its own level.

  • Data Governance#

    Decisions, roles, policies and accountabilities around data; at the center of the framework.

  • Data Architecture#

    Blueprint and overall structures of the organization's data.

  • Data Modeling and Design#

    Conceptual, logical and physical models; reasoned normalization and denormalization.

  • Data Storage and Operations#

    Databases, administration, availability, performance, backups.

  • Data Security#

    Confidentiality, integrity, availability, access and compliance.

  • Data Integration and Interoperability#

    Moving, consolidating and exchanging data between systems.

  • Document and Content Management#

    Unstructured data: documents, content, life cycle.

  • Reference and Master Data#

    Shared reference data, single identity of entities, quality of master data.

  • Data Warehousing and Business Intelligence#

    Warehousing, reporting and decision-support analysis.

  • Metadata#

    Glossaries, catalogs, dictionaries, lineage.

  • Data Quality#

    Defining, measuring and improving quality according to uses.

How to use it#

  1. Choose the scope: the whole organization, a division, a data product.
  2. For each area, collect evidence (documents, dashboards, logs, interviews), not impressions.
  3. Assign a level per area; avoid computing a single average that would hide the gaps.
  4. Set a target per area, justified by a business stake or a risk.
  5. Plan stages and reassess at regular intervals.

Limitations and precautions#

  • A high level is not a universal goal: aiming for “Optimized” everywhere is rarely cost-effective.
  • The grid measures organizational capabilities, not the quality of a given dataset.
  • Self-assessment tends to be optimistic; see the Dunning-Kruger effect.
  • Level names may vary from one edition or adaptation to another: always cite the edition used.

Sources and verification#