PBI Development approach in different organizations - self-service vs IT?

[southwood]

We're nearing the end of year 1 with rollout out PBI enterprise-wide and we're still evaluating the most efficient approach for delivery.

Our management assumed that Microsoft's positioning as a complete self-service environment meant that each business unit should take charge of all development with the intent of removing IT as the traditional bottleneck.  As the main PBI liaison, I've envisioned the struggles many of the less-technical groups encounter trying to wrangle data and create an optimized data model.  

I'm curious as how other organizations have approached these challenges and ulitmately where they landed.  If you wouldn't mind replying which of the following options your organization has chosen and feel free to add any addional comments.

Current PBI development approach:

(A) All IT-driven (data models and dashboards)

(B) Hybrid (IT creates all data models; business creates dashboards)

(C) All business driven (data models and dashboards)

(D) Controlled business driven (data models and dashboards using only a specified presentation-ready list of data-marts)

(E) Other

Thanks for any replies.

[AlexisOlson]

In my company, the dev team (programmers) mostly manages the SQL side of things (ETL, stored procedures, views, etc) and the analytics team builds data models and reports based on stuff in SQL and SharePoint. I'm a bit in the middle but officially on the analytics side. I do a limited amount of work in SQL and have personally built the majority of shared data models that most reports depend on since I have the most experience with DAX and data modeling.