Power BI Model Development Best Practices in a Team
summary
Describes a source control based model workflow that enforces a Git branch per environment with main = production, a release branch like release/2.6 for UAT and monthly milestones, and automated deployment from branch to workspace via a CI/CD server. Recommends strict semantic versioning for datasets (major/minor/patch), developer-only PPU for dev, use of PBI-Tools, Tabular Model Definition Language text format for readable model files, and shows this setup reduces downtime and speeds developer feedback in real projects.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 3:52Delivery vs engineering distinction
- 8:10PM side and product management
- 17:12DataOps manifesto overview
- 21:26Semantic versioning explained
- 26:22Engineering side principles
- 30:16Environment and branching strategy
- 40:09Tabular model definition language
- 45:53Q&A session
related talks
20mPower BI Culture: Governance as a gateway to adoption, not a barrier.
37mPitfalls and pro-tips for effective and transparent BI tools data science & applications
50mPrepare for Takeoff: Navigating Power BI Developer Mode - Is the Journey Worth the Flight?
01h 10mContinuous Integration for the BI Developer
26mWorking with Data Scientists and why I left my job (not)
48mBest practices for developing Power BI reports
01h 00mTaking BI to the Next Level: Collaboration
01h 03mPower BI for the Developer