|
In-spite of you wishing otherwise, maximizing existing Data Warehouse and working on its growth typically happens in parallel. Somewhere during the project an expectation gets created that Data Warehouse is the magic pill for all out information ailments, and it can be granularly evolved. Visible groups of power users will start demanding more and more information, and their needs have to be managed. The following aspects can be considered:
Steering team and project office should be maintained
The Data Warehouse project implementation is not the end, but the beginning. The requirements are going to be more complex and more urgent, as people have tasted the blood. One should maintain the process of gathering new requirements through a 'Data Warehouse Change Management Process' and 'End User Tools Change Management Process'.
Keeping track of new locations, new products, new channels and key initiatives
As a Data Warehouse sponsor and project manager, one should keep one’s eyes and ears open, to major initiatives and launches planned OR are in progress. Most of the initiatives need data during there analyze phase and also have data as a core need for their post-implementation success.
Leverage on an information management council
These are the people who are more than users. They are tasked to educate users, help in smoothening the difference between what users want and what Data Warehouse can deliver and also help prioritizing the
|
