The difference is that this “lifecycle” is now assigned to a 2-week sprint, with disciplined
agile delivery (DAD) overseeing the process.

There are several components to how this fits in with the Data Vault 2.0 methodology.
First, there is the master project—the overall enterprise-wide vision. This generally
consists of a multiyear, large-scale effort (for large enterprises). These projects are then
often broken into subprojects (as they should be), with outlined goals and objectives
within 6-month time frames.

Then, the subprojects should be broken into 2-week sprint cycles (to meet agile
requirements). The idea is to not have the project levels become top-heavy and full of
planning, but rather to act as an overall guide or map from start to finish in terms of what
the enterprise business intelligence solution needs to provide.

At the end of the day, project managers should have a firm grasp on what they are
managing (CMMI), how they will manage the people (agile/Scrum/DAD), how the sprints
have to be lined up in order to accomplish the goals and objectives of the enterprise, and
how to measure the success/failure of particular parts of the process. Otherwise, without
hindsight or measurement, then there will be no room for improvement or optimization.

So Then, What Does Six Sigma Contribute to the Data

Vault 2 Methodology?

Six Sigma is defined to be

Six Sigma seeks to improve the quality of process outputs by identifying and removing
the causes of defects (errors) and minimizing variability in manufacturing and business
processes. It uses a set of quality management methods, including statistical methods, and
creates a special infrastructure of people within the organization ("Champions,” "Black
Belts,” "Green Belts,” "Yellow Belts,” etc.) who are experts in these
methods.http://en.wikipedia.org/wiki/Six_Sigma

To paraphrase for enterprise BI projects, Six Sigma is all about measuring and eliminating
defects that plague the enterprise warehouse build process. Data Vault 2.0 methodology
attaches Six Sigma school of thought to the metrics that are captured in the life cycle of
each sprint (i.e., the KPIs and the Scrum review process—what’s broken, why, and how
do we fix it).

Chapter 6.4: Introduction to Data Vault Methodology