Heros of this blog

There are two heroes of this blog, whom I’ve mentioned a couple of time. They finally arrived on this blog and left some comments. Actually in Jan 2008.

Gurvinder Singh Chhatwal (Project Manager of MicroStrategy-QA project in Cybage, Pune)
“At least a MILLION times people around you, who have worked and lived with you have told you what an IDIOT you are. But seems you still fail to understand.
Pity on you.”

Paramjeet Singh Sidhu (Project Lead of MicroStrategy-QA project in Cybage, Pune)
“No wonder you write all bullshit about the people you work with because they all know how sick your thoughts and you were (seems like you still are). Anywayz, you and your fantasies go on and on.
May god help you.”
———
People like you give me good learning. I’ll not forget Cybage because of people like you. I owe you this. I pity having worked under you guys. I don’t think I’ll ever get any manager like you and pray to god that no one in this world gets it. and who was/is sick is known to persons concerned. May god help both of you. Last but not least, thanks for stopping by on the blog.

Data Modelling questions

Goal Alignment queries:

  • What is the strategic goal of the organization that is being addressed by this particular activity?
  • What organizational mission/vision does it relate to?
  • Do we have a hypothesis as to how this initiative will eventually improve results / performance (i.e. a strategy map)?

Baseline queries:

  • What is the existing level of performance? Do we know or have the capability to know (monitoring capability)?
  • Are we collecting this data and storing it somewhere?
  • What are the statistical parameters of this data, e.g. how much random variation does it contain? Are we measuring this?

Cost and risk queries:

  • What is the existing cost of present operations?
  • How much will that increase when we go ahead with the initiative?
  • What is the risk that this cost will be exceeded or achieved? Have we performed a similar sensitivity analysis on this?
  • Is the money being spent on this preset initiative the best use of the funds, or is there a better alternative usage?
  • What is the risk that the initiative will fail? Has this assessment been included in the planning?

Customer and Stakeholder queries:

  • Have you listed all the communities of interest that have a stake in this present initiative?
  • Who are the kinds of customers/stakeholders who will benefit directly from this initiative? Who will benefit indirectly? What are the quantitative / qualitative benefits?
  • Is the specified initiative the best way to increase satisfaction for all kinds of customers, or is there a better way?
  • How will we know that the initiative benefits these customers?

Metrics related queries:

  • What metrics will be used to define the benefit?
  • Are these the best metrics? How do we know that?
  • How many metrics need to be tracked? If this is a large number (it usually is), what kind of system are you planning to use to track them?
  • Are the metrics standardized, so they can be benchmarked against performance in other organizations? What are the industry standard metrics available?

Measurement Methodology related queries:

  • How will the metrics be measured? What methods will be used, and how frequently will data be collected? Are there any industry standards for this?
  • Is this the best way to do the measurements? How do we know that?

Results related queries:

  • How can we demonstrate that this strategic initiative, and not something else, contributed to a change in results?
  • How much of the change was probably random?

Version control in MicroStrategy

MicroStrategy doesn’t support Versioning. BTW, There are two types of versioning in MicroStrategy. Source control (what I’m taking about over here) and Slowly changing dimension (SCD). Lots of clients have put requests to MicroStrategy to have this feature of version control for schema object or at least attributes. In short the answer for this question is NO and I would never want MicroStrategy to have this features. Such a feature request is only idea that can come from bad MicroStrategy practice. Why in this world, do you want to have two definition. If a change in attribute breaks a report or sql goes haywire, one should rather fix this (that why it is job of MicroStrategy Architect). Such a feature would lead to lots of useless trial-n-error stuff in MicroStrategy. If you know any company who is behind this feature request, please post the name over here.

FYI, as per document ID (TN4100-800-0349), A current enhancement request exists for this functionality. Contact MicroStrategy Technical Support for the latest update of this request.

This would be a good feature for nuts in MicroStrategy and will give sane people hard time.

Update 13 Feb 2009

Cognos supports this feature. But one can’t use different object(s) from different set of version. :-(