My group and I are working on the business case for the datawarehouse. I'm inclined to include the glossary of DW terms as the sponsor indicated he'd be interested in learning about the terms, so that the executive team are up to speed in the techie language. Any thoughts? Saving Changes...
Sort By:
Ketan KarkhanisKetan A Karkhanis| CiscoSunnyvale, Ca, United States
If you include a glossary do Not make it all encompassing.
The longer the list the less chance anyone will read it. You can make them aware of the techie language, but you will never get them upto speed. In fact it may create some confusion and mis-understanding
I would also recommend that in all your presentations DO not use any TECHNICAL data warehousing term unless you really really have to. Just use plain English.
E.g instead of saying Dimensions, say the data can be sliced and diced using several filters, instead of saying data can be grouped by Time Hierarchy, just say you can run reports for fiscal quarters.
As one of my Econ professor in MBA school used to say , explain it to me the way you would explain it to your Mom :-)
Best Luck ...
Saving Changes...
Hans RobbersSenior Director| SalesforceVlissingen, Netherlands
Rajib
I do agree with Ketan. A list with common terms and abbreviations in the business case explained in non-tech language. The desire is to understand more of the DW project and terms not to become a techy.
By understanding the language he aims to be able to remain in control/manage/monitor progress
