Page 249 - Data Architecture

Chapter 6.4: Introduction to Data Vault Methodology
The second component is the recording of business requirement meetings. All business
requirement meeting “time” can be shortened, and the quality of the requirements
increases when the meetings themselves are actually recorded utilizing an MP3 recorder.
The audio files should be submitted to the wiki, so that team members (if out of the

office) can retroactively attend or review when necessary.

This leads to a more agile business requirement meeting. Noise makers in these meetings

tend to be quiet when it is recorded until or unless they have a significant contribution to
make that would impact the outcome of the project goals. Please note that the rest of the
explanation of how and why this works is beyond the scope of this book and is available
in Data Vault 2.0 Boot Camp training classes and online at http://LearnDataVault.com.

If CMMI Is So Great, Why Should We Care About

Agility Then?

Agility and Scrum or disciplined agile delivery (DAD) is still necessary to manage the
individual sprint cycles or miniprojects that need to occur. CMMI manages the overall
enterprise goals and provides a baseline consistency to the enterprise-wide efforts—so
everyone in IT is on the same page (at least those involved with the BI project).

An agile implementation should be tailored to match an organization's actual maturity
level; however, implementing agile when an organization is at CMMI level three can
result in less rework and improve the overall CMMI initiative while providing the
significant benefits of agile. Implementing a CMMI compliant software development
process that is also agile will bring the repeatability and predictability offered by CMMI.

Agile, by design, is highly adaptable and therefore can be molded into a CMMI-compliant
software development process without altering the primary objectives set forth by the
Agile Manifesto.https://www.scrumalliance.org/community/articles/2008/july/agile-and-
cmmi-better-together

Please keep in mind that teams don’t wake up one day and just decide to be agile right
there on the spot. It's an evolutionary process; the team must undergo training both in
agile and in Data Vault 2.0 methodology in order to achieve the desired goals. Most
teams that undertake training with Data Vault 2.0 start with 7-week sprint cycles (if they
have had zero exposure to CMMI and agile previously).

Usually, the second sprint cycle reduces 7 weeks to 6 weeks. The third (if the team is
working in earnest and measuring their productivity and following the agile and Scrum
249