Delivering Agile BI Solutions
summary
Moves a stalled waterfall program that needed an extra $500,000 into an agile Scrum flow that actually ships working BI: physical user-story cards for prioritization, 2–3 week sprints, daily standups, Sprint burndowns and velocity tracking. Uses Kimball-style dimensional matrices and an opportunity quadrant to pick subject areas, implements Analysis Services cubes and recommends Power Pivot for low-value cases, and reserves 10–20% technical debt capacity so iterative builds remain maintainable and usable.
AI-written summary · about
chapters (15)
- 0:00Agile BI journey intro
- 4:54Extreme programming pitfalls
- 10:15Waterfall failures lessons
- 13:44Structure versus agility
- 17:36Agile Scrum in BI
- 23:20Sprint cycles benefits
- 26:06BI user stories
- 32:19Velocity and burn down
- 35:10Waterfall to Agile overnight
- 37:14Kimball methodology in BI
- 41:07BI priorities with matrix
- 43:56BI roles and structure
- 49:09Technical debt management
- 51:13Projects to BI programs
- 52:16Q&A requirements planning
related talks
40mAgile Software Development: Practice and Analytics
35mScrum Overview
25m"Data Science & Agile: Strategies for Working Together"
39mScrum at Scale
33mMaximizing Data Usability for Impact
41mCreating an Effective Reporting Strategy: Tools, Metrics, Analytics
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
20mAgile development application for live ops