Best practices for end-users' interaction with DW/DMs?
Now that the first little corner of our DW is in production, an important governance question has arisen:
How do users interact with this resource?
The way I see it, there are a few camps to address. Here's the draft of what I've come up with so far:
Average business users will continue accessing their dashboards with no direct interaction with the DW, but those dashboards now load faster (in our initial case, 10x faster 🤯) with less latency, and are more readily and easily extensible by our BI devs.
Citizen developers/power users should have access to create their own dashboards/visualizations by connecting to a view (created by the AE via a post-loading script in the data mart task) of the data in the DM.
BI developers on the analytics team should have access to create dashboards/visualizations and do other analysis projects by connecting to a view (created by the BI dev via a separate post-loading script) of the data in the DM.
The AE maintains ownership of the DW and the DMs populated by it; new data in a DM and/or a new DM would be official feature requests.
For those of you further down the road in your DWBI environment development, or anyone on the Qlik team familiar with these sorts of governance/data ops questions, I'd love your feedback. Specifically, we are trying to work out appropriate access for our BI devs:
Should a BI developer have access to create a new post-load view? Or should this be the sole purview of the AE?
Should a BI developer have access to create a new DM? Or, again, should this be the sole purview of the AE?
As long as you're getting something out of doing it. : ) I know how you feel with the outside reading, I've tried giving my players "common knowledge" info on groups they were interacting with, and no one bothered.
