i wish to address a matter of importance to me, and while this is not a particularly pleasant topic, i hope that you will respond – by replying to this blog entry and letting me know your true feelings on the subject. this entry is about the standards, certification, and the methodology. warning: part of this is a rant, and it may in fact offend you. please read with a grain of salt, and put yourself in my shoes – try to think of this from my perspective, then, please, respond to the post by adding your comments.
first, about the standards…
i could be wrong, but it seems as though there are some people out there in the community who believe they should be the ones “changing, stating, and documenting” the standards for the data vault modeling and methodology.
i’m not opposed to suggestions to changing the standards, but i must say, that it is absolutely vital that if any changes are to be made, that i have the final call on this. otherwise, whomever is proposing the changes may actually re-invent the wheel. in other words, there’s a reason why it took me 10 years of research and design to get the patterns right, i’d hate to see these folks go through the same pain i’ve got – only to break the model, break the standards, all for the sake of change.
now, that’s not to say you can’t propose changes to me, i think you can, and you should – this is how standards evolve over time. i am saying that changes you propose should follow the rules of a scientific experiment. they need to be tested – for performance, durability, stability, pattern analysis, maintenance and complexity ratings, etc… there’s a whole set of tests and procedures that should be undertaken before changes are approved.
i will continue to maintain the tried and true standards of the data vault methodology, however i am open to suggestions – but only after they’ve been exposed to a number of tests, and proven themselves to be enduring.
regarding standards, i’m in the process of creating a “standards board” – involved with individuals who are a) trained, b) certified, c) have proven themselves in the field with experience, and d) come to the table with a wealth of background. while i will have the final say, as well as contributing power on this board, this board will have the power to document and release new standards, and recommended procedures moving forward.
by the way, i maintain a copy of the over-simplified standards. the rest of the standards for the data modeling components have been written in long-format in my technical modeling book, at: http://datavaultalliance.com
and here’s where certification comes in:
i will not recognize any other party who claims to be teaching data vault certification classes, unless they are listed on the authorized trainers page at http://datavaultalliance.com
this means: no other classes, organizations, affiliations, knowledge bodies, or groups will officially be recognized as certification authorities for data vault tests and certifications without approval by me. if you know of an organization or set of individuals performing or claiming that they offer certification, and they are not sanctioned or authorized, then they are not fit, not suited to provide you with anything other than a “certificate of completion”.
more standards and now, the methodology side…
you may think for a minute that the data vault is nothing more than data modeling, and you would be wrong. it’s much richer than just data modeling… it includes a philosophy of implementation, a project based methodology with it’s own rules, it’s own standards, and it’s own mechanisms for “getting your edw right, the first time!”
i’m sorry to stand on my soap-box here, but i’ve been around the block too many times, seen too many edw’s “fail” or not make it, or not cut the mustard, or not be what the business wants – all to be shut-down and re-started, re-architected, re-built, outsourced… you name it.
when i built the data vault model, i built a project methodology around it, based on sei cmmi level 5 principles – that’s why there are soooo many patterns embedded, that’s why it’s repeatable, that’s why the metrics of complexity are very very low, that’s why the implementation phases are generally quite quick, painless, and easy to do. it’s also why there is software available for “generating” loading code patterns.
i can’t begin to stress to you the actual importance of the methodology, and for those of you contemplating changes to the standard structures in the data vault model – don’t! why? because unless you consider the methodology side of the house with your changes and the impacts to the loading, complexity, management, and maintenance, then you will be doing a huge dis-service to the data vault community.
you simply cannot “make a change to the foundational or core architecture” of the data vault structures without considering the impacts on the methodology.
now where’s one more thing that might twist your knickers in a knot…
i’ve not yet written very much about the standards of implementation… there are very few individuals out there who “get it”, or “got-it” and understand what i’ve done. those that do have it, know just how powerful the methodology is, and how powerful it can be when the standards are adhered to. i have great respect for these individuals, and it is these folks whom i will invite to become a part of the data vault standards governance board.
the fact is, unfortunately, due to time limitations, i’ve not written enough about the methodology side of the house to provide for judgements about standards changes, and for understanding the impacts to the implementation methodology. all of this is coming, trust me, i’m working hard on releasing more information that will help expand your knowledge – but i can’t do that if you’re trying to change the data modeling structures and standards underneath…
anyhow, this isn’t a knock on anyone, it’s simply a wake-up call. changing standards, or even suggesting such things is not something that should be taken lightly, and of course as always…
buyer be-ware. if you run into individuals, or writings, or authors of such statements, and they don’t have my seal of approval – then you probably should dismiss their claims as being bogas, or not completely thought through…
am i being a stick-in-the-mud?
yes, and this is because every system i have ever built on the data vault (model & methodology) and every system i ever will build, i will stand on, stand with, point at, and say: i believe in it, it works, i guarantee it.
when was the last time you heard a guarantee from your it staff? let alone the consultant who is proposing “standards changes” to a modeling and methodology system they didn’t create?
i am sorry if i have offended you, but you (and you know whom you are) have continued to try and hide this fact from me. i am willing to work with you to entertain standards changes, but come to me with proven test cases, not just “one-offs” or single instances where “this worked, and this didn’t” i need proof – scalability, real-time, maintenance, complexity ratings, the whole 9 yards…
so you still want to change the standards? great, let’s work together – because teamwork is better than individualism, and more heads are better than one, and yes, i believe there are still great things yet to be done, but please don’t throw the baby out with the bathwater by trying to go around me, forming your own “group” to create standards that may not cut the mustard.