Kimball Approach To Data Warehouse Lifecycle < 2025 >

Everything starts with business requirements. The Kimball team insists on dimensional bus matrix —a simple spreadsheet that maps business processes (e.g., "Order Fulfillment") to common dimensions (e.g., "Date," "Product," "Customer"). This matrix becomes the master plan. It identifies which data marts to build first based on business priority, not technical convenience.

In the shifting landscape of modern data architecture—where buzzwords like “data mesh,” “lakehouse,” and “real-time analytics” dominate conference keynotes—one methodology has quietly endured for over three decades. It doesn’t chase trends. It doesn’t promise magical AI insights from raw chaos. Instead, it offers something rarer: a pragmatic, business-driven, repeatable path from source systems to trusted decisions. kimball approach to data warehouse lifecycle

Star schemas are highly denormalized, which plays perfectly to the strengths of columnar databases (Redshift, BigQuery, Snowflake) and traditional RDBMSs. Query optimizers love star joins. Everything starts with business requirements

Here, the famous Kimball dimensional model is created. A fact table is designed for a single business process (e.g., "Daily Sales Facts"). Dimensions are "conformed" so they can be used across multiple fact tables—ensuring that "Customer" means the same thing in Sales and Returns. It identifies which data marts to build first

That methodology is the .

Simultaneously, the back room (ETL) and front room (BI) are developed in parallel. Kimball famously separates the (data staging area: messy, technical, high-volume) from the presentation area (dimensional models: clean, business-facing, accessible). The ETL system must handle slowly changing dimensions (SCDs)—tracking historical changes like a customer’s address over time—a signature Kimball contribution. Stage 3: Deployment & Iteration Phases: BI Application Development, Deployment, Maintenance & Growth.

The other pillar of the philosophy is . Instead of complex, normalized schemas (third normal form) that confuse analysts, Kimball advocates for star schemas: a central fact table containing quantitative measures (sales dollars, units sold) surrounded by dimension tables containing descriptive attributes (customer name, product color, date). This design is intuitive, fast, and resilient to change. The Kimball Lifecycle: A Roadmap, Not a Waterfall The Kimball lifecycle is often visualized as a circular, iterative flow, not a straight line. It comprises nine high-level phases, but they group into four critical stages. Stage 1: Planning & Business Alignment Phases: Project Planning, Business Requirements Definition, Technical Architecture Design.