Databases Reference
In-Depth Information
mechanism to acknowledge what will actually be developed and delivered,
which may not be what was originally planned.
Too often, change control procedures are used only when there are increased
costs for a project. This is indeed the mechanism by which additional funding
is approved, but this is not the only way change control can help. Formal
change control procedures should also be used when there are modifications
to the scope of a project, or perhaps what data is included, that do not change
the cost or schedule. This is a mechanism to ensure that everyone has a
common understanding of what the project will deliver. These formal project
changes are a natural result of the business and IT team members learning and
adjusting as the project progresses. Successful projects use change control to
manage expectations and to communicate how the project will meet business
objectives.
Discussing Change in Business Terms
Many choices need to be made throughout the life of any data warehouse
project. The biggest decisions are often made when the project charter and
scope are crafted. The dozens of smaller decisions, however, can add up in
surprising ways, and it is unrealistic to expect IT staff members to make most
of these decisions. Clearly, technical decisions should be made by IT — after
all, this is their specialty. However, decisions about what data is important,
the rules to integrate data or determine business calculations, are not their
responsibility. These decisions must be made by the business. In order for
good decisions to be made, everyone involved must understand the question
at hand and the potential ramifications.
The project team must be able to articulate the question or problem and,
when possible, offer several alternative solutions. The problems need to be
communicated in terms that make sense to the business community. It is
critical that the ramifications of each alternative also be communicated in
business terms. Several examples are provided in Table 5-1 to demonstrate
how to communicate in business terms and to share the impact of a problem
or question. When possible, this translation should be done prior to meeting
with the business decision-maker.
From a business or management perspective, you may need to take the lead
to ensure that questions are posed in business terms. Keep asking questions
until the problem is clear enough that you feel comfortable making a decision.
As you work with more technical team members, they will learn what you
expect and, over time, be more prepared to clarify their concerns.
