Business intelligence and data warehousing team structure
How do most people structure BI/DW teams? Who do we want on the team? What's the typical chain of command? Are they part of the IT department?

    Requires Free Membership to View

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on the hottest data and information management trends today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchDataManagement.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataManagement.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Business intelligence/data warehousing teams are constructed quite differently from shop to shop. The most common placement is within IT, although recently I've noticed more in the CFO's area instead.

In business intelligence and data warehousing teams, there is a Director, a Technical Lead (which is somebody that oversees the architecture and can roam into multiple of the other positions), ETL developers (typically mutliple of these) and data access developers. Data modelers may also be a distinct role, or modeling may be done by the Technical Lead. Business analysis is required and may be done by the modeler in small shops. The Physical DBA/System Admininstration needs are generally done by service level agreement (SLA) with those core IT teams -- although in larger shops, a Logical DBA/physical modeler may be needed.

More information on business intelligence and data warehousing teams:

 

 

This was first published in May 2007