I feel comfortable doing the reporting and scripting but it would be good to validate my ideas for the designs when I get some hands on experience - hopefully soon!
Maybe a new question but I wonder if the data warehouse has been superseded a little by the whole big data / multiple data sources thing?
Something that stood out to me was their discussion about "Big Data technologies" (Hadoop, HBase...) and how they "support" data mining techniques. So sometimes I wonder if big data technologies are more for the processing of the data, like the ETL needed for data warehouses - but since it's big, we need those special technologies to process it (and do additional data-sciencey things on it - like calculate a probability of churn, probability of loan default, etc). End results can still be those high-performance in-memory objects that we can slice and dice, just like our data warehouses, if that's how we need to see them.
This is all coming from no practical experience with Hadoop / Big Data, just research so hopefully someone clarifies :)
I know you said you're aware of Ralph Kimball, but the first ~100 pages are broken into 1) Defining the Business Requirements and 2) Designing the Business Process Dimensional Model. It's really helped me wrap my head around the original design of the Facts and Dimensions as they relate to the business.