Databases Reference
In-Depth Information
may be excited and highly motivated to help get the data warehouse built.
Other groups may be more reserved and have serious doubts. In some cases,
legitimate issues are raised. The sooner the team is aware of potential problems
the better. In other cases, concerns may be due to a lack of understanding
of the project, about data warehousing in general, or uncertainty about the
project's impact on the work environment. The project team may need to take
specific actions to address concerns in either case.
If a group has been starved for data, it may be necessary to spend more
time educating and showing demonstrations. This may be more useful closer
to delivery of the completed data warehouse. If this group is needed to help
the design and development of the data warehouse, then the education must
happen soon so that they can be more effective throughout the life of the
project.
Complete Picture of the Data
Get a comprehensive list of the business data that is needed. This needs to
include a description of the data, and if this is already being captured, then
note the actual name of the system. Any primary concerns and issues with this
as a data source should also be documented here. This should include data
from major operational systems, information data sources, and data that is not
currently being captured. The purpose is to get a broad view of all the data
that would be useful. This is not a commitment that this project will address
all of these sources, but it does acknowledge the need.
What If No One Is Asking?
If there is a data warehouse project in process, and no one is talking to any-
one in the business community, then this is a major problem. Someone from
the business community must be proactive and get involved. This could be the
business champion, a strong business manager, or perhaps the executive spon-
sor. While this may be disruptive to the current project, business involvement
now will save time and money later. This may also mean the difference
between success and failure.
Start by looking at the project scope and objectives. Review where the
project is in the life cycle. Is it just starting, in the middle of developing the
staging processes, or just about to be deployed? Other business groups may
be participating, but for some reason your group was excluded. This may be
due to project scope or it may simply be an oversight.
It is never too late for the business and IT groups to begin working closely
together. Make an honest assessment of what you have and where you are as
an organization. Even when you already have a data mart in production, it is
still useful to take stock of what you have. Then, specific plans can be made to
move the data warehouse forward.
