I had never heard of BEAM but from the brief summary I feel like I am starting to mentally toy with that concept right now.
This is timely, I have notes in my 1:1 doc with my manager for this upcoming week about how we have a need for modeling some key business processes, instead of locking that up in custom sql in a dashboard
I've led a few organisations through it and it is really good at engaging the business stakeholders, while helping the data stakeholders understand the business processes better (and why to include business teams in the modelling). I've not done a Kimball implementation of it, but I've seen the outputs and it feeds really well into other bits like defining data assets/ products, categorising metadata into the Data Catalogues, and designing a solution architecture around the BEAM/ Kimball model. Check out the book on the stuff (I need to read it more too - http://www.amazon.com/Agile-Data-Warehouse-Design-Collaborative/dp/0956817203)
I had never heard of BEAM but from the brief summary I feel like I am starting to mentally toy with that concept right now.
This is timely, I have notes in my 1:1 doc with my manager for this upcoming week about how we have a need for modeling some key business processes, instead of locking that up in custom sql in a dashboard
I've led a few organisations through it and it is really good at engaging the business stakeholders, while helping the data stakeholders understand the business processes better (and why to include business teams in the modelling). I've not done a Kimball implementation of it, but I've seen the outputs and it feeds really well into other bits like defining data assets/ products, categorising metadata into the Data Catalogues, and designing a solution architecture around the BEAM/ Kimball model. Check out the book on the stuff (I need to read it more too - http://www.amazon.com/Agile-Data-Warehouse-Design-Collaborative/dp/0956817203)