Data Mart Business Theme Matrix

Data Mart Business Theme Matrix

Data-Mart here is one single Data Warehouse schema, a combination of interlinked fact table(s) and dimension table(s), in the overall Data Warehouse design. Each Data Warehouse can have many such schemas.These Data-Marts (OR schemas) can reside in any layer of Data Warehouse OR Data-Mart OR both, depending upon the Data Warehouse Architecture Scenarios

Data Mart Business Theme Matrix is created by picking-up all the business themes, requirements and specifications documents, and placing the business themes on one axis and the data marts on the other.

The matrix will contain:

• All the Data Warehouse business themes (within and out of phase I and II).
• All the Data Marts titles.
• The Descriptive objectives of the Data Marts.
• Phase of the Data Mart.

Identify the Data Warehouse Business themes

Though the stages a typical IT systems development and a Data Warehouse are similar, however, the methodology and approach at ground level is significantly different.

The difference between a Data Warehouse and a business application is that a business application has clear deliverables, actions, functions that any process manager can relate to. Most of the business applications deal with operational domain, whether back-end OR front-end (field) operations.
However, data-warehouse provides data to applications which help in decision, analysis, performance management, which take it into the realm of management, leadership and strategy. As we move into these plains, the project needs to manage high level of ambiguities, and more subtle needs and considerations. That�s why Data Warehouse initiatives need a higher level of change management.

Once we have the 'Go Ahead' on the project initiation, the core stakeholders' team is established and sponsor is identified, we list out the business objectives. These objectives will be mostly worked out in the back-end by going through.

• Management presentations.
• Organization Business Plans.
• The existing MIS and Scorecards being generated.
• Any strategy documents.
• Goal sheets of key management personnel.

The examples of the Data Warehouse business themes can be as follows:

• Maximize profitability of business portfolio.
• Maximize the value from the existing customer set.
• Maximize the annual renewals of the product.

Prioritization of Data Warehouse Themes for project scoping

While listing out the business themes, the following points needs to be ensured :

• The themes are distinct, and logically ground with least overlap with other themes.
• Each theme has to have an owner.
• Each theme should be mapped with the specific business plan parameter, measure of success OR a goal sheet.
• The potential business impact against each theme is listed out.
• Major themes/perspective like Revenue, Productivity, Cost, effectiveness, enhanced service and reputation are covered.
• Don�t list the business impact in terms of High/medium/Low. Let this be highlighted by the business stakeholders/Sponsors.
• The Expected cost and time impact for developing the theme to be listed out. This is worked out depending upon the readiness level (refer 'Data Warehouse Readiness Assessment' chapter), and size of work involved with the theme.
• The stakeholders against each theme are listed out.

Once this set of ready, we should call the stakeholder session, where the theme listing along with all the associated information is presented, for prioritization. The first track is to identify the business prioritization. Two possible challenges in this track are:

• All themes are marked, as high- Best way to handle is to ask people to mark their 'Top 3' themes.
• The stakeholders taking a 'functional' view only � Check with functional heads to mark the 'top 3' themes, which are linked to their function.

The second track is the do-ability/feasibility/cost/time impact of addressing a given theme. There is a debate on if we should share the do-ability with the business owners, while they are working out the business impact? This can make them float towards 'higher feasibility' themes, as they know that low feasibility items will any way not be delivered. BiPMinstitute.com vote would be to share this information, as the do-ability at that stage is purely indicative.