Continue in 2 seconds

Should I use a work breakdown structure in a data warehouse project?

By
  • Joe Oates, Sid Adelman, Chuck Kelley, Clay Rehm, Les Barbusinski
Published
  • December 09 2003, 1:00am EST

Q:

Should I use a work breakdown structure in a data warehouse project?

A:

Sid Adelman's Answer: Yes, a work breakdown structure (WBS) is appropriate in a data warehouse project. The Business Intelligence Roadmap by Larissa Moss and Shaku Atre has a very comprehensive WBS in both paper and electronic form.

Les Barbusinski's Answer: Absolutely. You can find template DW work breakdown structures in The Data Warehouse Lifecycle Toolkit (by Ralph Kimball and Margy Ross), The Business Intelligence Roadmap (by Larissa Moss and Shaku Atre), among other sources.

Chuck Kelley's Answer: Absolutely, as long as it can be somewhat fluid.

Joe Oates' Answer: Of course! The work breakdown structure (WBS) is the basis of the project plan. How well the project manager does this is a key factor in whether the project will be successful.

Most first-time data warehouse project managers don't know how to do this. Fortunately, there are some sources that can help you put together an adequate data warehouse project plan. Just a few are listed below:

Clay Rehm's Answer: Absolutely!! A Work breakdown structure (WBS) is an absolute necessity for every project - it provides what is in scope and what is not in scope. It does NOT specify who is doing the work or when it is done - that is found in a Gantt Chart. Go to www.PMI.org for more information.

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