Page 248 - Data Architecture

Chapter 6.4: Introduction to Data Vault Methodology
first managing the project.

The road to agility is paved with metrics and well-defined/well-understood business
processes. The Data Vault 2.0 methodology relies on the necessary components of CMMI
in order to establish a solid foundation on which to build and automate enterprise
business intelligence systems.

Taking a step back, here is a simplified definition of what CMMI cares about:

In CMMI, process management is the central theme. It represents learning and honesty as
demonstrated through work according to a process. Process also enables transparency by
communicating how work should be done. Such transparency is within the project, among
projects, and being clear about expectations. Also, measurement is part of process and

product management and provides the information needed to make decisions that guide
product development.
http://resources.sei.cmu.edu/asset_files/TechnicalNote/2008_004_001_14924.pdf
Page 17

CMMI brings consistency to the processes; it also brings manageability, documentation,
and cost control. CMMI helps the people assigned to the project execute with a specific
quality metric in mind. It also assists with the measurements of those metrics by
identifying common processes that must happen in every business intelligence system.

CMMI provides the framework to operate within. Teams implementing Data Vault 2.0
methodology inherit the best parts of CMMI level 5 specifications and can successfully
hit the ground running. Why? Because Data Vault 2.0 methodology provides the
transparency, defines many of the KPAs and KPIs, and also enriches the project process
by allocating template-based predefined deliverables, utilized during the implementation
phases.

Transparency is implemented in the Data Vault 2.0 projects in different manners. The
first recommendation for teams is to set up an in-company wiki, one that can reach any
and all employees (including executives) in the firm. All meetings, all models, all

templates, designs, metadata, and documentation should be recorded in the wiki.

The wiki should be updated at least once a day (if not more) by different members of the

team. There will be more updates at the start or kickoff of new projects than at any other
time during the life cycle. This should indicate a level of communication (which is
stressed in agile/Scrum) with the business users.

248