Q:  

How does one create a methodology to develop a data warehouse in a country where theconcept and technology have never been implemented. What steps do we need to take?

A:  

Sid Adelman’s Answer: There are some companies (and possibly some countries) that are so disaffected with the concept of methodology that any such suggestion you make will get you immediately disemboweled. The term "methodology" may carry some undesirable baggage and so it may be wise to find some other way of describing it.

Your first step has to be the listing of the benefits of a methodology. Once your company accepts the benefits, it shouldn’t be too difficult to sell them on using a methodology, but make sure that the methodology you use is useful and contributes to the success of the project.

If there are portions of the methodology that are inappropriate for your project, leave them out. Don’t feel you need to respond to all parts of the methodology. If the methodology just translates into a make-work effort with no tangible benefits, you are either using the wrong methodology or using the right methodology incorrectly.

Be sure the methodology is specifically designed for a data warehouse. Trying to force fit a data warehouse into a methodology designed for operational systems is the wrong approach and almost always fails.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access