We all intellectually understand that data warehousing is an iterative, not a waterfall, process. Actually, anyone who's been through a successful project or two can attest to this from personal experience. Strict adherence to a project plan with linear development can spell disaster for data warehouse projects. Many well-meaning data warehouse project managers will construct just such a project plan and end up either scrapping the project planning period, taking the project into the untrackable zone, or will stick it out until the bitter end. So, isn't there a place for a project plan in data warehousing? There absolutely is, with these caveats that accommodate its iterative nature:
- Major items, like data modeling, source-target modeling, end-user environment setup, source system analysis, etc. have 3-4 development cycles.
- Each of these development cycles are actually full deliverables (like a complete data model) and not just steps in the process of delivering the item.
- The complete cycles run until the deliverable can be considered final and therefore there may be more (or fewer) cycles than the 3-4 on the initial plan.
- Major activities run in parallel and are allowed to start when resources can get to it instead of waiting for other activities to complete. Seldom will this result in wasted effort.
As a consequence of #1 above, most appropriate data warehouse project plans are much larger than what
Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.
Hannah Smalltree, Editorial Director
This was first published in October 2001
Join the conversationComment
Share
Comments
Results
Contribute to the conversation